A Professional Owns the Whole Outcome
Professionalism in software isn't process, titles, or looking the part. It's owning the whole outcome — the cost, the failure, the 3am page, the wrong call.
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
Writing · Tag
4 posts on staff engineer. Or browse the full writing index →
Professionalism in software isn't process, titles, or looking the part. It's owning the whole outcome — the cost, the failure, the 3am page, the wrong call.
Fifty prompts I use to ship production AI features, debug distributed systems, and write docs that don't rot. Code review, debugging, refactoring, system design, and PR-quality writing — with five full examples.
The title 'Staff Engineer' means three different things at three different companies. At an AI startup pre-Series-A, only one of those three is what you actually need. The screen, the take-home, the interview loop, and the AI-fluency calibration that's now table stakes.
A fractional engineering engagement starts with a codebase you've never seen. You have ninety minutes to form a useful POV before the kickoff call. The seven-step triage I run, the two questions I bring back to the founder, and how AI tooling has accelerated the process.