Skip to content

Jason Poteet.Engineering Leader · Staff Software Engineer.

I lead teams and still ship code, for government, enterprise, and startup work.

  • LocationAustin, TX
  • ExperienceLed teams of up to 7 engineers

The stack I reach for

A pragmatic toolkit refined across government, enterprise, and startup engagements. I optimize for delivery without compromising long-term maintainability.

Languages

  • TypeScript
  • JavaScript
  • Python
  • SQL

Frontend

  • React
  • Next.js
  • Vite
  • Tailwind CSS

Backend

  • Node.js
  • Fastify
  • Express
  • GraphQL

Data

  • Postgres
  • Supabase
  • MySQL

Infra & Tooling

  • AWS
  • Docker
  • GitHub Actions
  • Vitest

Architecture & Practice

  • Mentoring
  • Roadmapping
  • On-call
  • Hiring
  • Code review
  • Incident response

Three modes, one way of working.

I operate in three modes depending on what the team needs. The work below is what each mode looks like in practice, not in a job description.

  1. As an engineer

    I stay close to the code. TypeScript across the stack, React on the surface, typed APIs and Postgres behind. The hard part is rarely the framework. It is naming the seams between systems and keeping the next change cheap. I write tests for the parts I would be afraid to refactor, and I leave a trail of small commits the next person can read.

  2. As a tech lead

    I make the architectural decisions explicit and reversible. That looks like short design docs, decision records, and reviews that ask the same three questions: what breaks, what gets slower, what gets simpler. I pair on the messy parts and pick the migrations the team will thank us for in six months, not the ones that look bold in a demo.

  3. As a manager

    I lead small teams (five to seven engineers) by removing ambiguity before it compounds. One-on-ones are for the engineer, not the status report. Roadmaps are negotiated, not handed down. I hire deliberately, give feedback in writing as well as in conversation, and protect the team from interrupts so the work that matters gets done.

Where I have done it

Government, enterprise, and startup teams. The short version is below, and the long version is in the resume.

  1. Clay

    Remote

    1. Aug 2025 to Present

      Engineering Manager

      Leading a team of seven on GTM data pipelines, CRM integrations, and the infrastructure behind AI research agents.

  2. Adobe

    Remote, Austin · 8 yrs

    1. 2021 to Aug 2025

      Senior Engineering Manager

      Promoted into people management and kept shipping, leading five engineers plus QA on Adobe Commerce.

    2. May 2017 to 2021

      Lead Software Engineer

      Lead engineer on the Product Discovery drop-in for Adobe Commerce Optimizer, owning front end architecture for enterprise eCommerce clients.

  3. Foxtrot Code

    Remote, Austin

    1. Jul 2015 to May 2017

      Senior Full Stack Engineer and DevOps Lead

      Built a codeless analytics and reporting platform on Splunk, and owned the AWS environments and delivery pipelines behind it.

  4. Sizmek

    Remote, Austin

    1. Mar 2014 to Jul 2015

      Software Developer Lead

      Led UI and analytics tooling for an ad platform running in more than 70 countries.

Earlier

  • 2010 to 2014Defense contracting, IT and software contractor
  • 2005 to 2010United States Department of Defense, IT contractor
  • 2000 to 2004United States Air Force, Communications-Computer Systems Programmer

Selected projects

Things I build, ship, and maintain. Each one is public, with a README that explains the problem and the decisions behind it.

  • An append-only inventory ledger that keeps two customers from buying the last unit, with measured concurrency control, checkout holds that expire and tenant isolation enforced by Postgres. The live demo runs its own store code against Postgres in the browser.

    • TypeScript
    • Node.js
    • Fastify
    • Postgres
    • React
    • Docker

The short version.

I am an engineering leader and staff software engineer who has shipped production software across government, enterprise, and startup teams. I work across the stack, from TypeScript and React on the front to typed APIs and cloud infrastructure behind them, and I lead the people building it. My focus is the same either way: reduce complexity, make the next change safe, and help the team ship work they are proud of.

  • Clarity over cleverness, in code and in conversation
  • Types and tests are how I keep future-me and the team honest
  • Architecture is a series of reversible decisions, so I optimize for the next one, not the final one
  • I lead by writing things down, asking better questions, and removing ambiguity before it compounds
  • A team that ships steadily beats a hero shipping occasionally

Let's build something.

The fastest way to reach me is email. I read everything and reply to teams hiring senior engineers, tech leads, or engineering managers for full-time roles, and to collaborations that sound interesting.