QA Engineer (Claude Code, Python, React, Manual Tester)

Top 3 reasons to join us

• We are flexible, don't expect you to be in office.
• No politics, respectful and straightforward.
• We iterate fast and are curious.

Job description

Brarista builds AI fit-assistance for lingerie and apparel brands — a chat assistant and sizing quizzes that are live on real stores today.

When we get a size recommendation wrong, nothing crashes and no alarm goes off. A real person is simply told the wrong size, buys the wrong bra, and sends it back. That is why this role exists: you are the person who catches things before customers do.

You'll work alongside our engineers across the sizing engine, the chat assistant, our client dashboard, and the widgets running on our clients' storefronts.

1. Verify the sizing engine.
Our system converts sizes across 11 regional systems, handles sister sizing, calculates from measurements, and applies a different size chart for every brand we support. That's thousands of combinations — far more than anyone can check by hand. You'll use Claude Code to generate exhaustive test matrices, build regression suites, and prove that a change to one brand didn't quietly break another.

2. Guard catalogue data quality.
Our product catalogue is tagged partly by AI, and every product needs a sizing category — which is what makes it billable, so mistakes here cost money directly. You'll verify AI-suggested tags, check assignments against our rules, and find the products that slipped through. This becomes one of the most important things you own.

3. Own release quality and the changelog.
You'll test what's about to ship and write the release notes our clients read. When something goes out, you're the person who can say what changed and why.

4. Triage what clients report.
Bug reports and feedback come in from clients. You'll reproduce them, work out what's actually happening, write them up so an engineer can act immediately, and close the loop with the person who reported it.

Your skills and experience

You are genuinely, unusually meticulous. You're the person who spots the inconsistent spacing, the off-by-one in a table, the one row in a spreadsheet where the pattern breaks. This isn't a preference you're describing on a CV — it's how your brain works, and people have told you so.

You're excellent with Claude Code, and you can prove it. We want to see a real project where you used it heavily — what you had it do, what you did yourself, and a specific time it produced something wrong that you caught. That last part is what separates people who use AI tools from people who are good with them.

You think in edge cases. Given a feature, you immediately wonder what happens with an empty value, a duplicate, a weird character, someone clicking twice, or the largest size in the range.

You write clearly, in English. Bug reports an engineer can act on without asking follow-up questions. Release notes a client can understand. You'll be working with UK-based colleagues and writing for international clients.

You're curious about the domain. You'll learn more about bra sizing than you expect to, and the good ones here find that interesting rather than tedious.

Experience level is flexible — if you're early in your career but genuinely sharp with AI tools and relentless about detail, we want to talk to you.

Nice to have

• Intercom, Gleap, or similar feedback and bug-reporting tools
• Writing changelogs or release documentation
• Test automation (pytest, Playwright) — or the appetite to learn it fast with Claude Code
• E-commerce experience, especially Shopify

Why you'll love working here

• Remote and async, with direct access to the founder and the engineers. Small team, no layers, no one to route your idea through.
• Goal-first. We care about what ships and what it does for clients — no office politics, no mandatory socials, no ceremony for its own sake.
• AI-first, genuinely. Our whole team works with Cursor and Claude Code, and much of our code is AI-authored under human review. You'll get better at working with these tools here than almost anywhere else.
• Real ownership from month one. Within three months the catalogue verification queue is yours, and the sizing regression suite is something you built.
• Your work is visible. Clients read your release notes. Your bug reports change what ships. Nothing you do disappears into a backlog.
• We move fast — which is exactly why we need someone whose job is to make sure fast doesn't mean sloppy.