Experience

A steady path through product work.

From marketing sites to full-stack product delivery, my work has moved steadily toward owning the whole path from first sketch to a reliable release.

Product engineering Frontend systems Full-stack delivery Remote collaboration

Career timeline

Roles and responsibilities.

The through-line: work close to the product, keep the system understandable and hand over something the team can own.

  1. 2021 — Present

    Independent Full-Stack Developer

    Freelance & product collaborations · San Francisco, CA · Remote

    Current

    Partner with small product teams to design, build and improve web applications from early concept through production.

    • Lead frontend and full-stack delivery for product experiments and production features.
    • Translate loose product briefs into scoped, testable implementation plans.
    • Build reusable UI foundations, API integrations and deployment workflows.
    • React
    • TypeScript
    • Node.js
    • PostgreSQL
    • AWS
  2. 2020 — 2021

    Frontend Engineer

    Product Studio (sample) · San Francisco, CA

    Built customer-facing interfaces for a small studio serving early-stage product teams.

    • Developed responsive product interfaces from Figma prototypes.
    • Introduced shared component patterns and clearer CSS conventions.
    • Worked with backend engineers on API contracts and loading states.
    • React
    • JavaScript
    • Sass
    • REST APIs
  3. 2018 — 2020

    Web Developer

    Digital Agency (sample) · Remote

    Delivered marketing sites and lightweight web applications for a range of small organisations.

    • Converted design systems into reusable page components.
    • Improved page performance and cross-browser consistency.
    • Supported content editors with practical documentation and handover.
    • HTML
    • CSS
    • JavaScript
    • WordPress

Education

Foundations.

2014 — 2018

BSc Computer Science

State University (sample) · California

Illustrative education entry. Replace it with your own qualification or remove this section.

Approach

How I tend to work.

Clear enough to be useful, loose enough to adapt to the team.

01

Understand the problem

Start with the decision the user is trying to make, not the screen they are on.

02

Make the path visible

Sketch flows and states early so ambiguity is exposed before code is written.

03

Build in slices

Ship a working vertical slice, learn from it, then widen the surface area.

04

Leave it documented

A clean handover is part of the deliverable, not an afterthought.

Right now

What has my attention.

The questions I'm carrying into the next project.

Talk about your product

What I'm focused on now

  • Design systems that survive real product pressure
  • Accessible, data-heavy interfaces
  • Small tools that make product teams faster
  • Performance budgets that are easy to keep

Next step

Looking for someone who can own the build?

Tell me about the team, the problem and the timing. I'll be direct about where I can help.