Technical Lead

3.1 Role Overview

Seniority    8+ years total; 3+ years in technical leadership / architect role
Engagement model    Offshore; IST overlap with US ET mandatory
US Client counterpart    Lead Application Architect, UX/UI Design Lead, Product Owner

3.2 Functional Requirements

The Technical Lead owns delivery quality across the entire POD. This person sets coding standards, conducts code reviews, coordinates integration across the three repositories, and is the primary technical interface with US Client's engineering leadership.

•    Own technical delivery of all DaaS Labs sprint commitments end-to-end
•    Lead twice-weekly tech syncs with US Client's architect and product team
•    Define and enforce code review standards across the POD
•    Resolve cross-team integration blockers between mobile, web, and API
•    Participate in sprint planning, contribute to effort estimation and risk identification
•    Translate business requirements into clearly scoped technical tasks for the POD
•    Ensure all three repositories maintain build stability and test coverage standards
•    Escalate architecture decisions to US Client's lead architect; do not unilaterally change patterns
•    Provide weekly delivery status visibility to DaaS Labs Delivery Head and US Client stakeholders

3.3 Technical Requirements

Required — Backend
•    .NET 8 / C# — must have shipped production APIs in the current LTS version
•    ASP.NET Core Web API — RESTful design, versioning, dependency injection
•    Entity Framework Core 9 — query optimization, migration strategy
•    Azure (App Service, Functions, Key Vault, Application Insights, Azure AD / Entra ID)

Required — Frontend
•    React 18+ — hooks, functional components, modern patterns
•    TypeScript — must be comfortable reviewing TypeScript code, not just JavaScript
•    Familiarity with MUI v5 and MSAL authentication flows

Required — Mobile
•    React Native — production experience required; Expo preferred
•    Observable/reactive state management — must be able to understand and review Legend State patterns
•    Sufficient familiarity to identify architecture risks in mobile PRs, even if not the primary mobile developer

Required — Engineering Practices
•    Git branching strategies — must have led team-level Git workflows (feature branches, PR standards, merge strategies)
•    CI/CD pipeline familiarity — does not need to own DevOps but must understand pipeline stages
•    Swagger/OpenAPI documentation standards
•    API contract design — ability to define interface agreements between mobile/web and backend teams
•    Security fundamentals — Azure AD token flows, key management, secure API patterns

Preferred
•    Experience on a prior offshore POD serving a US-based enterprise client
•    Exposure to scheduling, dispatch, or field operations domain (construction, logistics, utilities)
•    Open Telemetry or distributed tracing experience