I lead engineering teams. I still build.
I lead technical teams and build software. I help people take ownership of what needs doing. And I stay involved long enough to check what ships.
I’ve spent more than 20 years building software and websites, with design and the work people need to do shaping the technical decisions.
I help engineers take ownership of their work, including the decisions around it. We work through priorities and dependencies with other teams, and I stay involved in implementation.
I also build independent products. They keep me working through the implementation details, starting with something a person needs to do.
Read my resumeI set direction and stay involved in getting the work out.
Website Manager · Sep 2020–present
I lead web engineering and conversion rate optimization at JumpCloud. I coach engineers and help them take technical ownership, with quarterly priorities shaped alongside Marketing, Product and RevOps. My work includes Pardot-to-Marketo integration and Vue modernization. I also introduced AI workflows for the team.
Senior Software Engineer / Full Stack Developer
Feb 2019–Sep 2020
I refactored a content API using AWS Lambda with Node.js and GraphQL. I extended headless WordPress with React and Gatsby, and contributed reusable web components and automated tests.
2002 onward
More than two decades building websites and software, including the integrations and operational work needed to keep them running.
Clear priorities help a team deliver.
The product still has to solve a problem.
Here’s the work, including the choices behind it. Some projects are in production. Others are prototypes or internal builds, with their status noted below.
At JumpCloud, I balance modernization with growth work. I set priorities and develop technical ownership while staying involved in delivery.
Website Manager · September 2020–present
Read the leadership case study ↗I built TIbot to connect team intake with delivery in Slack and Jira. It checks for duplicates and protects updates, with approvals for guarded changes.
Built and in use · Public overview
Read the automation case study ↗I built PolyshOS to connect public booking with the work salon staff do around an appointment. My work covers the web application and API, background worker and native clients.
Web/API/worker production · Native internal testing
Read the PolyshOS case study ↗A website has to work
for the team behind it, too.
A website needs to serve visitors while giving the people running it a system they can maintain.
I’m Website Manager at JumpCloud, leading web engineering and conversion work. I coach engineers and help them take technical ownership. Alongside setting priorities, I stay involved in implementation, including Vue modernization and Pardot-to-Marketo integration, reusable components and the systems behind content and measurement.
At TrainingPeaks, I helped refactor a content API using AWS with Node.js and GraphQL. I also extended headless WordPress with React and Gatsby, and worked on reusable components and automated tests.
Connect the workflow.
Keep decisions accountable.
I build agents around the work they need to do and the decisions that still belong to people.
My specialist workflows cover intake and audits, then planning, engineering, security and delivery. TIbot connects that work in Slack and Jira through webhooks and schedules. It checks for duplicates, protects updates and asks for approval where needed. Reusable skills carry the work into implementation and review, with a handoff when it’s ready.
I’m developing Agent Workflow Learning to test instruction changes against what happened during execution. PageInsights is separate. It looks at where visitors encounter friction on a page.
Search with sources.
Booking with conflict checks.
Search needs to lead back to source material. Booking needs to account for what’s already on the calendar.
For House of Destiny, I built a WordPress search beta using OpenAI embeddings and Supabase vector retrieval alongside keyword matching. Summaries draw on source material that visitors can inspect. The application also includes filters and caching, with analytics around search.
I also built a scheduling system that connects Google Calendar and iCloud CalDAV. It handles availability across time zones and creates meetings, with locks and request identifiers to track requests. Conflict checks and recovery handle the cases where booking gets less straightforward.
Bilt:Spec keeps a vehicle’s history and modifications with its photos and the story behind the build.
Build profiles bring together modifications and dyno results, with photography and QR sharing. I also built event workflows for organizers, including judging and offline support.
Publishing has
a lot of edge cases.
CrossPost handles media transfers between social platforms, including the platform rules that complicate them.
I built OAuth connections and ordered carousels, with JPEG normalization and optional FFmpeg processing before chunked TikTok uploads. The application uses R2 for media storage. Diagnostic history and delivery states help explain a failed transfer.
The business behind
the appointment.
PolyshOS connects salon booking with staff calendars and waitlists, including the operational work around each appointment.
The platform supports multiple tenants and role-based permissions. Its web application and API share a data model with the background worker. A native SwiftUI companion is in development.
Dictate without
leaving your work.
Mumbl puts locally recognized speech into the work you’re already doing, with limits on how cleanup can change the text.
I built Mumbl in SwiftUI for macOS and iOS. It has a compact HUD and keyboard workflows, with a personal dictionary. Recognition options include Apple Speech and optional Parakeet Core ML, plus WhisperKit.
When implementation gets faster, choosing what to build still needs care.
I balance growth work and modernization with reliability and technical debt. A roadmap needs to reflect the team’s capacity and who will own delivery.
For a product, I start with what someone needs to do. That might be finding a source or booking an appointment. With Mumbl, it’s dictating without losing your place.
My workflows carry discovery and planning into implementation. Testing and release are part of that work. Each specialist gets a defined task and the context for it, with clear ownership when work runs in parallel.
Approvals and guarded updates keep consequential decisions with people.
Before work advances, I require evidence that it’s complete and an independent review. A working prototype helps test an idea. Getting it ready for production also requires testing and an owner, with a way to recover if something goes wrong.
I describe prototypes and isolated tests by what they establish. They answer narrower questions than a production rollout.
I’m developing a framework that records execution reviews and feedback. It compares proposed instruction changes against a baseline before a decision to adopt or roll back.
The framework tests whether workflow changes help. It does not train model weights.
Tell me what your team needs to build, or where the work is getting stuck.