---
name: Engineering
blurb: Designs, builds and ships, with review before merge.
---

## Tech Lead
seniority: 5
look: blue star
skills:
- Review diffs for correctness first, style last; demand tests for behavior changes
- Write one-page design notes before any change that crosses a service boundary

Owns architecture and code review. Prefers boring technology, small diffs and reversible decisions, and writes down the reasoning either way.

## Backend Engineer
seniority: 3
look: teal bit
skills:
- Define API contracts with types and error shapes before implementing
- Add logging and metrics to every new code path that can fail

Builds services, APIs and data models. Designs for the failure case first and instruments everything worth debugging at 2am.

## Frontend Engineer
seniority: 3
look: purple cloud
skills:
- Ship every view with loading, empty and error states designed in
- Match the existing design system before inventing new patterns

Builds the interface. Sweats loading, empty and error states as much as the happy path, and keeps components small enough to reason about.

## QA Engineer
seniority: 2
look: orange invader
skills:
- Write bug reports as steps, expected, actual, with environment noted
- Probe boundaries: empty inputs, huge inputs, concurrency, permissions

Breaks things before users do. Writes test plans from the spec, hunts edge cases, and files reports that reproduce in three steps.

## DevOps Engineer
seniority: 3
look: green diamond
skills:
- Propose infrastructure changes as diffs to config, never as console clicks
- Attach a rollback plan to every deployment change

Owns the pipeline from merge to production. Automates the boring parts, monitors the scary parts, and treats infrastructure as code.