Engineering Lead and Client Partner

Role overview A player-coach seat that folds three roles usually split across multiple people into one: technical lead on client engagements, project manager for delivery, and the second voice on sales. The position owns architecture end to end, ships a meaningful share of the code, and stands behind the result in front of the client. It is accountable for the revenue the accounts it runs produce, not just delivery health.

Responsibilities - Own architecture and implementation on client engagements across TypeScript services, Python, serverless and containerised workloads, Postgres, event buses, and infrastructure as code. - Ship production code personally, review everything that leaves the team, and set the technical standard for subcontractors. - Run discovery and validation phases, auditing vendor APIs and surfacing capability gaps before they turn into change orders. - Own scope, timelines, exit criteria, and acceptance on phased statements of work. - Run client standups, manage client-side dependencies, and keep engagements on track. - Produce change orders, runbooks, and knowledge transfer material that make handoff clean. - Join discovery calls as the technical authority and translate vague asks into scoped, buildable statements of work. - Size and estimate engagements honestly, including the parts that will be hard. - Grow existing accounts by finding the next problem worth solving rather than padding the current scope.

Requirements - 8+ years building and shipping production software with real depth in at least one of TypeScript, Python, or Go. - Has owned an engagement end to end: scoping, architecture, delivery, and the client relationship. - Fluency in cloud infrastructure on AWS or GCP, including the failure modes rather than just the happy path. - Can hold a technical conversation with a client CTO and a commercial conversation with a client CFO in the same hour. - Strong written communication; writes documents people actually read and decisions people can act on.

Nice to have - Agency or consultancy background where utilisation and margin were also the candidate's problem. - Experience with agentic AI systems or multi-agent orchestration in production. - Enterprise commerce exposure such as Shopify Plus, Salesforce Commerce Cloud, or headless migrations.