Lead Full Stack Engineer

MegazoneCloud US

MegazoneCloud is looking for a Lead Software Engineer to own technical direction on complex, multi-vendor cloud programs that modernize legacy applications and manual processes into agentic, event-driven architectures on AWS. These are large enterprise engagements, frequently in regulated industries, with multiple delivery teams, partner vendors, and a client organization that expects its technical lead to be in the room and accountable.

This is a hands-on technical leadership role, not a people-management one. You will not carry headcount or own career development. What you will own is the technical direction of the program: the target-state architecture, the quality of what multiple teams ship against it, the design decisions that get made and recorded, and the confidence of the senior client stakeholders who are funding the work.

The engineers around you will write most of the code. You will review it, shape it, and write the parts that set the pattern — which means staying technical enough to be credible with the people doing the building and clear enough to be credible with a VP who wants to know why the schedule moved.

• Own the target-state architecture for the program: event-driven and agentic designs built on Lambda, Step Functions, ECS Fargate, API Gateway, DynamoDB, S3, EventBridge, and Bedrock.

• Make and defend service selection, integration pattern, and design tradeoff decisions, grounded in distributed systems fundamentals and the AWS Well-Architected Framework.

• Set the engineering standards multiple teams deliver against — patterns, contracts, testing expectations, and the definition of done.

• Stay hands-on where it counts: reference implementations, architecture spikes, and the hardest technical problems your teams surface.

• Review code and technical artifacts — Python, Node.js/JavaScript, Terraform — with enough depth to give meaningful design-level feedback, not surface commentary.

• Contribute to and review REST and GraphQL API contracts, assessing consistency and completeness and identifying integration issues before development begins.

• Critically review FRDs, BRDs, and functional specifications — surfacing gaps, ambiguities, and technically infeasible requirements early, and translating business requirements into precise platform deliverables.

• Participate in architecture governance — ARB or equivalent — as the person who prepares the submission and answers for it.

• Engage senior client stakeholders at VP level and above, face to face, as the technical voice of the program.

• Translate between business and IT audiences at varying levels of seniority without losing precision in either direction.

• Produce the written record the program runs on: architecture decision records, decision logs, design documentation, and status reporting that an executive can act on.

• Coordinate technical delivery across multiple teams, partner vendors, offshore development groups, and specialist analytics firms.

• Hold vendor output to the same technical bar as internal work, and escalate credibly when it falls short.

• Run the program's technical cadence within an Agile delivery model — Scrum or Kanban — across teams that do not all report to the same place.