Hi, I'm Vincent.

I'm a full-stack software engineer in Long Beach, California. Right now I'm the first engineering hire at Lemon Law Champions, a law firm in Costa Mesa, where I'm building the firm's internal operations platform and modernizing the reporting system it runs on. On the side I consult through QaasLab and I'm building TennisFlow, a tennis journal app that's in private beta.

Before that I was on product teams at Ally Financial and Apartments.com. At Ally I shipped an internal dashboard that cut manual loan verification in half. At Apartments.com I helped with the Canada launch. Mostly TypeScript, React, and Angular, with C#/.NET, Python, and SQL when a project called for it.

Outside of work I play a lot of tennis, run when I can, and still get a lot out of the music minor I picked up at UC San Diego. I'm always open to hearing about full-stack roles and contract work. If you're working on something, say hi.

Vincent You smiling in a navy blazer and white shirt, standing in front of palm leaves
Long Beach, CA

Where I've worked

The short version. Happy to go deeper on any of it.

  1. Jul 2026 – Present

    Full Stack Software Engineer · Lemon Law ChampionsNow

    The firm's first full-time engineering hire. I'm building a greenfield internal operations platform, starting with an intake tool that scores case strength, applies the firm's eligibility rules, and routes leads by quality. I also took over a live Google Apps Script reporting system that runs intake, settlements, payroll, and case activity, and brought it under version control with local development, credential management, and a safer way to deploy.

    Next.js · React · TypeScript · PostgreSQL · Supabase

  2. Jan 2025 – Present

    Software Engineering Consultant · QaasLabNow, on the side

    Project-based consulting on client web projects. I lead smaller engagements from the first conversation through delivery and act as the client-facing engineer on larger ones, translating what the business needs into requirements the team can build.

    React · TypeScript · Next.js

  3. Oct 2023 – Mar 2025

    Frontend Software Engineer · Ally Financial

    Shipped an internal ops dashboard that cut manual loan verification by 50% and funding time by 25%, about 30 minutes saved on every loan. Before that, built a custom landing page and application flow for one of Ally's partners. All of it on the auto refinance platform, which processes around $280M a year in originations.

    Angular · React · TypeScript

  4. Sep 2022 – Mar 2023

    Software Engineer · Apartments.com

    Mostly worked on the Canada launch: localization-ready UI and region-specific configuration. Also shipped new components for a sitewide overhaul and added structured logging for the fraud and upload checks in the listing flow.

    Angular · C#/.NET · SQL

  5. Feb 2020 – Apr 2020

    Back End Developer · Scrybe

    Full-stack work on proprietary movement capture software, with the goal of moving stroke recreation to the cloud.

  6. Nov 2019 – Jan 2020

    Software Engineer Intern · Solar Billing

    Automated the data pipelines behind personalized solar savings outreach, replacing a manual process. Added unit tests along the way so they'd stay reliable after I left.

    Python

  7. 2018 – 2022

    B.S. Computer Science, Minor in Music · UC San Diego

    • Communications Director on the founding board of UCSD's ACM chapter. Helped grow it to 1,000+ members and 40K+ views across socials, and wrote the member spotlight interviews for our Medium publication. Sep 2019 – Jun 2020
    • Computer vision research with Prof. Gary Cottrell through ERSP, on reducing racial bias in deep facial recognition with unsupervised and adversarial domain adaptation in PyTorch. Sep 2019 – Jun 2020

How I like to work

A few things I keep coming back to when I'm building something.

Start before it feels ready

I used to think there'd be a point where I finally felt ready to take on something new. That point honestly never came. Most of what I know came from starting anyway and figuring out the next step once I was in it.

Talk to the people using it

Conversations with other players changed what I paid attention to while building TennisFlow. Hearing what they cared about, and what they ignored, gave me more direction than my roadmap did. Client work is the same, so I ask a lot of questions before I write a lot of code.

Ship the smaller version

I've caught myself spending hours getting one detail just right when I should have moved on. Shipping the smaller version usually gives me something real to learn from, and that decides what's next.

Say hi

If you want to talk about a role, a project, or tennis, send me an email. I'm always up for a great conversation.