Engineering Lead

Project description

Modernization as a Service (MaaS) is a horizontal practice, supporting all business verticals in the company. Core Engineering Lead responsibility: owns the end-to-end engineering process across all account projects. This is the single person accountable for technical outcomes on the account.

• What Engineering Lead does:
  Owns technical risk management across all projects. Ensures critical activities are not delayed or skipped: load and performance testing is planned and executed on time, key integrations are verified early, security reviews are conducted, and infrastructure capacity is validated before major releases. Reviews project roadmaps, WBS, and technical estimates prepared by Solution Architects. Challenges assumptions and identifies gaps. Acts as the technical escalation point for all functional leads and architects.
  
  Defines and enforces engineering standards across all projects: code review policy, CI/CD practices, branching strategy, documentation standards, Definition of Done from a technical perspective. Runs Architecture Review Board (ARB). Reviews and approves key architectural decisions, ensures consistency across projects. Reviews all Solution Architect artifacts: HLD, LLD, integration specs, ADRs. Ensures quality and consistency. Reviews test strategy and works with QA Leads to improve it.
  
  Helps QA Leads strengthen areas where they fall short. Coaches and mentors functional leads and architects. Helps leads strengthen areas where they fall short. Steps in and covers responsibilities of leads or architects when they are underperforming: reviews their deliverables, takes over critical tasks, and works hands‑on until the gap is closed. Monitors technical debt across all projects, prioritizes remediation with PMs.
  
  Drives cross-project reuse: shared libraries, common patterns, lessons learned. Provides Delivery Manager with an independent technical health assessment. Flags risks early. Participates in goal‑setting and performance reviews for all technical roles, bringing the engineering quality perspective. Owns the account's technical strategy: technology direction, competency roadmap, tooling decisions. Interviews lead and architect candidates for their projects and makes hiring decisions.
• What Engineering Lead does NOT do:
  Does not replace Solution Architect on any project. Does not manage project scope, budget, or schedule. Does not write code on a daily basis. This is not a hands‑on developer role.

• 10+ years in software engineering, with at least 3-5 years in a technical leadership role (Solution Architect, Tech Lead, Engineering Manager, or similar). Very strong hands‑on experience in the past. Has led technical delivery on large engagements: 30+ people, multiple concurrent work streams. Has worked across the full stack of project roles: started as a developer, grew into a lead, then into an architect or engineering manager.
  
  Understands each role from the inside. Experience in a consulting/outsourcing delivery model is strongly preferred. Understands client dynamics, onshore/offshore coordination, and delivery pressure. Has managed or closely supervised architects and functional leads, not just developers.

Java, Python, C#