Description
We are looking for a Tech Lead to own the technical direction of a squad within the Trintech AI Platform — either the Agent Stream or the Platform Team. You own how the squad designs and builds — running design sessions, making squad-level technical trade-offs, and translating the Software Architect’s direction into squad execution. You remain hands-on in code and design, but your primary accountability is the technical soundness of everything the squad ships, not just your own services.
What You’ll Do
Squad Technical Leadership
- Own squad technical direction — run design sessions before implementation, challenge proposals, and ensure services are designed correctly before code is written.
- Primary technical interface between the Software Architect and the squad — translate architectural direction into squad-level implementation decisions across all services.
- Review and challenge low-level designs from squad engineers — identify design debt, scalability risks, and contract inconsistencies before they reach production.
- Own squad-level technical standards — API contract conventions, observability patterns, test architecture, and code quality bar across all squad services.
- Identify systemic quality issues across the squad — patterns of technical debt, repeated design mistakes, and coverage gaps that affect collective delivery quality.
Hands-On Engineering Delivery
- Own and deliver the most technically complex service implementations in the squad.
- Review critical PRs with depth and set the engineering standard through example.
- Own CI/CD pipeline integration, observability instrumentation, and production-readiness gates for squad services.
System Design
- Lead squad-level high-level design sessions — cross-service interaction patterns, failure modes, and data contracts across service boundaries.
- Make system design trade-off decisions independently — latency vs. consistency, synchronous vs. event-driven, shared vs. isolated data models.
- Proactively flag architectural risks — scalability bottlenecks, failure cascade risks, and integration complexity in squad designs before they affect delivery.
Technical Mentorship
- Mentor Principal and Senior Engineers — design reviews as learning sessions, actionable technical feedback, deliberate capability building across the squad.
- Make design reasoning visible and transferable — the squad’s technical level rises because the Tech Lead explains why, not just what.
Who You Are
Python Backend Engineering — Primary Gate
- 10+ years in software engineering with primary depth in Python backend systems — FastAPI, async patterns, service design, error handling, and observability at production scale.
- Low-level system design at lead depth — designs and reviews components, data structures, service internals, and API contracts from first principles. Applies the same rigour to others’ designs as to their own.
System Design — Primary Gate
- High-level system design at working depth — cross-service interaction patterns, failure modes, and data contracts. Leads squad design sessions and makes trade-off decisions independently.
- Distributed systems depth — failure modes, scalability trade-offs, consistency vs. availability, and graceful degradation for shared platform services.
Technical Depth
- Event-driven architecture — message ordering, delivery guarantees, idempotency, and failure handling. Designs and reviews event-driven services with equal depth.
- Multi-tenant data architecture — tenant isolation, data partitioning, row-level security, and cross-tenant boundary enforcement.
- Immutable data design and append-only event patterns — owns at design review level, not just implementation.
- API design and OpenAPI contracts — designs, versions, and governs platform APIs. Contract consistency across squad services is a Tech Lead ownership item.
- SQL and NoSQL at production scale — schema design, query optimisation, indexing, and data modelling trade-offs across service boundaries.
- Kubernetes, Docker, and Helm — production deployment, release engineering, and squad-level CI/CD pipeline ownership.
Awareness
- Security and IAM patterns — OAuth flows and token propagation at service level. Sufficient to identify security gaps in squad designs and escalate to the Platform Architect.
- API gateway and platform integration — how squad services are exposed through the platform layer. LLM and agent service patterns: sufficient to design service interfaces that agent consumers can build against.
Nice to Have
- Workflow orchestration — Temporal or equivalent. AI-native SDLC: Human-led Agentic SDLC practices.
- Azure cloud experience. Experience building audit, compliance, or billing platform capabilities.
What You’ll Learn & Gain
- Squad-level technical ownership on a live enterprise AI platform — design decisions and technical standards that shape the quality of every service the squad ships.
- System design depth accelerated by owning cross-service decisions, running design reviews, and making trade-off calls that service-level IC roles rarely require.
- Technical leadership as a senior IC — growing Principal and Senior Engineers through design review and mentorship, with clear paths toward Staff Engineer, Architect, or Engineering Manager in the Bangalore market.
- Direct collaboration with the Software Architect and Engineering Manager in a fast-moving, squad-based delivery model where technical decisions have immediate, visible production consequences.
If you are a senior engineer ready to own squad technical direction, lead design sessions with confidence, and grow from service-level into system-level technical leadership — we encourage you to apply.
At our core, Trintechers stand committed to fostering a culture rooted in our core values – Humble, Empowered, Reliable, and Open. Together, these values guide our actions, define our identity, and inspire us to continuously strive for excellence in everything we do.
All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin or disability.
