Job Description
THE ROLE
This is not a promotion title for a mid-level developer. This is for the engineer who decides how systems are structured — who owns architecture, not just implementation within it.
You'll work directly with the CTO and product leadership to translate ambiguous business problems into system design. You'll define scope, propose architecture, own decisions end-to-end, and be accountable for outcomes.
If you've always worked within someone else's architecture, this isn't the role. If you've been the person who defines that architecture — keep reading.
WHAT YOU'LL OWN
• System architecture: service design, inter-service communication patterns, event-driven design, and data modeling — independently, from first principles
• Technical requirement gathering directly with product and business stakeholders — you define scope, not wait for a spec
• AWS infrastructure architecture: compute, networking, data layer...