About
Hi, I'm Josh Esquivel.
I work across the parts of software delivery that usually get split between separate teams — building the product, testing it, and running the pipeline that gets it to production. Holding all three tends to surface the problems that fall between them.
Most of my work involves test automation: Playwright suites for web applications, Appium for mobile, and the CI pipelines that run them on every pull request. The recurring theme is trustworthiness — a suite that only goes red for real reasons, fast enough that people wait for it rather than merging around it.
The other half is building: TypeScript and Next.js applications, the APIs behind them, and the internal tooling that removes manual steps from a team's week. Increasingly that includes putting AI tooling to work where it genuinely helps, and being clear about where it doesn't.
Positive Techie is how I take that work on directly, without a layer of account management in between. You talk to the person writing the code.
Point of view
What I believe about building software
Quality is a delivery problem, not a department
Handing finished code to a separate QA stage at the end guarantees that defects are found at their most expensive. The useful work is upstream: testable design, fast feedback, and a pipeline that tells the truth.
A test suite nobody trusts is worse than none
A suite that goes red for unrelated reasons trains a team to ignore red. Reliability comes before coverage — always. I'd rather ship forty tests that mean something than four hundred that get retried until they pass.
The best outcome is not needing me
Consultants who make themselves indispensable have optimised for the wrong thing. Documentation, conventions that match your stack, and a real handover are part of the work, not an afterthought.
Let's talk about what you're building
A short conversation is usually enough to work out whether I can help, and what the first useful step would be. No pitch deck, no obligation.