James Martinez

I'm a software engineering manager. I run about 8 people on two remote teams that build construction software: Equipment360 (a .NET desktop app, its API, and iOS apps) and Fleet Mobile (iOS). Two of them are QA engineers, and a third is in training.

I came up through customer support, business solutions, and four years of QA on the same product before I started managing the team in late 2024. Most of my work is the handoff from a customer problem into engineering work. When that handoff is broken, I fix the system behind it.

Right now QA owns first-line product escalations. A time-to-resolve board shows how long each case has been open. A hard night starts with a short written page. Anything that ships has one named owner.

I score people on a written card, and it's on this site. If a number isn't mine to stand behind, it stays off.

Selected work

Five things you can judge.

• Escalation bot + time-to-resolve board: QA on the front line and a shared clock on every case. Tier 2 support tickets are down about 75% after the escalation path and related support tooling landed.
• Wrenchy, an AI code reviewer: reviews every pull request that's ready for review. Support pastes an error message and gets a likely place in the code.
• Day-0 incident writeup: the short page we should have had the night documents went missing.
• Equipment360's first performance test: started with our QI team, ended in Azure sizing and database index recommendations.
• GitHub Enterprise cutover: about 40 repos moved on one cutoff date.

How I work

How I staff, what I kill, how I run hard nights, and the bar I score people on: How I work. Two pieces you can open without the rest: my hiring scorecard and the day-0 incident page I want on the first night of a hard customer issue.