15+ years shipping production systems, frontend through infrastructure. Specializing in legacy modernization, AI integration, and end-to-end product development. Available for contract and fractional engagements through A.Team or direct.
Every consultant claims they can do everything. These are the engagements where my fifteen years actually compound — where deep experience produces meaningfully better outcomes than throwing more bodies at the problem.
Owning a feature from React component through API to database to deployment, without handoffs or "that's not my job" moments. The single-engineer-deep-stack model that lets small teams move like big ones.
Migrating aging PHP, Zend, and monolithic codebases to modern stacks: backend rewritten in Python/FastAPI, frontend rebuilt in React/TypeScript, infrastructure containerized and auto-scaled. SOC2-aware throughout.
Adding OpenAI and other LLM-powered features to existing applications, end to end. Async Python workflows, structured output handling, frontend integration, and the unglamorous production concerns: rate limiting, cost monitoring, fallback behavior, evaluation.
Different problems want different shapes. Pick the structure that matches your situation — or describe what you need and we'll figure out the right fit together.
Defined scope, fixed or milestone-based pricing. Best for migrations, integrations, and well-scoped builds where the destination is clear and the path needs experience to navigate.
Ongoing weekly hours as a senior engineer for teams without one. Best for early-stage startups, teams between hires, or organizations needing senior judgment without a full-time hire.
Architecture reviews, code audits, hiring support, second-opinion calls. Hourly or retainer. The cheap insurance policy for technical decisions you don't want to make alone.
I'm an active A.Team builder. If your team works through them, we can engage that way — same work, same standards, their billing and onboarding flow.
Rates depend on engagement type, scope, and duration. I don't publish them because they're never one-size-fits-all — but I'll quote you within 24 hours of an initial conversation, and I'm happy to share ballpark ranges before we dive into specifics.
A grouped, scannable view of what I work with day-to-day. The split below mirrors how I actually structure work: UI, services, data, and the platform underneath.
I started writing code professionally as a high schooler, redesigning a school district's web infrastructure as an intern. That project earned a regional Excellence in Business Award — and more importantly, taught me early that production software has stakeholders, deadlines, and consequences.
The fifteen years since have been spent in roles where I owned the work end-to-end across the stack: high-traffic news sites, financial-services platform migrations, SOC2-bound enterprise admin consoles, AI-powered systems for live newsrooms. The common thread is depth and accountability. The same person who designs the UI also writes the API, ships the database migration, and owns the deployment.
Based in Medford, Oregon. Available remote. I take on a small number of contracts at a time so each one gets real attention.
I respond within one business day. The fastest way to get a useful answer is to include a few specifics up front.