Staff Software Engineer (Backend)

What you'll do

• Own technical direction across backend services and shared platform capabilities
• Translate ambiguous business needs into durable architecture and reliable execution
• Drive architecture alignment across multiple systems with clear service boundaries, interfaces, and design patterns
• Lead cross-team technical initiatives from discovery through production rollout with strong observability and documented tradeoffs
• Improve platform health by identifying and addressing structural weaknesses through refactors, new reference implementations, or infrastructure investments
• Increase engineering effectiveness across teams by improving tooling, testing strategy, and documentation
• Mentor senior engineers to expand their scope and technical influence
• Lead design reviews and technical discussions to bring teams to strong decisions without formal authority
• Establish reusable patterns and reference implementations adopted by other engineers
• Treat observability, incident management, and post-launch iteration as integral parts of the engineering process
• Identify systemic risk early and make sound decisions on patching, refactoring, or redesigning
• Invest in the development of senior engineers and lead by example with high-leverage code contributions

Requirements

• Deep proficiency in Go (or comparable systems/compiled language) with production experience building and operating large-scale distributed systems
• Strong systems design fundamentals: APIs, service architecture, concurrency, data modeling, fault tolerance, and performance
• Hands-on experience with Docker, Kubernetes, and AWS in production environments
• Operational instincts across monitoring, debugging, incident response, and systemic follow-through
• Demonstrated ability to lead complex, cross-team technical initiatives from problem definition through production rollout
• Strong written and verbal communication skills, including the ability to explain technical tradeoffs to non-technical stakeholders
• Familiarity with RTB, SSP, or auction systems — or other performance-sensitive distributed platforms where latency, throughput, and cost must be actively balanced (preferred)
• Experience building shared internal platforms or frameworks adopted across multiple engineering teams (preferred)

Tech stack