Jacob Prudent
Engineering Lead, Telehealth CommerceEngineering Lead, Telehealth Commerce · flag on
Kennewick, WA, USA [email protected] Phone available on request LinkedInlinkedin.com/in/jacobprudent GitHubgithub.com/prudentj jacobprudent.com
- Serving
trueto 100% of visitors- Rollout
- 100%
- Scope
- 4 yrs telehealth commerce2 platforms led6 engineers
- Fallback
business· facts unchanged
Profile
Engineering lead with six years in software, four of them in telehealth commerce. Leads Telegra’s Commerce team of six engineers plus QA, with product responsibility for the patient-facing platform: white-labelled storefronts, checkout, subscriptions and patient dashboards. Previously Director of Technology at Invigor Medical, a telehealth e-commerce company. Works specification-first, using AI-assisted development with human review of every change. Came to software from laboratory science.
Current workCurrently
I lead the build-out of Telegra Commerce. The platform previously relied on a WooCommerce plugin; it now has its own end-to-end e-commerce solution, tracked from storefront to fulfilment. We are now building the layer above it: a client-facing API, MCP servers and rebuilt patient intake, so partners can launch their own white-labelled telehealth service.
My role has shifted from writing features to defining them and reviewing what ships. In a regulated space, where mistakes reach patients, clear scoping and a firm quality bar matter more as the team speeds up.
MERN stack (MongoDB, Express, React, Node) · TypeScript
cv.pdf was moved to the Trash. This page is the CV now.
- 2026 – present
Telegra
US telehealth platform for clinics and brands · Remote / Kennewick, WA, USA
Commerce Team Lead
Lead the Commerce team of six engineers, with product responsibility for the patient-facing platform.
- Lead a six-person engineering team based in India, plus QA: write the specifications, plan the sprints, review and merge all code, and sit on hiring panels.
- Led the build-out of Telegra Commerce, replacing reliance on a WooCommerce plugin with an end-to-end platform tracked from storefront to fulfilment; specified the renewals engine the team built.
- Led the one-page checkout from specification to release; review caught four release blockers, including a security issue.
- Built a self-service tool to reprice and reissue invoices for closed billing periods, replacing manual corrections for clinic customers.
- Responsible for production: releases, incidents and data fixes.
- Set up the team’s AI-assisted development workflow: specification-first tickets, and no merge until a person has reviewed the full change.
MERN (MongoDB · Express · React · Node.js) · TypeScript · Next.js · Redis · BullMQ · Stripe · AWS
- Sep 2022 – Apr 2026
Invigor Medical
US telehealth e-commerce company
Director of TechnologyJan 2024 – Apr 2026 · Pasco, WA, USA
Technical owner of a telehealth e-commerce platform running prescription subscriptions.
- Primary technical owner across WooCommerce, Zoho CRM, EHR, e-prescribing and payment systems.
- Co-led the build of a React and Node.js prescription commerce platform integrating intake, payment and prescription routing.
- Built and maintained 15+ production automations for order routing, patient intake, billing triggers, subscription recovery and cross-system status sync.
- Implemented prescription routing by state, medication type and pharmacy capability.
- Designed delayed-capture payments so patients were charged only after a clinician approved the order, running Stripe and Authorize.Net side by side for resilience.
- Delivered executive reporting on revenue, cancellations and fulfilment.
Zoho (Deluge, Flow) · WooCommerce · WordPress · React · Node.js · Stripe · Authorize.Net · Segment · Metorik
Full Stack DeveloperSep 2022 – Jan 2024 · Kennewick, WA, USA
Automated operations in Zoho Deluge; built a React/Node patient dashboard.
- Oct 2020 – Dec 2021
Pathwright
US online learning platform · Remote
Full Stack Developer (contract)
Contract developer: built a hypertext parser and rich-text editor in React, TypeScript and Slate.js, and prototyped features for the product team.
- Jun 2020
Lambda School
US coding bootcamp · Remote
Section Lead
Mentored eleven team leads, each supporting 5–12 students.
- Aug 2017 – Sep 2019
Earlier career
Microbiologist, Tyson Foods (Sep 2018 – Sep 2019); Research Assistant, Santa Cruz Biotechnology (Aug 2017 – Aug 2018).
Education
- 2016BSc Biochemistry, Brigham Young University–Idaho (US)
- Oct 2019 – 2020Lambda School (US coding bootcamp), full-stack web development
Skills
- Languages & frameworks
- TypeScript, JavaScript, React, Next.js, Node.js, Express
- Data & infrastructure
- MongoDB, Redis, BullMQ, AWS, Docker, Jenkins
- Payments & integrations
- Stripe, Authorize.Net, EHR and e-prescribing, webhooks, REST APIs
- Leadership & delivery
- Agile delivery, specification writing, code review, stakeholder management, roadmap planning, incident management, AI-assisted development (Claude Code)
Selected work
- One-page checkoutSpecified, reviewed and released with the team. Review caught four release blockers, one of them a security issue. Live since October 2026.
- Billing correction toolA reprice-and-reissue tool for closed billing periods on Stripe Billing. Corrections no longer need a manual reissue.
- Analytics reconciliationReconciled a client’s conversion funnel against their own data. Our figures matched theirs to within 0.5%.
ApproachHouse rules
-
Specify before building
Requirements become tickets the team can build without further questions. 27 product requirement documents became epics this year.
-
Verify
Reported numbers come from scripts that can be rerun, not from summaries. A suspected cross-client data leak was disproved from delivery records before anyone escalated.
-
Change production carefully
Back up, dry run, guarded write, verify, keep a revert. Incidents get evidence before a fix.
-
AI-assisted, personally accountable
Most of my code is written with Claude Code. I decide what is built, review every change and answer for what ships. I also practise without it.
Show and tell
What the work looks like up close. Synthetic examples, no real data.
- Node.js
- TypeScript
- React
- Next.js
- MongoDB
- Redis
- Stripe
- AWS
- Docker
- Claude
Renewals: retry a failed charge with backoff, then alert
- Given a declined renewal, retry at 1, 3 and 7 days
- Given three failures, mark past due and alert the clinic
- No second charge if a retry and a manual payment overlap
- await subs.updateMany({ _id: { $in: ids } }, patch)
+ await subs.updateMany({ _id: { $in: ids }, status: 'past_due' }, patch)Review: Only write records that still match the expected state. The dry run counted 41; assert that before writing.
- checkoutJourney completed, payment authorised
- clinician reviewApproved; payment captured only now
- pharmacyRouted, filled, label created
- shippedTracking pushed to the patient dashboard
- deliveredRenewal scheduled
- Back upCopy every record the change will touch.
- Dry runCount what it would change, write nothing.
- Guarded writeOnly touch records still in the expected state.
- VerifyRe-read and compare with the dry run.
- Keep a revertA tested script that restores the backup.
Illustrative shape, not data. The real result: our figures matched the client's to within 0.5%.
Synthetic examples: invented identifiers and code, in the shape of real work. No company, client or patient data.
Off the record
The background is Conway’s Game of Life, after a 2020 build-week project.