Technical Lead React & .NET India Remote US shift

Position title
Technical Lead — React & .NET
Department
Engineering & Delivery
Reports to

Head, Project Management Office / Delivery Manager
Direct reports

4–8 engineers (developers and QA), matrixed by project
Location
Remote, within India
Working hours

US shift — see Section 7 for the overlap requirement
Experience required

Minimum 5 years in React and .NET delivery, including team-leadership exposure
Employment type
Full-time, permanent
1. About PATeam Software Consulting

PATeam Software Consulting Ltd. delivers custom software product POS (ModusTech) and process-automation solutions for clients across the United States, the United Kingdom and Europe. Our delivery model is engagement-led: small, accountable teams work directly with client stakeholders from discovery through to go-live and hypercare, under a Project Management Office that holds the schedule, quality and governance line.

We are strengthening our engineering leadership bench and are looking for a Technical Lead who can own the technical outcome of a React and .NET engagement end to end inclusive of writing code, guiding a team, and standing confidently in front of the client.
2. Role Purpose

The Technical Lead is accountable for the technical quality and on-time delivery of assigned React and .NET projects. This is a hands-on leadership role: roughly half the week is spent on design, code and review, and the remainder on guiding the team, planning sprints, managing dependencies and communicating with client stakeholders.

Success in this role means predictable delivery. Commitments made at sprint planning are met, risks are raised early rather than explained late, the codebase remains maintainable as the team scales, and the client regards you as the technical authority on the engagement.
3. Key Responsibilities

3.1 Technical leadership and hands-on engineering

Own the solution architecture for assigned projects across the front end (React) and back end (.NET), including component structure, API contracts, data models, authentication and integration patterns.
Contribute production code for the most complex or highest-risk parts of the solution, and set the standard the rest of the team follows.
Run code review as a quality gate — enforce coding standards, review pull requests within agreed turnaround times, and coach through review comments rather than simply rejecting work.
Make and document technical decisions with the trade-offs stated, so that choices can be revisited later without re-litigating them from scratch.
Own non-functional quality — performance, security, accessibility, scalability and maintainability are treated as delivery requirements, not afterthoughts.
Manage technical debt deliberately by maintaining a visible register and negotiating remediation into the sprint plan.
3.2 Agile delivery and schedule control

Lead sprint planning, estimation and backlog refinement with the Product Owner and Project Manager, and hold the team to realistic, defensible commitments.
Break down requirements into stories and technical tasks with clear acceptance criteria and identified dependencies.
Protect the delivery date — track sprint burndown daily, identify slippage the day it appears, and propose concrete recovery options (scope, sequence or capacity) rather than escalating without a plan.
Facilitate daily stand-ups, sprint reviews and retrospectives where the Scrum Master role is not separately staffed, and act on retrospective outcomes.
Maintain accurate delivery status for PMO reporting, including RAG status, milestone confidence, risks, issues and change requests.
Manage release readiness — go-live checklists, cutover planning, rollback provisions and hypercare support arrangements.
3.3 Team leadership and development

Lead a team of 4–8 engineers across development and QA, allocating work to match capability and stretch goals.
Onboard and mentor engineers through pairing, design walkthrou