Being an Account Technical Lead¶
Technical quality, honest standards, and the solution that actually fits.
What it is¶
The Account Technical Lead is responsible for the technical quality of what CDS delivers for a client. The solution is fit for purpose. The standards are right. The team is building well, not just building fast.
While the Account Owner manages the relationship and the Account Delivery Lead runs the delivery, the Account Technical Lead is asking the harder technical questions, and making sure they get answered properly.
The role is typically worn by a Lead Engineer.
What you actually do¶
- Lead technical design: the choices that shape the solution, the architecture that has to hold up over time, and the tradeoffs worth making explicit.
- Make tool and technology choices, and make sure those choices are right for the client, not just comfortable for CDS.
- Run regular delivery quality assessments and flag where the bar isn't being met.
- Make sure test coverage is strong and modern: automation where it should be, not as an afterthought.
- Keep the team from gold-plating. High-quality delivery and over-engineered delivery aren't the same thing.
- Work closely with the Account Delivery Lead to make sure technical solutions and delivery plans are aligned.
- Escalate technical risks and blockers to the Account Owner when they need client-level visibility.
- Spot opportunities for the account to evolve technically, and work with the Account Owner to make the case.
What good looks like¶
The solution performs. The documentation is there when someone needs it. The team is building to a standard that CDS would be proud to have scrutinised. You're the person in the room who catches the decision that seems fine today but will hurt in six months, and you say something about it.
What it isn't¶
It isn't delivery management. That's the Account Delivery Lead's responsibility. It isn't a purely hands-on engineering role, though many Account Technical Leads are still writing code. And it isn't a veto on every technical decision: the team should be building their own judgement, with you setting the standard and stepping in when it matters.
The honest bit¶
The technical accountability is real. When something goes wrong with the solution, whether that's performance, reliability, or a design decision that didn't hold, this is the hat that owns it. That's a meaningful responsibility, and it means staying close enough to the work to actually know what's happening.
The behaviours it helps build are central to what we look for at Lead level and above: practitioner excellence, leadership, continuous improvement, client obsession.
Read account leadership for how the Account Technical Lead hat works alongside the Account Owner and Account Delivery Lead.