
ID · 001
Est. 2001
AJ Barnett
Systems Engineer · Judgment
Product-minded systems engineer·Full lifecycle·Framework-agnostic
I chase problems,not technologies.AI lets me solve more of them.
Twenty years across agencies, studios, fintech, and Fortune 500 engineering, frontend architecture, backend services, system design, and the judgment between them. Technologies expire. Thinking scales.
Breadth,
with depth.
A staff engineer's job is holding the whole product in mind, frontend, backend, systems, the seams between them, and knowing which lever to pull first. Frameworks come and go. These disciplines compound.
How I think- 01
Frontend Architecture
Interfaces designed for change, not for demos. Boundaries first, then components.
- 02
Backend & System Design
API contracts, data shape, service seams. The parts of the product no user sees, but every user feels.
- 03
Product Engineering
Ship the outcome, not the ticket. Own the surface area from problem to release.
- 04
Technical Leadership
Multiply teams. Lower ambiguity. Make the next decision cheaper than the last.
- 05
Design Systems
Tokens, primitives, motion, docs, accessibility, one chapter of the work, not the thesis.
- 06
Accessibility
WCAG 2.1 AA and Section 508 as product quality, verified, never a compliance checkbox.
- 07
AI as Leverage
Claude, Copilot, MCP, and the rest, used to widen the surface I can hold. Execution accelerates. Judgment stays human.
- 08
Engineering Judgment
The compounding asset. Knowing which problems are worth solving, and which tradeoffs to refuse.
The next chapter
is being written.
If your team is building something worth showing up for, I'd love to hear about it.