Kraken Senior Backend Engineer (Growth Platform) — X-Ray

We built three fictional candidate personas — a senior platform engineer, a product-focused backend engineer, and a full-stack developer transitioning to backend — and ran each of them through JobJam against Kraken's real job description. The personas are made up. The JD, the evaluator, the scores, and the analysis are real JobJam output. Same role, three very different results.

This page is not affiliated with or endorsed by Kraken. The job description is sourced from Kraken's public careers page. The three candidate profiles are fictional, designed to represent realistic archetypes — any resemblance to real individuals is coincidental.

The role

Kraken's Growth Platform team builds internal tooling, services, SDKs, CLIs, and APIs used by Growth engineering teams across marketing funnels, signup, KYC, engagement, and funding. The role requires 5+ years of software engineering experience, proficiency in TypeScript, Rust, Go, Python, or Ruby, and hands-on experience with distributed systems, Docker, Kubernetes, Terraform, MySQL/MariaDB, Redis, and GitLab CI/CD. Ability to design APIs and SDKs consumed by other engineering teams is core to the job.

What this role is actually testing

Past the bullet list of required skills, the JD is probing for four things that a keyword matcher will miss:

• Platform-engineering depth, not product-API breadth. Kraken wants SDKs, CLIs, and shared services consumed by other engineers — a different muscle from building REST APIs consumed by a mobile app.
• Polyglot reach, not single-language fluency. The "TypeScript, Rust, Go, Python, or Ruby" phrasing is a filter for engineers who can pick up a language in a week, not specialists in one.
• Developer-experience obsession. Docs quality, ramp-up time, observability, reliability improvements — the role is scored on how much faster other engineers move because of your work.
• Senior technical leadership and mentorship. Not years of experience. Evidence of mentoring engineers, driving technical design across teams, advocating for engineering excellence.

Watch how each of the three profiles below lines up — or doesn't — against these four axes.

Profile A — James Okonkwo, Senior Platform Engineer (Fintech)

6 years of senior backend experience at Plaid and Twilio. Built internal SDKs, CLIs, and developer platforms at fintech scale. TypeScript and Go, Kubernetes, Terraform, observability, mentorship — all present. Direct experience in the exact domain the role is asking for.

JobJam fit evaluation for James Okonkwo — 92% ATS score, 9/11 skills matched, Excellent Match

92% — Excellent Match. 9/11 skills matched.

JobJam overall assessment for James Okonkwo — direct experience in all core responsibilities

JobJam's assessment: excellent candidate with direct experience in all core responsibilities — building SDKs, CLIs, APIs, internal platforms, and owning reliability improvements. 9 of 11 required technical skills, all soft skills demonstrated through concrete examples. The only gaps are Rust and Ruby, addressable given James's strong polyglot background.

JobJam match analysis for James Okonkwo showing strengths across Experience, Soft Skills, and Technical Skills

What JobJam recommended

Even at 92%, JobJam found 5 specific improvements:

1. Highlight Rust experience or learning plan — Rust is a required skill not present in resume. Adding even basic Rust exposure or a learning initiative would address this gap.
2. Emphasize cross-team collaboration and partnership — role requires partnering with engineers to understand pain points. Resume shows this implicitly but it could be more explicit.
3. Quantify developer experience improvements — DX is central to this role. James's metrics are strong but could be more prominent.
4. Demonstrate infrastructure and platform team collaboration — role requires close partnership with infrastructure and platform teams on reliability and observability.
5. Showcase technical design leadership at scale — bonus skill and important for a senior role. Current resume shows this but could be stronger.

JobJam recommendations for James Okonkwo — 5 specific actions

Profile B — Ana Costa, Backend Engineer (Product APIs)

5 years of backend experience at iFood and Creditas. Strong Python, Django, Flask, PostgreSQL, Docker. Solid foundation but product-API focused rather than platform focused. Missing TypeScript, Rust, Go, Kubernetes, Terraform, and SDK/CLI development experience.

JobJam fit evaluation for Ana Costa — 52% ATS score, 6/11 skills matched, Weak Match

52% — Weak Match. 6/11 skills matched.

JobJam overall assessment for Ana Costa — solid fundamentals with significant platform gaps

JobJam's assessment: solid backend engineering fundamentals with strong Python and API design skills, but significant gaps exist for a senior platform engineering role. Missing required languages (TypeScript, Rust, Go), infrastructure tools (Kubernetes, Terraform), and platform-focused work like SDK/CLI development and internal tooling. Growth trajectory is promising, but substantial skill development is needed to be competitive for this role.

JobJam match analysis for Ana Costa showing product-focused strengths vs platform gaps

What JobJam recommended

5 specific actions to close the gap:

1. Learn TypeScript and Go — required languages for the role and critical for SDK/CLI development. Ana's Python foundation makes learning these feasible.
2. Gain Kubernetes and Terraform experience — infrastructure automation is essential for platform engineering roles. Current AWS EC2 knowledge is insufficient for this level.
3. Build or contribute to an internal developer platform — role requires designing systems that improve engineering workflows. Product API experience doesn't demonstrate this capability.
4. Develop observability and reliability expertise — role emphasizes owning reliability, observability, and performance. Ana's incident response experience is a start but needs depth.
5. Demonstrate mentoring and technical leadership — senior role requires mentoring skills and advocacy for engineering excellence, which are not evident in the current resume.

JobJam recommendations for Ana Costa — 5 specific actions to close the gap

Profile C — Lena Vogel, Full Stack Developer (Frontend-primary)

4 years of full-stack experience at SumUp, Jimdo, and freelance. Strong React and TypeScript, some Node.js and Express backend work, basic Docker. Crypto enthusiast and DeFi user — genuine domain interest, but the experience is primarily frontend.

JobJam fit evaluation for Lena Vogel — 28% ATS score, 5/14 skills matched, Weak Match

28% — Weak Match. 5/14 skills matched.

JobJam overall assessment for Lena Vogel — junior-to-mid full-stack, insufficient backend depth for senior role

JobJam's assessment: junior-to-mid-level full-stack developer with strong frontend skills but insufficient backend depth for a senior backend platform engineering role. Critical gaps in backend languages, infrastructure tooling, and systems design experience make this a poor fit. The honest recommendation: 2–3 years of focused backend development before being competitive for this senior position.

JobJam match analysis for Lena Vogel showing significant backend architecture gaps

What JobJam recommended

Lena gets a development plan, not a resume polish:

1. Develop proficiency in backend-focused languages — Rust, Go, and Python are core requirements. Current Node.js experience is insufficient for senior backend role expectations.
2. Gain infrastructure and DevOps expertise — Kubernetes, Terraform, and GitLab CI/CD are required skills with no current experience. Essential for senior platform engineering role.
3. Build experience with databases and caching systems — role requires designing scalable databases and systems. Current experience is limited to basic PostgreSQL and Firebase.
4. Develop internal platform or SDK experience — core responsibility is building SDKs, CLIs, and internal tools. No current evidence of this work.
5. Demonstrate mentoring and technical leadership — senior role requires mentoring engineers and advocating for excellence. Resume lacks evidence of these activities.

JobJam recommendations for Lena Vogel — 5-step development plan

What this shows

Same role, same JD, three archetypes — three completely different analyses.

• James gets 5 recommendations about strategic narrative and subtle gap-closing. His 92% is ready to apply; JobJam is helping him polish.
• Ana gets 5 recommendations about filling specific platform-engineering skill gaps. Her 52% is a clear "not yet, but here's the path" — and every suggestion is grounded in what her resume already shows vs what the JD actually asks for.
• Lena gets an honest 28% and a 2–3 year development plan, not false hope. JobJam tells her what to work on instead of pretending she's a fit.

That's the difference between a keyword matcher and JobJam's multi-model evaluation pipeline: specificity grounded in the real resume, not generic "add more keywords" advice.

Not a mockup — here's the full dashboard

Every screenshot above is cropped from a real JobJam evaluation page. Here's what Ana's full dashboard actually looks like — JobJam nav, role header, the score ring, overall assessment, job details, match analysis, recommendations, and application notes, all in one uncropped screenshot:

Full JobJam dashboard for Ana Costa's evaluation against Kraken's Senior Backend Engineer — Growth Platform role

This is the actual product — same URL, same layout, same data — that you'd get running your own profile through JobJam.

Run your own profile against this role →

JobJam uses a one-time credit model — no subscription, no auto-renewal. See pricing →