12yr Fullstack Engineer: UI/UX & 3D Expert 🌟
- $25k+
- Earned
- 2x
- Hired
- 5.0
- Rating
- 53
- Followers
12yr Fullstack Engineer: UI/UX & 3D Expert 🌟
Kajabi Designer & Tech Support for Course Creators
- $10k+
- Earned
- 19x
- Hired
- 5.0
- Rating
- 8
- Followers
Kajabi Designer & Tech Support for Course Creators
Senior Product Designer & No-code Developer
- $5k+
- Earned
- 1x
- Hired
- 5.0
- Rating
- 6
- Followers
Senior Product Designer & No-code Developer
Bringing Strategy + Personality to your brand ✍️✨🤝
- $5k+
- Earned
- 3x
- Hired
- 4.9
- Rating
- 13
- Followers
Bringing Strategy + Personality to your brand ✍️✨🤝
Since December 2024, I have been a content creator (retainer-based), creating 4-5 videos per week for Adopt a Pet. Each week, we reach out to shelters across the country and gather content and stories to feature adoptable dogs and cats and share them on the brand's Instagram and TikTok to drive traffic to their Adoptapet.com (https://Adoptapet.com) profiles.
0
162
Since December 2024, I have been a content creator (retainer-based), creating 4-5 videos per week for Kinship Pets. Each week, I create a mixture of trend-focused and SEO-focused content to be posted to TikTok and Instagram.
0
167
Since August 2023, I have been creating content for SkillPop — an in-person and online learning company based here in Charlotte, NC. SkillPop focuses on accessible, fun classes on tons of topics from art to business to personal development, where you can both learn & connect with people of similar interests.
We worked with this client on full social media management until November 2025.
0
172
2025 was my first year dipping my toes into YouTube sponsorships, and my first client was Circle — a company that I've partnered with for the last 2+ years via Instagram/TikTok AND have hosted my own membership community on since 2022.
This year, we worked on three videos together to share how I've used Circle to create an incredible membership community:
1. Why I chose Circle vs. Facebook Groups
(https://www.youtube.com/watch?v=1355AtUOhP8&t=4s)2. How to increase engagement in a membership community
(https://www.youtube.com/watch?v=KjuTOJ7yr74&t=243s)3. How I used Circle to grow my membership community (https://www.youtube.com/watch?v=0fdcq-yf1mE)
We have weekly videos planned for YouTube in 2026 and are very excited to dip into more sponsored content there as well!
24
339
Principal Engineer & Software Architect | Digital Platforms
- 5.0
- Rating
- 8
- Followers
Principal Engineer & Software Architect | Digital Platforms
Wellos — Healthcare SaaS Frontend Architecture & Scalable Design Systems
Wellos was an emerging healthcare SaaS platform developed within RVO Health. The platform was being expanded to bring capabilities from established wellness programs, including Real Appeal and Quit for Life, into a more flexible, unified product experience.
These programs supported different healthcare needs, including weight management, coaching, activity tracking, and smoking cessation. The challenge was building an architecture that could support distinct customer journeys, integrations, and product branding while making it easier to add programs over time.
I joined the initiative as a Staff Software Engineer, bringing more than a decade of experience designing and implementing shared frontend component systems at scale.
Frontend Architecture & Design System
I helped establish a reusable React and TypeScript component architecture built around React Aria, Class Variance Authority (CVA), and Tailwind CSS.
React Aria provided accessible interaction primitives, while CVA enabled consistent component variants and states. We developed a shared Tailwind styling foundation that teams could adopt across the broader healthcare vertical, letting each team apply its own branding through separate theme configurations.
This approach reduced duplicated implementation work while maintaining consistency across products and giving each program flexibility in its visual identity.
Complex Workflows & Sensitive Data Boundaries
Supporting multiple healthcare programs introduced important architectural considerations. Each program required its own customer journeys, application state, and backend API interactions.
I advocated for explicit state-machine modeling to make workflow transitions and safeguards easier to reason about. When the team chose to keep its existing Redux architecture, I developed a Redux approach that established clearer boundaries between program-specific workflows.
These safeguards helped reduce the risk of unintended cross-program interactions and sensitive healthcare information being sent to unrelated services. Backend authorization and data protection remained separate responsibilities.
Hands-On Frontend Implementation
Alongside the architectural work, I translated Figma designs into React and TypeScript interfaces and implemented much of the shared component system and frontend foundation.
The goal was to give teams reusable building blocks for new features, customer journeys, and branded experiences without repeatedly rebuilding common UI functionality.
Outcome & Impact
I established key architectural patterns and delivered substantial frontend implementation supporting Wellos's planned expansion into additional healthcare programs.
My involvement concluded during a company-wide reduction in force before the broader initiative was completed. The architectural foundation and implementation work I contributed were intended to support continued development and future product expansion.
Technologies: React, TypeScript, React Aria UI Components, Class Variance Authority (CVA), Tailwind CSS, Redux, Figma
Visual Assets: An actual Wellos homepage screenshot, accompanied by conceptual illustrations of the shared frontend architecture, workflow isolation, and reusable component system. The diagrams represent architectural concepts from my work, not original internal documentation.
1
1
172
Building a shared foundation for Healthline Media’s digital products
Healthline Media operated multiple high-traffic digital health properties that had evolved with separate frontend implementations. As new products and experiences launched, that model created duplicated engineering work, inconsistent implementation patterns, and added maintenance overhead.
As a Staff Software Engineer at RVO Health, I helped modernize that architecture around a shared React and TypeScript platform. The work focused on building a reusable engineering foundation that could support multiple products while letting individual experiences retain their own requirements and identity.
From independent implementations to a shared platform
The modernization brought frontend development into a Rush-managed monorepo and established common architecture, shared UI components, Storybook documentation, development tooling, and engineering standards.
Rather than treating each new experience as an independent implementation, teams could build on an established foundation. Teams could develop shared functionality once and use it across products, while keeping product-specific features appropriately isolated.
My contributions included frontend architecture, reusable component patterns, TypeScript adoption, technical decision-making, architectural documentation, development standards, and collaboration with engineering and product teams as the platform evolved.
Architecture designed for reuse
A major goal was to make reuse practical without creating unnecessary coupling between products. The platform provided common foundations for UI, application structure, tooling, testing, and development workflows while leaving room for individual product needs.
This architecture also became strategically important when we developed Real Appeal RX, a new enrollment experience representing a significant business opportunity. Instead of creating another independent frontend and adding to the existing duplication, we extended the shared platform for the new product.Â
Engineering impact
The work's value extended beyond a framework migration. It changed how the organization could deliver new frontend experiences.
Teams gained a more consistent development model, reusable components and patterns, stronger documentation, and a foundation that could evolve across products. New work could begin from established architecture rather than repeatedly solving the same underlying engineering problems.
The result was a frontend platform designed to make future product development faster, more consistent, and easier to maintain.
About the visuals
The live Healthline experience shown here reflects the current public site and may have evolved since my direct involvement. The architecture and transformation diagrams are portfolio representations of the engineering approach and platform modernization work I contributed to during my time at RVO Health; they are not internal company artifacts.
2
242
I’m designing and developing a custom direct-to-consumer e-commerce platform for a family farm bringing its premium farm-raised meat products online. The project is focused on translating the trust, quality, and personal connection of buying directly from a local producer into a polished digital shopping experience.
The work spans UX and visual design, responsive frontend development, e-commerce architecture, product and collection experiences, and the customer journey from discovery through purchase. I’m building the platform around clear product discovery, strong brand storytelling, and a straightforward buying experience that can grow with the business.
The project is currently in development, with the foundation designed to help the farm expand beyond its local customer base while preserving the authenticity and credibility that distinguish a family-run producer.
1
284
Real Appeal RX created an opportunity to solve more than a single product launch. Rather than build another standalone enrollment experience, I led the architecture and development of a reusable platform designed to support multiple healthcare products.
The work consolidated shared enrollment patterns into a React and TypeScript architecture while preserving the flexibility required by individual products. I partnered across engineering, product, design, and business teams to define the technical approach, establish reusable development patterns, and guide implementation.
The resulting platform supported Real Appeal RX, a new enrollment experience tied to a significant business opportunity, while reducing duplicated engineering effort and building a stronger foundation for future enrollment products.
1
260
Full-Stack Developer & Product Designer
View more →
Turning messy business problems into working software.
Turning messy business problems into working software.
Jamie’s Crafty Touch | Ecommerce Website Redesign
A handmade business deserves a website with just as much personality. 🦋
For Jamie’s Crafty Touch, We’ve been redesigning the shopping experience while keeping her colorful, creative brand at the center.
Built with Lovable and connected to Square, the site brings together product browsing, detailed product pages, and a mobile-friendly layout. We’re preparing for final checkout testing and ownership handover.
Watch the video for a look at Jamie’s wreaths, custom apparel, and creations!
Have a website or app that needs some attention? Bring us the messy part.
1
1
154
MessyAPI is a production-ready developer infrastructure platform I built to eliminate repetitive data utility work. It gives developers one API to clean, validate, match, transform, protect, and analyze messy data instead of rebuilding those capabilities for every application.
I designed the platform around real production requirements, including API-key authentication, tenant isolation, usage metering, rate limiting, idempotency, asynchronous jobs, retries, webhooks, observability, and secure data handling.
MessyAPI also includes JavaScript and Python SDKs, OpenAPI, MCP support, CLI tooling, RapidAPI integration, interactive testing, and composable workflows for chaining multiple data operations together.
The goal was simple:Â turn common data infrastructure developers repeatedly build themselves into one reliable API.
1
1
316
I designed and built MessyCare to solve what happens after an AI-built application launches. Instead of waiting for something to break, MessyCare creates a continuous application-care layer covering onboarding, handoff documentation, ongoing support, change requests, maintenance, improvements, and secure ownership transfer. The goal is to give businesses a clear operational record of what was built and one place to keep their applications supported and improving over time. I led the product strategy, UX, workflow design, application architecture, and positioning from concept through implementation.
0
196
I designed and built MessyProof to solve a growing problem with AI-built software: generating an application is getting easier, but understanding what was actually built — and whether it’s production-ready — is still difficult. MessyProof acts as an independent verification layer, analyzing an application’s architecture, dependencies, integrations, changes, security signals, and production readiness. It turns that analysis into a plain-English App Passport backed by evidence rather than assumptions. I led the product strategy, UX, verification model, application architecture, integrations, and go-to-market positioning from concept through implementation.
0
186
I Specialize in Modern, High-Converting Websites.
View more →