Backend / Java Engineering Requirement

Backend / Java Engineering LeadWe'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.Own the technical roadmap for backend services: reporting, data access, scheduled processing, and export/deliveryDrive architectural decisions across multiple interdependent services and data sources, and document them for the teamSet and enforce engineering standards: code quality, testing practices, API design conventions, and observabilityReview designs and code from other engineers, and unblock them on hard technical problemsBreak down ambiguous requirements into a clear technical plan the team can execute againstBalance short-term delivery pressure against long-term technical health; call out and manage technical debt deliberatelyPartner directly with product, QA, and other engineering teams to align on scope, sequencing, and dependenciesLead and propose ideas/solutions in cross-team architecture discussions and vendor/platform evaluationsMentor engineers on the team and help grow their technical judgment, not just their task listHands-on Engineer: contribute code, especially for the highest-risk or highest-ambiguity problemsRequired: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 oneSolid relational database experience (schema design, migrations, query performance) at a systems-design levelExperience designing REST APIs and service contracts that other teams build againstExperience with cloud platforms, GCP preferredStrong understanding of authentication/authorization patterns and security tradeoffs in distributed systemsExperience coordinating work and dependencies across multiple engineers and multiple servicesExperience with CI/CD pipelines and containerization, including improving pipeline health and delivery velocityStrong background in building scalable, distributed applications and platformsStrong written and verbal communication; comfortable presenting tradeoffs to both engineers and non-technical stakeholdersJava and spring and (Kotlin or .net or python or Go or Golang or Node)Strongly preferred:Experience integrating with BI/analytics or data-warehouse platformsBackground in regulated or audit-sensitive domains (healthcare, finance, insurance) where data lineage and correctness are strict requirementsExperience leading a system through a migration or major architectural shiftExperience designing asynchronous or scheduled processing for large data volumesExperience establishing role-based access control and data visibility enforcement at a system-design levelExperience mentoring engineers and running technical planning (grooming, estimation, design reviews)Nice to have:Experience with distributed caching or session/token storesEnough frontend familiarity to review API design from the consumer's perspectiveExperience building out observability and logging practices for a team, not just using them