Level 4 of 6, 2021–2026

Transfix

Staff Software Engineer

Staff Software Engineer 2022–2026 · Senior Software Engineer 2021–2022

New York freight-tech, remote

Context

Moved the app to a Turborepo and npm workspaces monorepo with affected-package detection, picked over Nx in a weighted comparison, with a custom remote cache on S3.

Built AI agent skills with Claude Code and Playwright that create test users, log in and run documented QA test cases on staging, then report what broke.

Maintained and extended the DPL design system on MUI and Storybook, used by all 4 product apps and every engineering team.

Chose Vite for the frontend architecture, worked on real-time notifications over WebSockets, and handled major React upgrades and Module Federation micro-frontends.

Play

This part needs JavaScript. Everything it shows is listed below.

Read the real result

Illustration8 packages · 2 lanes

Only What Changed

Edit a package in an example monorepo, then race "run everything" against "affected only".

Illustration: made-up packages and timings, not Transfix code or data.

Packages · pick one, then edit it

The example monorepo

  • tokens: uses nothing
  • icons: uses tokens
  • button: uses tokens
  • table: uses tokens, icons
  • forms: uses button
  • docs: uses icons, table
  • app-web: uses forms, table
  • app-admin: uses forms, table, icons

Real resultCV

The real result

After the move to a Turborepo monorepo, the same design-system build checks ran about 50% faster, measured before and after. They took about 50 minutes before. That's for those checks, not total CI time.

Daniel and a co-worker compared Turborepo and Nx against weighted criteria they agreed on. He built the Turborepo proof of concept, the co-worker built the Nx one, and Turborepo won on flexibility and customization.

Affected-package detection decides what runs. The remote cache was custom: stored in S3, via a GitHub Action.

Proof

  • ~60%

    faster first paint on the most-used page

    CV

  • ~95%

    fewer calls a day on some queries

    CV

  • ~50%

    faster design-system build checks

    CV

  • Self-initiated: made the shipment details page, the most-used page, ~60% faster. First contentful paint went from ~3.8 s to 1.5 s and largest contentful paint from ~5.1 s to 2.1 s, measured with Datadog RUM.
  • Stopped hidden components from calling APIs and trimmed GraphQL fragments: some queries went from ~10,000 to ~500 calls a day.
  • After the monorepo move, the same design-system build checks ran about 50% faster, measured before and after.
  • The AI QA skills were demoed company-wide and are used by developers, product and support; a teammate built a release-review agent on top. His rough, unmeasured estimate: manual QA of 45 to 60 minutes per feature down to 20 to 30 minutes, running unattended.
  • Delivered core pieces of the data-driven RFP pricing solution; recognized by the VP of Engineering.
  • Hackathon winner: as the team's only developer, built a map of a customer's lanes with arrows colored by risk, from risk and carrier-history data. Design later shipped it as icons in the lane list.

Stack

  • React
  • TypeScript
  • Vite
  • Turborepo
  • npm workspaces
  • Apollo Client
  • GraphQL
  • Redux
  • MUI
  • Storybook
  • Module Federation
  • WebSockets
  • Playwright
  • Claude Code
  • Datadog RUM
  • AWS S3
  • GitHub Actions
  • Ruby on Rails
  • PostgreSQL

NEXT

Want the short version?

The CV has all six levels on one page.