TechSoft
Playbook menu: Engineering roles

Delivery Playbook · Roles

Engineering roles

Solution Architect / Tech Lead and Software Engineers.

Owner: CTO · Last reviewed: · Next review: 28 April 2027

Engineers design, build and look after the software. The Tech Lead is accountable for technical quality. Every engineer is responsible for the changes they commit, whether they wrote the code or an AI tool helped.

Solution Architect / Tech Lead

TechSoft

Owns technical direction, architecture and engineering quality.

Owns

  • Architecture and integration design
  • Technical decisions and records (ADRs)
  • Technical requirements, constraints and acceptance criteria
  • Code review standards and technical risk
  • Non-functional requirements: performance, security, scalability

Day to day

  • Assesses existing systems before work starts
  • Clarifies business rules and edge cases with the client's team
  • Breaks work into increments that can be released safely
  • Reviews designs and critical code
  • Coaches engineers, including on effective AI-assisted practice

Use of AI: Sets the rules for where AI-written code is acceptable and how it is reviewed. Responsible for the result.

Works with: Works with the Designer on scope, and with the CTO and DevOps on controls.

Software Engineers (backend, frontend, mobile)

TechSoft

Understand the business context, then build, test and ship working software in small increments.

Owns

  • Implementation quality of their changes
  • Understanding the business context of each story
  • Unit and integration tests
  • Technical documentation of what they build

Day to day

  • Ask the client's team about rules and edge cases directly
  • Write or refine the stories for what they will build
  • Implement stories to the definition of done
  • Review each other's changes
  • Fix defects and pay down technical debt
  • Support releases and production issues

Use of AI: Use AI coding tools such as Claude Code to accelerate work. They understand the business context well enough to guide the tool and judge its output, and they test and take responsibility for every line they commit.

Works with: Hand finished increments to QA and the release process.

DiscoverDesignBuild with AIVerifyOperate & improve
Tech Lead / Architect••••••••••••
Software Engineers••••••••••
Not involvedSupportsContributesLeads

Engineering habits

  • Small, reviewable changes: easy to understand and easy to roll back
  • Architecture decisions recorded as short ADRs
  • Tests written with the change, not afterwards
  • Documentation updated in the same change as the code
  • No change is merged that the author cannot explain

Related