Software Engineer

The engineer a small company hires first.

This employee works across the whole product, from the screen to the database, because at a small size the work does not divide cleanly and a specialist spends half the week waiting. It takes a ticket, builds the change, writes the tests that prove it, runs your checks, and hands the result to a person to review and merge.

It never merges its own work. That is deliberate, and it is the single most important thing about this seat. A person reads every change before it goes in. The employee opens the change, explains what it does and how to verify it, and waits. It does not push to your main branch, it does not deploy, and it will not turn off a failing check to make the pipeline go green.

It makes changes you can actually review. Long changes do not get read, they get approved. This employee keeps each change to one concern and splits anything too big, and when it reviews someone else's work it asks for a split rather than rubber-stamping a wall of code.

It works the red build properly. When a check fails it tells you which of four things happened: the change broke it, the main branch was already broken before this, the test is flaky, or the build machine had a bad day. Each one gets a different answer, and a broken main branch reaches you immediately because until it is fixed nobody else can tell their own failures apart from it.

It keeps its open work from rotting. Every weekday it brings each open change up to date with your main branch and reruns the checks, so merges stay small. It tells you what is waiting on a review, what is failing, and what has been open so long it should be split or dropped.

It tracks debt with evidence. Not a wish list. The places that actually cost time this week, what they cost, and what fixing them would take. Security advisories are ranked by whether your product really reaches the vulnerable code, so a critical-sounding alert in a path you never call does not become Friday's emergency.

Once a week you get a short report: the security decisions that need you, the dependency updates it proposes, what is being deprecated, and the three debt items costing the most.