We're hiring a QA specialist to own quality on real client products. Half the job is hands-on: exploratory passes, edge cases, design review, catching the things the spec never mentioned. The other half is building the AI-assisted and automated coverage that runs those checks continuously, so you're not manually re-testing the same login flow every sprint. You'll be the person the team asks when someone wants to know whether this is actually ready to ship.

About Us

Bolder Apps is a product development studio that partners with US-based startups and established companies to build and scale innovative digital products. We specialize in AI-powered development, full-cycle product creation, and engineering team augmentation. Our mission is simple: build bolder, faster, and smarter.

Our Culture & Values (read before applying)

We move fast. We take ownership. We work with AI, not against it. And we expect everyone to bring ideas, not wait for instructions.

There are no daily checklists, no micromanagement, and no corporate politics. Instead, you'll have autonomy, trust, and a team that's always ready to help you grow. At Bolder Apps, impact matters more than titles, and curiosity matters more than seniority.

If you want a place where you can level up fast and actually see your work making a difference - welcome aboard.

Responsibilities

• Own the QA process on your projects end to end. Test strategy, test cases, regression suites, release sign-off. Nobody is going to hand you a template.
• Run manual and exploratory testing across web and mobile. Functional, boundary, negative, cross-browser, responsive, and the paths users find that nobody planned for.
• Build and maintain automated coverage where it earns its keep, and use coding agents to write, extend, and repair those suites faster than you could by hand.
• Test AI features properly. Non-deterministic output, prompt regressions, hallucination and failure modes, evals instead of a single golden assertion.
• Research and pilot new AI testing tools, then report honestly on what worked, what cost too much, and what we should drop.
• Write bug reports engineers can act on without a follow-up call. Repro steps, environment, severity, evidence, expected versus actual.
• Get deep on each product early. Read the spec, interrogate the requirements, understand the user, then map where it's most likely to break.
• Keep everyone current on release status: what's covered, what's blocked, and what risk we're accepting if we ship today.