Tech Leader
Layer:
OperationalScope:
Account/Project
Mission
Section titled “Mission”Lead the technical execution of one or more projects, ensuring deliveries meet timelines, quality and standards while guiding the development team.
Responsibilities
Section titled “Responsibilities”- Lead the day-to-day technical execution of the project(s).
- Ensure deliverables meet timelines, quality and defined standards.
- Make project-level technical and design decisions.
- Guide, review and unblock Developers (code review, direction).
- Coordinate with PM and clients on scope, estimates and risks.
- Apply architecture standards; escalate gaps and risks.
- Mentor the Developers on the team.
Objectives by level
Section titled “Objectives by level”| Level | What success looks like |
|---|---|
| Operational | Deliveries on time, on quality, following standards; the team stays unblocked. |
| Tactical | (contributing) Feeds improvements upward; develops the team’s skills. |
Reporting & management
Section titled “Reporting & management”- Reports to: Tech Manager
- Manages: Developers (~3–5) — technical leadership.
Decides vs. escalates
Section titled “Decides vs. escalates”- Decides: Project-level technical & design decisions, task breakdown, technical priorities.
- Escalates: Resource / timeline conflicts; cross-project or architectural decisions.
Requirements
Section titled “Requirements”Must have
Section titled “Must have”- Hands-on technical expertise
- Project solution design
- Code review
- Mentoring
- Client communication
- Scope management
Nice to have
Section titled “Nice to have”- Not specified in the source material yet.
Related documents
Section titled “Related documents”- See
reference/career-levels.mdfor how every track’s ladder reaches this role. - Career path and evaluation criteria specific to this role are not defined yet.