Sample analysis
What a Job Fit actually tells you
This is one worked example, start to finish. A real Job Fit is generated from your own profile against a job you paste in — the score, the evidence and the questions all change. What stays the same is the shape: what you have, what you don’t, and what to do about it.
This candidate and role are invented for illustration. Nothing here describes a real person, a real company, or a real application.
The role
Staff Platform Engineer
Northwind Systems · Remote (US)
The candidate
A software engineer with 8 years' experience, mostly at growth-stage SaaS companies
The read
This role wants someone who has owned a platform other engineers build on, not just built services within one. Your API and SDK work maps directly onto that, and the scale you have worked at is in the right band. The gap is organisational rather than technical: the posting repeatedly describes influencing roadmaps across teams you do not manage, and your evidence for that is thinner than your evidence for shipping.
Strengths
What you bring that maps to this role — each tied to something in your history, not a restatement of the job ad.
- Owned a public REST API used by 5,000 external developers — the posting's first responsibility is 'own the public platform surface', and this is direct evidence rather than adjacent work.
- Shipped TypeScript and Python SDKs with documentation, cutting integration time from days to hours. The role asks for 'developer experience as a first-class concern' and names SDKs specifically.
- Ran a weekly cross-functional sync across three teams and shipped a launch two weeks early with no rework — partial evidence for the influence-without-authority requirement.
- Depth in TypeScript, Python, PostgreSQL and Kubernetes covers the whole listed stack, with no requirement unaccounted for.
Gaps
Named plainly rather than implied — and each one is answerable.
A gap isn’t a dead end
Your resume is a summary, and the skills interview only reaches so far in one sitting. Plenty of what you’ve actually done never makes it into either. Address this gap lets you add it now — the skill, where you did it, and what came of it.
- It joins your profile, so every future resume and analysis can use it.
- Re-run the analysis and the gap is scored against the new evidence.
- For something you genuinely haven’t done yet, Add to plan tracks it as a thing to learn instead.
No evidence of formal technical leadership at staff level. The posting says 'set technical direction for the platform group'; your history shows leading projects, not setting direction across a group.
Address this gapAdd to plan
Setting technical direction · Meridian Labs
Owned the platform roadmap across three teams for two quarters — chose what shipped and in what order, and defended it at planning.
Added by the candidate — now part of their profile
Event-driven architecture appears once in your profile as Kafka familiarity. The role treats it as core, mentioning event streaming four times.
Address this gapAdd to plan
No public writing, talks or open-source presence. Two of the listed responsibilities involve representing the platform externally.
Address this gapAdd to plan
What to do about it
Concrete changes before you apply — including the ones you can't close, which are better acknowledged than hidden.
- Lead with the API and SDK ownership, not with years of experience. The strongest evidence you have is the thing they asked for first, and it is currently third on your resume.
- Reframe the cross-functional sync as direction-setting rather than coordination — you decided the roadmap order, which is closer to what they are asking for than 'ran a meeting' suggests.
- Name the Kafka work concretely, even if the scope was small. An honest 'built one consumer pipeline' beats silence against a requirement mentioned four times.
- The external-presence gap is real and not closable before you apply. Address it directly in a cover letter rather than hoping it goes unnoticed.
Questions to prepare for
Drawn from the gap between your profile and this role, so they're the questions this interview is likely to probe.
- Walk me through a technical decision you made that other teams had to live with. How did you get their agreement?
- You have built on top of platforms and you have built platforms. What changes about the job when your users are other engineers?
- Tell me about a time you set direction and were wrong. When did you notice, and what did you do?
- How would you decide whether a piece of functionality belongs in the platform or in a consuming service?
- Your event-streaming experience looks lighter than the rest of your stack. How would you get up to speed here?
Matched skills
- TypeScript
- Python
- PostgreSQL
- Kubernetes
- Public API design
- Developer SDK delivery
- Cross-functional partnership
Not evidenced
- Event-driven architecture at scale
- Staff-level technical direction
- External technical communication
Run this against a job you actually want
Upload your resume, paste a job description, and get this for your own profile. Setting up is free and needs no card.