Selected products, each with the problem, the build, and the outcome.
Clinics lose money when the visit, the coverage check, and the claim live in different tools. I built that loop as one CodeSync product, with each clinic’s rows isolated, on Next.js, Supabase, and tenant-safe Postgres.
Front desk and billing share one visit and coverage record, so an operator can go from the calendar to a claim without retyping the patient.
Associate Product Engineer
The public editorial product: CMS-backed Work and Writing, no static fallback catalog, and no service-role key in the public app.
Founders, recruiters, and engineers get one evidence-led path from positioning to shipped systems, technical depth, current experience, and contact.
Product engineering · Content systems
A single suite for utilities, private files, games, and workspaces, with executable registries and risk-based persistence.
The suite shows how several real workflows can move from interface through APIs, data, security, and deployment while remaining coherent as one product.
Product engineering · Full-stack systems
The private console that writes Portfolio contracts, IAM access, and deploys—after a live capability check, not a hidden button.
Editorial operations are separated from public presentation, so the portfolio can evolve without code edits or duplicated content while authorization remains server-enforced.
Full-stack engineering · CMS architecture
A shared authentication foundation for password and OAuth entry, recovery, MFA, connected providers, safe return paths, and explicit logout across the application family.
Shared session contracts reduce divergent auth behavior while each application retains ownership of its public, protected, and role-gated authorization policy.
Authentication architecture · Security engineering
