Developer

Layer: Operational

Scope: Account/Project

Track: see reference/tracks.md — one row per specialization

Mission

Build high-quality software within the project, following the team’s standards and technical direction. This is one role; specializations (the technology stack) are defined per track in reference/tracks.md — the responsibilities below are the same across every specialization.

Responsibilities

• Develop, test and maintain features per requirements and standards.
• Participate in technical design discussions and estimations.
• Write clean, tested, maintainable code; perform peer reviews.
• Collaborate with the Tech Leader and team to meet commitments.
• Continuously improve within their specialization.

Objectives by level

Level	What success looks like
Operational	Assigned work delivered on time, meeting quality and standards.

Reporting & management

• Reports to: Tech Leader
• Manages: No direct reports.

Decides vs. escalates

• Decides: Implementation details within assigned tasks and the agreed design.
• Escalates: Design ambiguities, blockers, and scope or estimate risks.

Requirements

Must have

• Engineering fundamentals
• Proficiency in the specialization stack
• Testing
• Code quality
• Collaboration

Nice to have

• Not specified in the source material yet.

Related documents

Roadmap and career path are defined per specialization — see frontend.md, backend.md, devops.md, qa.md, and each one’s linked roadmaps//career-paths/ file. Evaluation criteria per specialization is not defined yet.