/index · independent engineering practice
We build unusual systems, automate ugly workflows, connect things that were never designed to connect, and fix software that has become fragile, slow, or unsafe.
Colorado / available remotely across the U.S.
A screenshot-driven operations agent became a deterministic browser workflow, with model reasoning retained only where ambiguity required it.
technical record →61.7s → 4.8s median execution
A small integration layer reconciled incompatible models, incomplete APIs, and side effects that could not safely happen twice.
technical record →11 hr/week → <30 min manual reconciliation
An unstable AI prototype was rebuilt around bounded model behavior, explicit state, evaluations, and observable deterministic code.
technical record →p95 latency: 18.4s → 3.1s
An application-security review continued through patches, regression coverage, and verification instead of ending at a findings report.
technical record →3 critical / 7 high findings identified
Instrumentation and behavioral tests made a fragile legacy service understandable enough to repair incrementally.
technical record →37 incidents/quarter → 2
Applications, backend systems, APIs, integrations, legacy rescue, and performance.
software engineering →Workflow automation, agents, browser control, AI systems, evaluations, and orchestration.
automation engineering →Application security, architecture review, hardening, remediation, and security automation.
security engineering →/why
01 / ASSESS
Understand an ugly system, bottleneck, or risk before committing to a larger project.
02 / TEST
Test an uncertain technical approach with the smallest useful implementation.
03 / BUILD
Build, repair, automate, integrate, or secure a clearly bounded system.
04 / ADVISE
Senior engineering judgment without adding another full-time role.
A model is useful when a step is ambiguous. Most interface navigation is not.
Instrumentation changes a legacy-system decision from opinion into evidence.
A severity label is not remediation guidance, and a finding is not finished when the PDF ships.
/contact
You do not need a complete specification. Explain what you are trying to build, fix, automate, integrate, or secure.
[ start a technical conversation → ]
Prefer email? [email protected]