Explain job-change motivation despite mission fit

Approach Use a concise 3-part structure: 1) What you’ve learned and appreciated + the gap (fact-based, non-negative). 2) Proof you tried to improve the situation. 3) What you want next, mapped to impact, growth, and mission. Quantify each gap with concrete examples. Useful metrics to quantify gaps (pick a few that are true for you) - Impact - Users reached: internal-only (≈200) vs external (≥100k+) - Business outcomes: revenue influenced, cost savings, conversion uplift, churn reduction - Reliability/latency: p95 latency, SLOs, incident frequency - Speed and autonomy - Release cadence: monthly vs daily/continuous - DORA: deployment frequency (2/month vs 20/day), lead time for changes (2 weeks vs hours) - Approval layers: 4+ sign-offs vs engineer-owned changes behind feature flags - Ownership and scope - From single component to owning an end-to-end surface area (service + data + UX) - Design-to-launch cycles owned per quarter (0–1 vs 2–3) - On-call/build ratio: 60% tickets/ops vs 70% roadmap delivery - Growth - Mentorship: active staff/principal mentorship hours/month - Promotions: promotions to senior/staff in org last year (e.g., 1 of 40) - Learning budget/courses, conference talks, design reviews per quarter - Mission alignment - Product domain relevance to your values/user problems you care about - Company’s north star metrics aligned with your motivation (e.g., safety, access, sustainability) Sample 75-second answer (tailor numbers to your reality) "I’ve had a strong run at my current company—shipped two services that reduced p95 checkout latency by 28% and cut infra costs by 12%. The gap is less about work quality and more about impact, growth velocity, and mission fit. On impact, my team builds internal tooling used by about 180 engineers; that’s valuable, but I’m looking to work on products directly used by 100k+ customers where I can tie changes to metrics like activation rate or retention. On speed, our deployment frequency is ~2 per month with a two-week lead time and four approval layers. I prefer an environment with daily deployments, feature flags, and tighter build–measure–learn loops. On growth, promotions to senior/staff were 1 of ~40 engineers last year, and design review opportunities are sparse—maybe one per quarter. I’ve sought more ownership by proposing a CI pipeline that cut flake rate by 35% and mentoring two junior devs, but broader changes require org-level shifts. In my next role, I’m seeking end-to-end ownership of a user-facing surface, faster iteration supported by strong testing/observability, and a mission where user outcomes are the north star. I’m excited by teams where engineers ship weekly, measure impact directly, and invest in mentorship and architectural rigor." Alternate phrases you can adapt - Impact - "I’d like to move from internal cost-center metrics to user and revenue-facing KPIs like conversion, LTV, or time-to-value." - "I’m seeking ownership of a service handling 10x current traffic with clear SLOs." - Growth - "I’m looking for regular architecture reviews and a path to tech leadership; currently there were 0 openings for staff last cycle." - "I want to lead 2–3 design-to-launch projects per half; I averaged 0–1." - Speed - "I prefer CI/CD with trunk-based development and progressive delivery; today’s monthly releases slow learning loops." - Mission - "I’m motivated by products improving [X outcome]; my current roadmap pivoted away from that focus this year." Show you tried to fix it (interviewer follow-up ready) - "I proposed and piloted feature flags to enable dark launches; it worked for one service but org-wide adoption was deprioritized." - "I created a weekly design-review and mentored two engineers; helped locally, but ladder criteria remain unchanged." - "I pushed for adding SLOs; we set them for one service but lack product KPIs to close the loop." Do’s and don’ts - Do: Be specific and measurable; tie to business/user impact; stay respectful. - Do: Show agency—what you tried internally. - Do: End with what you want next and how you’ll contribute. - Don’t: Complain about people or compensation as the lead point. - Don’t: Share confidential numbers; use ranges or percentages. - Don’t: Be vague (e.g., "better culture"); define it (e.g., deployment cadence, ownership). Quick template to craft your answer 1) Current: "I’ve delivered [X results]; I value [Y]." 2) Gap: "I’m limited by [metric/cadence/ownership], e.g., [concrete example with numbers]." 3) Agency: "I tried [action] which achieved [result], but [org constraint]." 4) Next: "I’m seeking [impact on users/KPIs], [growth path], and [mission alignment], ideally with [specific engineering practices]." Quality check before you say it aloud - Can you state 2–3 metrics that quantify the gaps? - Did you avoid blaming individuals and focus on structure/process/scope? - Can the listener picture what you want to do in the first 90 days? This framing keeps you positive, data-driven, and aligned to a mission- and impact-focused engineering environment while clearly explaining why you’re moving.