Patients, clinicians, and health coaches needed different help from the same product. I built the assistant platform they share, with a member assistant, a clinician assistant, and a health-coach assistant, each limited to the information and tasks that role should have.

• Healthcare assistants
• Role-based access

Found

Clinicians were searching records and writing follow-ups by hand, and the notes varied from person to person. I built an assistant that brings up the relevant chart context and helps clinicians write clearer, more consistent responses.

• Clinician assistant
• Chart review
• Clinical messaging

Found

Prior authorizations were handled by hand by a very small team, from collecting clinical notes and insurance details through submission to insurers. I built the workflow that tracks each authorization through submission, status, and renewal, and pulls a person in for cases that need judgment, such as denials. I also added coverage and billing checks that show cash and insurance options on a member's medication timeline.

• Prior authorization
• Coverage checks
• Billing workflows

Found

Adding registered dietitian care meant a new clinical service the existing consult system was not set up for. I built the core pieces: eligibility checks, scheduling that matches patients with dietitians, visit documentation, and insurance billing for those visits.

• EMR
• Scheduling
• Insurance eligibility & billing

Found

The consult system had been built for one kind of visit. As care expanded, the product had to decide what kind of visit a member needs, who can provide it, what can be covered, and how it is billed. I built that visit workflow, including scheduling, clinician queues, messaging during the visit, coverage checks, and prior-authorization tracking, with a handoff when a person needs to step in.

• Visit workflows
• Scheduling
• Coverage

Found

I built a health-coach assistant with tighter limits on which patient information it can use. It helps coaches plan follow-ups, draft messages, and put together workout and meal plans.

• Health-coach assistant
• Care planning
• Patient messaging

Found

Customers had to contact support to cancel. I built a self-serve cancellation flow that can offer a reason to stay, and a refund flow that follows the terms the customer agreed to.

• Cancellation
• Refunds
• Subscriptions

Found

I built the customer-facing assistant members use day to day. It helps with food questions, app questions, and meal planning, including messages that include photos, and it follows up after periods of inactivity.

• Member assistant
• Nutrition guidance
• Meal planning

Found

Members were cancelling before they had seen what the program could do. I built a churn model that showed which in-product behaviors tend to come before cancellation, and that informed product and outreach decisions.

• Churn prediction
• Retention

Found

Clinicians spent a large part of every visit writing the note afterward. I added drafting support so they start from a note they can review and edit, which cut time per visit and reduced rework when notes were sent on for coverage and reimbursement.

• Clinical documentation
• Clinician review

Found

I built subscription management for web checkout and the mobile app stores, including keeping those records in agreement. Checkout later moved to a dedicated billing provider.

Found

I built a public assessment used to bring people in. I made the results change with the answers, added sharing, and stored the responses on the backend. I worked on both the front end and the backend.

Found

I rebuilt account creation and onboarding, including registrations that were left unfinished.

Found

I was a front-end engineer building a React design system and reusable components used across Edward Jones's internal systems, including money transfers, securities transfers, and financial planning and management features. I integrated the UI with existing backend APIs built by their internal engineers.

• React
• Design systems
• Component libraries
• Financial services

Consulting engagement

I led the front end for GAF's business storefront for roofing shingles, staffing and planning the team and moving it from HTML, CSS, and JavaScript to React, on a .NET Sitecore backend.

• React
• Sitecore (.NET)
• Front-end leadership

Consulting engagement

I led the front end of Elevate, a React platform where brokers and underwriters manage property risk. Instead of waiting on backend services, I designed the API contracts from the front end's point of view and built a mocked API gateway generated from OpenAPI specs. As real services came online and satisfied each contract, they replaced the mocks in place. Both teams could build in parallel, and the API and architecture decisions were settled early. The interfaces were packaged as reusable, versioned NPM modules used by both front end and backend.

• React
• API design
• OpenAPI
• Contract-first development

Consulting engagement

I led the front end and the team for Arrow Electronics' customer-facing product pages and purchasing flow, built in Angular on a .NET Sitecore backend.

• Angular
• Sitecore (.NET)
• Front-end leadership

Consulting engagement

I was the technical lead on this engagement, focused on planning and delivery rather than writing code: breaking work into tasks, shaping requirements, planning the architecture, and running deployments, as the team shipped features on Sentara's existing content system and then moved it to Sitecore.

• Technical leadership
• Architecture planning
• Delivery

Consulting engagement

I led the front end and the team for Lowe's Canada's ecommerce site, staffing and planning the work and integrating its HTML and CSS into Sitecore, on a .NET backend.

• Sitecore (.NET)
• Front-end leadership

Consulting engagement

As a freelancer, I owned this multi-year engagement on my own: a full-stack build on WordPress, with an HTML, CSS, and jQuery front end and a PHP/MySQL back end. After launch, I stayed on in a support role, fixing issues and building new page templates and landing pages.

• WordPress
• PHP/MySQL
• jQuery
• Freelance

Freelance

I led this greenfield build and put the team together myself, hiring the engineers and QA engineers and building the framework from the ground up. We started in Angular 1.5 to meet the initial requirements, and when it wrapped, Fannie Mae followed it with a rebuild of the same product in Angular 2. It was also the first project where I used the backend-for-frontend pattern. On the front end, I built custom extensions to mapping systems, from Google Maps to GIS and property-plot systems, plus the logic that identifies comparable properties within the map's bounds.

• Team leadership
• Angular
• Backend for frontend
• Mapping & GIS

Consulting engagement

I led the front end for a small team building a fully custom ebook reader for the Kingdom of Heaven Library, in Angular 1.5. Readers pick up where they left off, search, save passages, and keep highlights and bookmarks beside the lesson. I also built account creation, access control, and subscription billing in Node.js.

• Angular 1.5
• Node.js
• Access control
• Subscription billing

Consulting engagement

I led the front end of the Mount Sinai site and the team of front-end engineers. I built the front-end design system and the page templates the CMS used, in HTML, CSS, and jQuery, including doctor search, the location chooser, the services list, and the news and stats sections.

• Design systems
• CMS templates
• HTML/CSS
• jQuery

Consulting engagement

I led the Icahn School site and a team of up to six UI developers. I built the front-end design system and the page templates the CMS used, in HTML, CSS, and jQuery, and set up a Gulp build. Pages ranged from simple styled layouts to screens wired to Google Maps and YouTube.

• Design systems
• Gulp
• CMS templates
• HTML/CSS
• jQuery

NavigationArts

I wrote an HTML, JavaScript, and CSS engine for Fresh Match, a timed matching game, and I reused that engine on later games. I built it to move this work off Flash.

BFG Communications

I built Maze Moves and the HTML, JavaScript, and CSS engine behind it. A run started in a random spot, the maps could change, and artists could place pickups and draw paths without being locked to tiles.

BFG Communications

I rebuilt the earlier camel race as Camel Cup. I added new tracks and a freeform map editor so new courses could be laid out quickly.

BFG Communications

I built the Grand Hump Day Derby racing engine in Flash and ActionScript 3. Racers ran a track against a recorded ghost, climbed a leaderboard, and customized a camel, and I made new tracks easy to prototype.

BFG Communications

I built the Camel Mod Garage in Flash. Players set speed, traction, and acceleration, then chose colors and a saddle mark before they started a race.

BFG Communications

I built Mel's Holy Shiitaké Challenge for Mellow Mushroom, from the title screen through the game behind the play button.

BFG Communications

I built Campaign Trail in ActionScript 3 and Flash, on a tree-traversal engine I wrote for it. Players chose a route to Winston-Salem, and finished runs fed a rewards system for the year-long promotion.

BFG Communications

I built Smooth Operator, a Mello Yello quiz. I scored the answers, showed where that score landed, and let people share the result or pick up a ringtone or wallpaper.

BFG Communications

I built a large multi-touch walkthrough of a helicopter engine assembly, for several people to use at once.

Vision 3

I built interactive 3D presentations for a faucet company, using Flash, Unity, and native tools.

Vision 3

I built the PooYou site during a MediaSauce internship. I put up the poll, the product pitches, the newsletter signup, and the links into the downloads and the Facebook app.

MediaSauce

I built the leadership assessment on the Center for Creative Leadership site during a MediaSauce internship. Each question offered a choice, and the flow stepped through the set before it finished.

MediaSauce