Architect

The Engineering Manager M2 is a senior leadership role responsible for 4–7 scrum teams and up to 50 engineers in Pune — with no intermediate management layer beneath you

This role requires you to resolve complex cross-sub-domain dependencies laterally — with programme managers, product directors, and peer M2s who have equal or greater organisational weight. Managers who default to top-down authority or upward escalation will not succeed at this span.

Skills And Qualifications-Programme Delivery & Governance

Build and maintain a delivery signal system across up to 50 engineers that provides genuine visibility without creating reporting overhead for tech leads

Own programme-level commitments to product directors; communicate slippage risks proactively and accurately before they become crises

Resolve complex cross-sub-domain dependencies laterally — through peer influence, not escalation

Protect delivery capacity from the volume of senior stakeholder requests without creating a black box that erodes trust with leadership

Govern engineering quality across the programme — defining what you measure, who is accountable, and what triggers your intervention

AI & Workforce Strategy

Design a programme-level governance model for AI tooling adoption across 5–7 teams — balancing mandate, architect-led standards, and team experimentation

Place AI risk on the programme risk register with clear ownership

Think explicitly about what AI capability improvements mean for workforce composition, hiring profiles, and team structure over 2–3 years

Proficiency in Python and hands-on experience developing serverless applications using AWS Lambda, AWS SAM, and AWS Step Functions.

Proficiency in Node.js and TypeScript, with experience building scalable backend services and serverless applications using AWS Lambda and DynamoDB.

Experience in React 18, TypeScript, Vite, and Material UI (MUI).

Familiarity with Test-Driven Development, Continuous Integration, and Continuous Deployment (GitHub Actions)

Experience managing large offshore engineering cohorts (40–60 engineers) in a distributed model

Hands-on experience with Kafka and event-driven architecture at production scale

Prior engagement with principal engineers or architects on platform-level trade-offs

Exposure to OA/academic publishing platforms or similarly complex B2B SaaS environments