Principal Engineer L5
Shapes how KODE builds software for years, not just this quarter.
What we expect at L5
| Scope | The engineering organization as a whole, its long-term technical strategy, and how technology supports KODE's business strategy. |
|---|---|
| Independence and judgment | Works through highly complex and ambiguous problems to deliver concrete, actionable solutions, and is the escalation point for the hardest technical problems. Makes and explains the hardest technical calls, including what not to build. |
| Technical skills | Sets the platform's architecture and long-term technical direction, including major infrastructure and build-versus-buy decisions. Defines technical best practices and processes. |
| AI-assisted delivery | Defines how AI changes the way KODE builds, and keeps that aligned with our security and compliance commitments. |
| Quality and review | Sets the standards that make quality everyone's job, and shows them in their own work. |
| Communication and influence | Very high influence across the company. Advises on promotions into technical leadership, and represents KODE outside the company, such as at conferences, in published writing and in the Rails community. Direct reports are not required. |
At every level
Every engineer's work gets reviewed, whatever their level, and leading a project is an assignment, not a promotion. Read more on the engineering overview.