Startups · AI

Senior Software Engineer (AI Tooling)

Triumph · San Francisco HQ · On-site

← All jobs
About Triumph

Premier consumer entertainment and commerce. Backed by General Catalyst.

About the role

Identify and eliminate friction in engineer workflows by constructing effective developer tooling. Quantify the problem before you solve it. Figure out what a given piece of friction is actually costing in time and money, and use that to decide what to build first. Found on 1752vc Careers, the job board for startup and VC roles.

What they're looking for

  • 5+ years of software engineering experience
  • You’ve designed, built, and delivered an internal tool or system that real people used. Ideally something serving a team of roughly 20 to 100 engineers
  • Experience quantifying your own impact. Being able to say what the problem was, how you solved it, and what measurably improved is the signal we care about most
  • Strong engineering fundamentals across the stack. You can work in unfamiliar parts of a codebase and reason about what’s happening
  • Observational instinct. A lot of this job is noticing what frustrates other people and caring enough to fix it, before anyone files a ticket
  • Comfort working with AI. We’re an AI oriented company with an AI integrated development environment, and you should be willing and able to work inside it. Prior experience with AI coding or productivity tools is a plus, not a requirement
More about this role

Triumph runs real money gaming at scale with a small engineering team. The thing that makes that work is leverage: the tooling and automation that let a handful of engineers operate like a much larger group.

That’s this job. You’ll look across our entire development and release process, find the friction, and remove it. Not a narrow slice of it, the whole thing, from local development through CI to what happens after code ships. We have a lot of unknown unknowns right now, and a lot of small things that could be better. Your first job is noticing them.

This is close to a greenfield function. Nobody owns this work today, so you’d be setting the standards rather than inheriting them.

Identify and eliminate friction in engineer workflows by constructing effective developer tooling.

Quantify the problem before you solve it. Figure out what a given piece of friction is actually costing in time and money, and use that to decide what to build first.

Go wherever the process needs attention. You won’t be pigeonholed into one part of the development or release cycle, and you’re free to propose improvements anywhere in it.

Work alongside our engineers. You make the people building our...

Read the full posting on Triumph's site ↗

Engineering

Build your edge while you search

Free tools for founders and investors, plus VC Unfiltered, our take on startups, venture and the people who build them.