Multi-source data + structured LLM evaluation
Job Search Command Center
A privately operated system that turns inconsistent ATS feeds into a normalized, cost-aware application workflow with explainable recommendations.
Read the case studyFull-stack engineering · customer solutions
I work across discovery, architecture, APIs, data, frontend delivery, testing, rollout, and production support—especially where the problem is still taking shape.
Selected systems
These systems are private and actively operated. The case studies expose the problem, architecture, decisions, tradeoffs, and verification evidence without exposing private data.
Multi-source data + structured LLM evaluation
A privately operated system that turns inconsistent ATS feeds into a normalized, cost-aware application workflow with explainable recommendations.
Read the case studyOne task workflow across browser and chat
A private task platform that keeps browser actions, Telegram commands, reminders, and scheduled check-ins on one durable domain model.
Read the case studyHow I work
Forward deployed engineering is less about a title than an operating model: learn the domain, reduce ambiguity, build the right system, and stay accountable after launch.
Clarify the real workflow, users, constraints, and success criteria before prescribing architecture.
Shape data contracts, APIs, integrations, state transitions, and failure boundaries that teams can reason about.
Build across Rails, React, Next.js, TypeScript, Python, SQL, and third-party systems with tests alongside the work.
Own rollout, monitoring, cost controls, support paths, and the tradeoffs that appear after a system meets production.
Experience
My path runs from field engineering to full-stack delivery. The common thread is diagnosing real operating conditions, communicating clearly, and making the system work.
Delivering production software across healthcare, pharmaceutical, real-estate, and enterprise client environments.
Built mobile healthcare experiences and helped establish frontend architecture.
Field engineering in high-stakes operating environments before moving into software.
About
Before software, I worked as a petroleum engineer in operating environments where technical decisions carried real cost and schedule consequences. That background still shapes how I work: understand the system, make risk visible, and communicate with the people closest to the problem.
Since 2021, I have worked remotely while traveling the US and Canada with my wife and our two cats. It is a human detail, but also evidence of the adaptability and ownership I bring to distributed teams.