Example with sample data
Findem
Workforce intelligence Talent flow report
ExampleCo’s engineering talent flow.
184 observed joiners against 44 departures — net +140 in Software engineering. Observed moves.
ExampleCo · Software engineering2024-01-01 – 2025-12-31
As of 2026-01-01 · Revision 1 · Sources [1]
The talent-flow picture
A steady net gain in engineering.
184 observed joiners against 44 departures — net +140 in Software engineering.
Illustrative example. Joiners rise across the eight quarters while observed departures remain lower. A live report replaces these values and this interpretation with the requested company and role.
+140
Net observed moves
4.18
Joiners per leaver
2.29×
Joiners: 2025 vs 2024 (full years)
170
Joiners with a known prior employer
Findem
Observed moves · Software engineering · Sources [1]
Headline metrics
Observed moves · Software engineering
184
Joined
Observed in requested cohort
44
Left
Observed in requested cohort
+140
Net flow
Observed joiners minus leavers
4.18
Joiner : leaver
Ratio
60
Top inflow source
Northstar · 32.6%
15
Top outflow destination
Orion Labs · 34.1%
170
Attributed joiners
Moves with a known prior employer
32
Attributed leavers
Moves with a known next employer
Findem
Observed moves · Software engineering · Sources [1]
Quarterly talent flow
Joined vs. left vs. net, per quarter
Joined
Left
Net flow
ExampleCo · Software engineering · observed talent flow01020304024 Q124 Q224 Q324 Q425 Q125 Q225 Q325 Q4
Illustrative trend: all eight quarters show positive net flow. Complete periods · observed moves
Observed moves · Software engineering · Sources [1]
Year over year
Observed hiring rises across two full years
Joined
Left
56
14
128
30
2024
2025
Annual observed totals · partial years are not annualized · Sources [1]
Per-role breakdown
The requested engineering cohort
Separately queried title cohorts. Cohorts may overlap; do not add their totals.
Role cohort
Joined
Left
Net
Top inflow source
Top outflow destination
Software engineering
184
44
+140
Northstar (60)
Orion Labs (15)
Cohort precision and filters are recorded in the method notes · Sources [1]
Ranked employers · Software engineering · 1/1
Inflow sources & outflow destinations
Inflow Joiners · % of inflow
Northstar60 · 32.6%
Orion Labs35 · 19.0%
HarborWorks12 · 6.5%
Outflow Leavers · % of outflow
Orion Labs15 · 34.1%
Northstar10 · 22.7%
Cedar Systems7 · 15.9%
Bars scale separately within each direction · percentages use that direction’s observed total · Sources [1]
Talent-market exchange
Two-way moves, company by company
Net gain
Net loss
Company
In
Out
Observed net flow
Northstar
60
10
+50
Orion Labs
35
15
+20
Cedar Systems
—
7
—
HarborWorks
12
—
—
— = not observed in a returned top-company list; not zero. Net requires both sides. Companies are not automatically competitors.
Observed moves · Software engineering · Sources [1]
Key findings
Findem workforce intelligence
{01}
A positive observed balance.
In this fictional example, 184 joiners and 44 leavers produce a net gain of 140 observed moves. [1]
{02}
Northstar leads the inflow.
The largest returned source contributes 60 of 184 joiners. Shares use the full observed direction total. [1]
{03}
Exchange evidence is uneven.
Both sides are available for Northstar and Orion Labs. Missing counterparts remain unknown for the other employers. [1]
{04}
Keep coverage in view.
170 joiners and 32 leavers have a known adjacent employer. These figures count attributed moves, not unique companies. [1]
Findem
Findings and interpretations from the cited source runs · Sources [1]
The so what
Use observed engineering flows to focus the next workforce conversation.
Illustrative interpretation: investigate the strongest feeder relationships and the destinations visible in both directions. Movement alone does not explain why people leave.
Findem
Strategic interpretation · observed flows do not establish motives or future moves · Sources [1]
Method & source
Observed moves, explicit coverage.
ExampleCo · Software engineering · 2024-01-01 – 2025-12-31. Observed moves. 184 joiners / 44 leavers are observed employment events; 170 / 32 have a known adjacent employer. Attribution counts describe moves, not distinct companies. Percentages use 184 / 44 as denominators. Public-profile coverage is not an employee census. Partial periods are marked; cohorts may overlap.
Retrieved 2026-01-01 · 1 source run · revision 1. Detailed query and coverage notes follow.
Findem
Method & source
Source 1 · Software engineering

[1] Software engineering · retrieved 2026-01-01

Company: ExampleCo (example-only). Window: 2024-01-01 – 2025-12-31. Titles: software engineer. Skill filters: [].

Precision: exact. Profiles (in/out): 184/44. Truncated (in/out): false/false. Unhydrated (in/out): 0/0.

Coverage (in/out): attributed moves 170/32; unknown employer 14/12; self-employment-like 0/0. Excluded internal transfers: 0; boomerang profiles: 0.

Timeline: the tool may omit periods with no events. After its period totals reconcile with its headline, missing periods display zero observed moves. The original response is retained unchanged; sample zeros are not proof of zero workforce activity.

Corporate family: distinct; annotated; coverage complete.

Illustrative example only. The company and employer counts are fictional and demonstrate the report layout.

A missing company in a top-N list does not establish zero moves.

Findem · 2026-01-01 · revision 1
Findem