We're looking for a technical lead to help drive the backend architecture for an Internal Reporting tool, a business intelligence and client reporting platform serving enterprise healthcare clients. You'll set technical direction across a suite of interdependent backend services, guide a team of engineers through delivery, and be the primary escalation point for architectural and cross-service decisions. This role blends hands-on engineering with technical leadership: you'll still write code and review designs, but you're also accountable for the health, coherence, and direction of the system.

Requirements

What You'll Do

• Own the technical roadmap for backend services: reporting, data access, scheduled processing, and export/delivery
• Drive architectural decisions across multiple interdependent services and data sources, and document them for the team
• Set and enforce engineering standards: code quality, testing practices, API design conventions, and observability
• Review designs and code from other engineers, and unblock them on hard technical problems
• Break down ambiguous requirements into a clear technical plan the team can execute against
• Balance short-term delivery pressure against long-term technical health; call out and manage technical debt deliberately
• Partner directly with product, QA, and other engineering teams to align on scope, sequencing, and dependencies
• Lead and propose ideas/solutions in cross-team architecture discussions and vendor/platform evaluations
• Mentor engineers on the team and help grow their technical judgment, not just their task list
• Hands-on Engineer: contribute code, especially for the highest-risk or highest-ambiguity problems

What We're Looking For

Required:

• 12+ years building and operating production backend systems, with demonstrated technical leadership (formal or informal)
• Strong hands-on experience with a modern backend language and framework (e.g. Java/Spring, Kotlin, C#/.NET, Node.js, Python, or Go)
• Track record of making and owning architectural decisions across multiple services, not just within one
• Solid relational database experience (schema design, migrations, query performance) at a systems-design level
• Experience designing REST APIs and service contracts that other teams build against