Senior Quality Engineer (Belo Horizonte)

Quality Engineer — LawnStarter (Remote, Belo Horizonte, Brazil)

LawnStarter started out as the go-to on-demand marketplace for lawn care, and it's grown into something bigger — annual bookings are now north of $100M, and the company is pushing past lawn care into home services more broadly. Three brands (LawnStarter, Lawn Love, Home Gnome) now run on one shared platform.

On the engineering side, the last two years have been about rebuilding everything: a new customer app, new Pro onboarding, a job distribution engine, fresh data infrastructure. That groundwork is done. The next phase is about expanding into new service verticals, dynamic pricing, and AI features — and quality has to scale right alongside it.

The stack: PHP/Laravel on the backend, React and React Native on the front end, Cypress for testing. Claude Code isn't a side experiment here — it's baked into how the team actually works day to day.

The role

This isn't a "find bugs after the fact" job. As the team grows and the product expands into new territory, quality needs to be built in from the start — which means owning automation coverage, shaping how bugs get handled, and working closely with Product, Design, and Data to catch problems before customers do.

You'd report to the Engineering Manager, sit embedded across engineering (possibly attached to one or two delivery teams), and have real say over both the hands-on work and the bigger-picture process.

A few things that set this apart from a typical QA role:
- You're not just executing test plans — you set the automation strategy.
- You have the authority to actually fix gaps in the quality process, not just write them up in a doc nobody reads.
- You'll work directly with engineers, PMs, designers, and Data to catch risk early and push back on requirements that don't hold up.

What you'd own

- Test automation — Build and grow the E2E/integration suite in Cypress. Decide what to prioritize, where the coverage gaps are, and raise the bar platform-wide.
- Bug process— Triage through to production fix, start to finish. Keep things moving and keep people in the loop.
- Cross-functional quality— Sit in on requirement reviews with PMs, Designers, and Data. Flag risks early. Help define what "done" really means for a feature.
- Process improvement— Spot the weak points in how the team ships software, and actually fix them.
- Exploratory testing— Get hands-on with new and existing flows across web, mobile, and devices — the stuff automation tends to miss.

The real problems you'd be solving

Coverage doesn't stay solid on its own. As new service verticals come online, the challenge is staying ahead of the product — finding new kinds of coverage and smarter ways to automate as things grow more complex.

There's also a real opening here to use AI to change how quality work gets done — not just to write tests faster, but to catch gaps a person might miss entirely. LawnStarter wants someone who's already poking around in that space, not waiting to be handed a tool.

What success looks like after year one

- New features ship with automated tests as the default, and the testing strategy keeps pace with the product.
- The bug pipeline runs predictably enough that people aren't constantly asking "where's this at?"
- You know the marketplace well enough to spot edge cases before anyone points them out.
- At least one real, lasting improvement to the quality process is in place and actually being used.

Who they're looking for

AI-native. Tools like Claude Code, browser MCPs, agent workflows — this is how you already write and maintain test code. If you're skeptical of AI in the engineering workflow, this probably isn't the right fit.

Automation-first by instinct. When something breaks, your first question is how to stop it from breaking again automatically — not how to patch it manually. If manual testing is more your comfort zone than building infrastructure, this role will feel like a stretch in the wrong direction.

Genuinely customer-obsessed.You test like an actual user would use the product, not just like someone checking a flow against a spec. Quality, to you, isn't a checkbox.

Comfortable with change.No single tool, stack, or process feels permanent to you — which matters, because the company's still moving fast and things shift accordingly.