The Lead Engineer owns the technical integrity, reliability, and scalability of the Quest platform, while also being directly hands-on in building critical systems.
This is a player-coach role:
○ You will write and review code
○ Solve complex technical problems directly
And ensure that all engineering (internal + vendors) meets high quality and architectural
Standards
Key Responsibilities:
Hands-on Engineering Ownership (Critical)
○ Actively contribute to core platform code (backend, APIs, system components)
○ Take ownership of complex, high-risk, or poorly understood problem areas
○ Performance bottlenecks
○ Data inconsistencies
○ Critical bugs (e.g., save failures, concurrency issues)
○ Build reference implementations that set standards for vendors
○ Step in when:
○ Root cause is unclear
○ Issues are repeatedly reopened
This role is not advisory — you get into the code and fix things
Architecture & System Design
○ Define and evolve platform architecture
○ Ensure system coherence across modules, services, and integrations
○ Make pragmatic architecture decisions grounded in real constraints