Tech Lead - Backend

Responsibilities:

• Design and build core platform services that handle complex business logic reliably at scale.
• Architect and own integrations with external enterprise systems, each with their own quirks, rate limits, and failure modes.
• Build APIs that enterprise engineering teams actually want to integrate with, not just ones that technically work.
• Own production debugging end-to-end: diagnose issues across services using logs, traces, and metrics, and make incidents boring rather than fires.
• Embed security and compliance thinking into your systems by default, not as a retrofit.
• Mentor the Senior Backend Engineers in your pod: pair on hard problems, review their work, and help them grow as engineers.
• Set the architectural direction for your domain: choose the frameworks, patterns, and abstractions the team builds on, and make the calls that shape the platform for years.
• Lead design reviews and code reviews, and set the technical standard the rest of the team calibrates against.
• Hold a clear bar for quality, follow-through, and ownership across the engineers you work with, and make sure work is healthy in production, not just merged.
• Partner with product, implementation, and customer success as the engineer who understands the system deeply enough to push back when requirements are wrong.
• Raise the bar for the engineers around you without slowing the team down.
• The systems and frameworks you set up become the foundation the rest of the backend team builds on.
• Architectural decisions you make now will define how the platform scales over the next several years.
• You will shorten the time from new enterprise requirement to production-ready system, enabling the company to move faster without breaking things.
• You will raise the engineering quality bar for the team through the standards you set, the reviews you run, and the code you ship.
• You will work on problems that don't have obvious solutions, and your judgment will determine the outcome.

Requirements:

• 7+ years of professional software development experience building production systems at real companies.
• CS degree or equivalent (B. Tech/B. E. /B. S. ), strong fundamentals in data structures, algorithms, OS, and networking.
• Can describe the hard problems they have solved, why they were difficult, and what changed as a result, not just a list of technologies used.
• Deep proficiency in at least one backend language; language matters less than depth and engineering judgment.
• Strong system design instincts: can reason through tradeoffs, failure modes, and long-term maintainability under pressure.
• Has set technical direction before: defined architecture, frameworks, or standards that other engineers built on, not just owned their own slice.
• Has driven quality and accountability across a team, formally.