About you You don't need to have experience of every single point, but these are the attributes of someone who will perform well in this role: 5+ years building software, with a good chunk of it on data-heavy or integration-flavored systems Solid backend and systems instincts. You can reason about deployment topology, multi-tenancy, and data movement, and you're comfortable owning architectural tradeoffs you'll have to live with later You've worked with modern auth protocols, service principals, and identity federation, and you know how to get it right across a trust boundary You've built on someone else's platform and know what that's actually like: incomplete docs, unintended breaking changes, etc. You're comfortable in ambiguity. You can ship before the spec is finished, make sensible calls under uncertainty, and flag the decisions that'll be hard to undo instead of quietly baking them in. You're good with other engineers. Much of the work runs through teams you don't own, and you earn their trust by how you think, not just what you commit. You're mainly a backend engineer, but you're comfortable enough in JavaScript / TypeScript to jump in when it helps You use AI tools well and honestly. Reach for Claude Code, Cursor, Copilot, or whatever helps, and be clear about where you did and didn't You write well. Most of how we coordinate happens in design docs, PRs, and RFCs
