Work with me
Quality you can defend, from someone who has shipped it.
I have spent over a decade testing real software: department-store retail platforms handling promotions at scale, e-commerce, mobile apps, and AI products. Through JPott Studios I help teams build software worth trusting, and I teach what I practice. Here is how we can work together.
What I offer
Pick the shape
that fits your team.
QA health check
A short, fixed-scope review of how your team tests today: the suite, the pipeline, the process, the gaps.
You walk away with
- A written report ranked by impact, plain enough that a VP can read it and specific enough that a QA engineer can act on it.
- Quick wins your team can ship this month, and a longer bet or two for the next quarter, with the reasoning behind each.
- One live 60 minute walkthrough with your team so nothing gets lost in translation.
How I work
I read the code, run the tests, sit in a release, and talk to the people doing the work. Then I write it up in one sitting so you get one report, not a stack of docs. Everything I say is grounded in what I actually saw, not what I would guess.
Start a conversation →Ongoing consulting
Regular advisory time with your team, weekly or monthly. Test strategy, automation decisions, release risk, and how to bring AI into your quality work without losing the trust your tests are supposed to give you.
You walk away with
- A senior QA voice in your regular team decisions, without adding another headcount.
- Short written notes after each session so the calls do not get lost, and a steady view of your suite and pipeline over time rather than one snapshot.
- Someone you can message on release day and get a real answer, not a canned one.
How I work
I show up like a member of your team, not a vendor. I read PRs, sit in your standups when it helps, and give you my honest read even when it is uncomfortable. If I ever think you do not need me anymore, I will say so.
Start a conversation →Team training and workshops
Live, hands-on sessions built around your product and your stack, not slides about someone else’s.
You walk away with
- A team that can do the thing, not just talk about it, with real exercises using your codebase so the muscle stays after the session ends.
- A short reference doc your team can come back to, and follow-up questions answered in writing so nobody is stuck a week later.
- Topics that match where you actually are: testing foundations, automation, API testing, or working with AI coding agents as a QA engineer.
How I work
I start by asking what your team already knows and what they wish they knew. I teach the way I learned. Plain words, real examples, one hard question per section. No slides for the sake of slides, and no filler.
Start a conversation →Speaking
Conference talks, company events, podcasts, and panels on software quality, automation, and AI-assisted development. I have taught at Test Automation University and spoken at STAREAST, SauceCon, and TestBash.
You walk away with
- A talk your audience actually remembers, with clear slides, honest examples, and no vendor pitch.
- A speaker who prepares for your room, not the last room, and rewrites the talk to match the depth your audience needs.
- Follow-through: I answer questions on LinkedIn and by email after the event, so the value keeps compounding.
How I work
I ask what your audience needs and I write for them. If you send me a recording of a past event, I will match the depth to what worked there. If your audience is more technical or less than I usually meet, I adjust.
Start a conversation →Mentoring
One-on-one time for QA engineers who want to grow: moving into automation, leveling up as an SDET, finding your footing with AI tools, or figuring out what your next role should be and how to get there.
You walk away with
- Straight answers about where you are and where you could go next, with a short reading list picked for you and not a generic one.
- Real reviews of your work: PRs, tests, portfolio, resume, or a project you are stuck on.
- Someone in your corner who has done this a while and will tell you the truth kindly.
How I work
We meet monthly or every other week, we set one goal, and we work on it together. If mentoring is not what you need and a course or a paid coach would fit better, I will say so and point you there.
Start a conversation →Product reviews and content
Hands-on, honest reviews and tutorials for testing and developer tools. Always clearly disclosed, and only for products I would genuinely put in front of my readers. If the tool does not hold up, I will tell you privately instead of publishing.
You walk away with
- A real review written after real use on a real project, not a demo transcript.
- Coverage that lasts: a written article, and where it fits the tool, a video walkthrough on my YouTube.
- Space on my blog and newsletter with a real audience of QA and engineering readers, and an honest signal to your team about what to fix before a wider launch.
How I work
I need real access to the product for at least a week of use, not a scripted demo. I disclose every partnership clearly. I write in my voice, not a script you send me. Deadlines get agreed in writing before I start.
Start a conversation →How it works
Simple, honest,
no lock-in.
Tell me what you need
Send a short note through the contact form: what you are building, what is hurting, and what you want to be true in three months.
We talk it through
A short call to make sure I am the right fit and the scope is real. No charge, no obligation, and I will say so plainly if you do not need me.
You get a plan
A clear proposal with scope, timeline, and price. Work starts when it looks right to you.
Not sure which of these you need? That is fine. Describe the problem and I will tell you what I would actually do about it, even if the answer is not hiring me.
Get in touch