Example report
See what the analysis looks like before you upload anything
Anonymised client report
Engineering Manager, industrial software
This is a real report from a CareerSynth client, published with permission. The name, employer and any identifying details have been removed. Only the role title, the analysis and the recommendations remain.
Executive summary
The client manages two engineering teams and has run one significant cross-team programme. The experience supports a director-level move, but the written profile does not. Achievements are described as responsibilities, and the strongest proof point, a 14 month platform migration, is buried in the middle of the current role.
The recommended direction is Director of Engineering in industrial software, with Head of Platform as a faster alternative. The decisive constraint is evidence of budget and hiring ownership, not technical depth.
Career Positioning Score: 60 of 100
This score is a decision-support indicator based on the information provided. It is not an objective market ranking. It is not a percentile and it is not a ranking against the labour market.
Leadership scope
64 of 100Two teams and eight engineers are stated. Budget ownership and hiring authority are not documented, which caps the score for director-level targets.
Confidence: Medium
Evidence of impact
51 of 100Most achievements describe responsibilities rather than results. Two entries carry a measurable outcome.
Confidence: Low
Target-role relevance
78 of 100Platform and reliability experience maps closely onto the responsibilities named in the target role. This compares the profile with that role only, not with other candidates.
Confidence: High
Strategic differentiation
47 of 100The profile reads like many engineering managers. The migration programme is the one distinctive asset and it is under-stated.
Confidence: Medium
Target-role readiness
58 of 100Director of Engineering is reachable within four to six quarters if budget and hiring evidence is built.
Confidence: Medium
One conclusion, with its evidence trail
Conclusion: the profile understates the one achievement that qualifies this client for director-level conversations.
- Extracted fact
The CV states: led a platform migration across two teams over 14 months, reducing deployment failures from weekly to monthly.
- User statement
The target role given in the intake form is Director of Engineering within industrial software.
- Interpretation
The migration is the strongest available proof of cross-team execution. It is currently listed as one bullet among nine and is not visible to a reader scanning for 20 seconds.
- Assumption
We assume the migration was owned rather than delegated. If a staff engineer held technical ownership, the readiness score for director-level roles drops.
Three career paths
- Recommended
Director of Engineering
- Fit
- Strong
- Readiness
- Partial
- Transition
- Moderate
Closest to demonstrated scope. The gap is commercial and budget ownership, not technical credibility.
- Alternative
Head of Platform
- Fit
- Strong
- Readiness
- High
- Transition
- Low
Best match to the migration evidence. Narrower long-term ceiling than a general engineering leadership track.
- Stretch
VP Engineering, scale-up
- Fit
- Moderate
- Readiness
- Low
- Transition
- High
Requires org-building and hiring evidence that the profile does not yet contain.
Scenario comparison
| Criterion | Director of Engineering | Head of Platform | VP Engineering |
|---|---|---|---|
| Strategic fit | Strong | Strong | Moderate |
| Demonstrated readiness | Partial | High | Low |
| Evidence strength | Medium | High | Low |
| Transition difficulty | Moderate | Low | High |
| Time to credibility | 4 to 6 quarters | 1 to 2 quarters | 8+ quarters |
| Primary risk | No budget evidence | Narrower ceiling | Scope gap is visible |
The full report compares twelve criteria per path and states why one path is recommended over the others.
One positioning gap
No documented budget or hiring ownership
Director shortlists are usually built around resource decisions. The profile shows delivery ownership and no budget, headcount planning or vendor decisions. Evidence needed: annual budget figure, number of hires made, and one resourcing trade-off you decided.
Confidence: Medium. Two further gaps are covered in the full report.
CV and LinkedIn recommendations
Lead the current role with the migration
Move the platform migration to the first bullet and state scope, duration and result in one line: "Led platform migration across 2 teams (8 engineers) in 14 months, cutting deployment failures from weekly to monthly." Insert your verified figure where the placeholder sits, do not estimate.
Replace the job title headline
Headline option: "Engineering Manager, platform reliability and cross-team delivery in industrial software." It states the audience and the problem you own. The full report gives three headline options and an About structure.
90-day plan, first phases shown
Days 1 to 30
- Rewrite the current role around the migration outcome, with team count, duration and failure-rate change in the first bullet.
- Confirm two verifiable numbers with a former colleague before publishing them.
Days 31 to 60
- Open five conversations with directors in industrial software and record which part of the story they question first.
Days 61 to 90
- Available in the full report.