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 walkthroughs, structured feedback and clear technical direction. Set and monitor engineering standards for branching, testing, documentation and definition of done, and hold the team to them consistently. Conduct performance conversations and contribute to appraisals, development plans and capability assessments in partnership with the reporting manager. Reduce single points of knowledge by insisting on documentation and deliberate cross-skilling within the team. Support recruitment through technical screening and interview panels. 3.4 Client engagement and stakeholder management Act as the technical point of contact for US and other international clients, translating technical positions into business language and business needs into technical requirements. Run technical discussions and demonstrations with client architects, product owners and executive sponsors, and present options with a clear recommendation. Manage scope conversations professionally - recognise change when it arrives, quantify its schedule and effort impact, and route it through the agreed change-control process. Communicate proactively across time zones so that a client starting their day has the update they need without having to ask for it. Build client confidence by being candid about risk and consistent in follow-through. 3.5 Governance, quality and process Comply with PMO governance including project documentation, stage gates, sign-offs, time recording and audit evidence. Own the test strategy for the engagement across unit, integration, end-to-end and UAT layers, in partnership with QA. Maintain CI/CD discipline — automated builds, quality gates, environment management and repeatable, low-drama deployments. Contribute to continuous improvement by feeding lessons learned and reusable assets back into organisational practice. 4. Essential Skills and Experience Candidates must be able to evidence all of the following. 4.1 Experience Minimum five years of professional software delivery experience with React and the .NET stack, including at least two years in a technical lead, lead developer or equivalent leadership capacity. Demonstrable record of leading a delivery team to release on a committed schedule, ideally across multiple projects or engagements. Hands-on experience working directly with international clients, with the United States preferred, in a consulting, outsourced or product-engineering setting. Experience delivering within Agile frameworks (Scrum or Kanban) throughout the full lifecycle — requirements, design, build, test, release and post-go-live support. 4.2 Front-end technical skills Strong command of React, including hooks, component composition, state management (Redux, Zustand, React Query or equivalent) and performance optimisation. Proficiency in JavaScript and TypeScript, with modern tooling and build pipelines. Competence in HTML5, CSS3 and responsive design, and familiarity with a component library or design system. Front-end testing practice using Jest, React Testing Library or comparable tooling. 4.3 Back-end and platform skills Strong command of C# and .NET (.NET 6 or later, and ASP.NET Core), including RESTful API design and layered or clean architecture patterns. Working knowledge of Entity Framework Core or a comparable ORM, plus SQL Server or an equivalent relational database, including query performance tuning. Practical experience with cloud services — Azure preferred, AWS acceptable — covering application hosting, identity, storage and messaging. Version control with Git and branching strategies suited to team delivery, plus CI/CD pipeline configuration (Azure DevOps, GitHub Actions or equivalent). Sound grasp of application security fundamentals, including authentication and authorisation patterns such as OAuth 2.0, OpenID Connect and JWT. 4.4 Leadership and delivery competencies Ability to lead by influence as well as authority, and to hold a team to standards without damaging morale. Disciplined approach to estimation, dependency management and schedule control under fixed-date pressure. Clear written and spoken English, sufficient to hold an unscripted technical conversation with a senior client stakeholder. Sound judgement on when to decide, when to consult and when to escalate. 4.5 Working arrangement Willingness and availability to work United States hours on a sustained basis, including participation in client ceremonies scheduled in US time zones. A reliable remote working setup, including stable high-speed connectivity and a quiet environment suitable for client calls. 5. Desirable Skills and Experience Microservices, containerisation (Docker, Kubernetes) or event-driven architecture in production. Exposure to process automation or RPA platforms, or to integration-heavy enterprise environments. Certification in Azure (for example AZ-204 or AZ-305), Scrum (PSM or CSM) or SAFe. Experience with Next.js, GraphQL, micro-frontends or mobile delivery. Experience operating within a formal PMO governance model, including stage gates and audit requirements. Presales or solution-estimation experience, such as contributing to proposals or technical responses. Bachelor's degree in Computer Science, Engineering or a related discipline. 6. Behavioural Expectations We assess these as rigorously as the technical criteria. Accountability. Owns the outcome, not just the assigned task, and does not require chasing. Candour. Raises bad news early and factually, with options attached. Composure. Remains measured under delivery pressure and during escalations. Client orientation. Understands that the client is buying confidence as much as code. Developing others. Treats the growth of the team as part of the job, not a distraction from it. 7. Working Hours and Shift Arrangement This role supports clients in United States time zones. The expected working pattern will be set out as per specific client engagement at the point of offer.