Systems
Legible under pressure
Architecture that keeps ownership, state, and failure modes clear when work speeds up.
Technical side
Operator, architect, builder.
I work where systems architecture, local-first AI, workflow design, customer empathy, risk mitigation, and commercial pressure meet. I like environments where there is room to improve the system itself, not just work around it.
What I help with
Design the system, clean up the handoffs, and keep automation useful when the work gets real.
Workflows
Safer automation
AI-assisted flows with boundaries, review points, and outputs people can trust.
Delivery
Commercially aware execution
Hands-on building that respects adoption, customer friction, and the cost of getting it wrong.
Technical cockpit
This side is for the deeper answer: stack choices, operating posture, how I think, and where the value comes from, presented as cleaner tiles instead of draggable windows.
proof / impact
what has already shipped
Numbers with context
$6.8M net-new ARR
Atlassian growth motion with real commercial pressure and scale.
22% faster time-to-value
Onboarding redesign that made adoption clearer and faster.
40% less validation overhead
Tooling that cut repeated manual checks out of the loop.
Current build lane
Master OS proves the systems thinking is live, not hypothetical.
stack / posture
how it is built
Current stack
- local models plus selective frontier services
- BrowserOS and review-first browser work
- Linux, Git, APIs, observability, and workflow automation
- guardrails, approvals, and visible outputs over black-box motion
local-first
browser workflows
bounded AI
operator-led
notes / recruiter mode
fast answers
Useful answers, quickly
What do you actually do?
I design systems that reduce ambiguity, speed up execution, and make AI useful in real operating environments.
Why does this matter?
Most teams do not need more tools. They need clearer handoffs, safer automation, and systems people can trust.
What is your edge?
I combine architecture, operator empathy, commercial awareness, AI systems judgment, and a habit of actually shipping.
fit / role map
where I work best
Strong fit
- AI systems architecture
- platform engineering with automation scope
- internal tooling and workflow design
- hands-on architecture with real ownership
Less interesting
- endpoint admin with no design authority
- ticket-heavy support with no route to fix the system
- architecture jobs where execution is blocked by layers of theatre