Senior Quality Engineer (Florianópolis)

Remote role — candidates must be based in Florianópolis, Brazil.



A bit about LawnStarter

We run the biggest on-demand marketplace for lawn care and outdoor services in the country. Over $100 million in annual bookings — and honestly, that's just where things stand today. The bigger picture is that we're turning this into a full home services platform. Three brands — LawnStarter, Lawn Love, Home Gnome — all running off one shared backend. The goal is simple: if you own a home, we want to be the only call you need to make.



How engineering works here

Two years ago, we made a decision to rebuild things properly. Not patch what was broken — actually rebuild. New customer app, fresh Pro onboarding, a job distribution engine that actually works, and data infrastructure we're no longer embarrassed by. That work is done. What's next is expanding into new service categories, building out dynamic pricing, and shipping AI features that aren't just demos.

Stack-wise, it's PHP and Laravel on the back end, React and React Native on the front. Cypress is our main testing framework. We use Claude Code as part of how work actually gets done here — it's not a pilot, it's just how the team operates.



What this role is about

Moving fast into new verticals means quality has to move with us. Right now, it can't just be reactive. This person will own the test automation strategy, keep the bug process from falling apart, and work closely enough with Product and Design that problems get caught before they ever reach a customer.

You'd report to the Engineering Manager and sit across the engineering org rather than getting siloed in one corner of it. Expect it to be hands-on — there's real work to do — but also genuinely strategic. You'd have a say in how the team operates, not just how your own tests are written.

A few things that make this different from a typical QA role:

You'd have genuine cross-functional reach. Working directly with engineers, PMs, designers, and the data team — not just getting handed specs to verify. Your job is to surface risks early enough that something can actually be done about them. You might be embedded in one or two delivery teams depending on where the need is.

You'd own the automation strategy. Not execute someone else's plan — set the direction, decide what's worth covering, and build something that holds up as the product keeps changing.

You'd be expected to fix process gaps, not just report them. If something in how we ship software is broken, you'd have the authority to go change it.



Day-to-day, you'd be handling:

Designing and growing the E2E and integration test suite in Cypress. Setting the strategy, prioritizing where coverage is thin, and making sure quality doesn't degrade as new features pile on.

Owning bugs from the moment they're triaged to the moment they're fixed and verified in production. Keeping things moving. Making sure stakeholders already know the status before they think to ask.

Getting into requirements conversations early — with PMs, designers, and the data team. Asking the awkward questions before anyone writes a single line of code. Helping define what "done" actually means in practice.

Finding the weaknesses in how we deliver software and doing something about them. This isn't about writing recommendations documents. It's about shipping actual improvements.

Testing new features and existing flows on real devices across web and mobile. Catching the things a test script would never think to look for.



Two problems you'd be working on from day one:

The first is keeping test coverage sharp as the product grows. The E2E suite is in decent shape. The harder challenge is staying ahead of it — thinking about new kinds of coverage, finding smarter ways to automate as new verticals come online, and not letting the suite turn into a maintenance burden.

The second is figuring out how AI can make quality work better. This isn't a theoretical conversation. There's genuine opportunity to cut repetitive work, find coverage gaps faster, and improve how we catch bugs before they ship. We'd want someone who's actively exploring this — trying things, seeing what works — not waiting for a directive.



What we'd hope to see after your first year:

New features shipping with automated tests already written. Coverage strategies that evolve with the product instead of lagging behind it.

A bug process that runs predictably. People aren't chasing updates because they already know where things stand.

A real understanding of how the marketplace works — well enough that you can spot edge cases nobody thought to spec out.

At least one meaningful quality improvement that's live and actually being used by the team. Something real, not a proposal.



The kind of person we're looking for:

Someone who uses AI tools as a normal part of working. Not because they were asked to — because it makes the work better. Claude Code, browser MCPs, agent workflows, scripting the repetitive stuff away — this should already feel familiar. If you're skeptical about AI having a place in engineering, you'd probably find this environment frustrating.

Someone who defaults to automation when they find a problem. The question isn't "should I write a test for this?" — it's "why doesn't a test already exist?" You build infrastructure that outlasts any one test case. If manual testing is your comfort zone and automation is more of a side task, that's going to be a mismatch here.

Someone who actually thinks like a user. When you test a flow, you're asking whether a real customer can do what they came to do — not whether the behavior matches the ticket description. Quality, for you, is a standard. Not a step in a checklist.

Someone who adapts without making it a big deal. Tools change. Processes change. The way software gets built is shifting faster than most people expected, and a lot of that is because of AI. You either lean into that or you don't — and this team leans in.

Someone direct enough to push back. You'd be working across Product, Design, Engineering, and Operations. When something isn't ready to ship, you say so clearly. If your tendency is to soften feedback to keep things comfortable, that's going to create problems here.

Someone technically solid across the stack. Comfortable writing and reading code. Understands enough about front-end and back-end services to test them properly. Can write meaningful SQL and debug issues wherever they show up.



What this role isn't:

It's not a manual testing job. Automation should make up the bulk of what you actually do day to day.

It's not a backlog-execution job. You'd be shaping what gets worked on — not just picking tickets.

It's not a one-framework job. Cypress is what we use today. Tomorrow might look different. Being attached to one tool would be limiting.

It's not for someone who needs clarity before they can move. New verticals mean new unknowns. You have to be comfortable making judgment calls before everything is defined.

It's not a supporting role. Quality is a real priority here. You'd be expected to have opinions and bring them upstream — not just validate what's already been built.



Compensation and benefits:

Salary range: $45,000–$65,000



Equity — because we want you thinking about the long-term health of what you're building, not just your sprint velocity



Fully remote across the Americas — async-first, results-focused



Unlimited PTO — we care about output, not hours logged

LawnStarter is an equal opportunity employer. We don't discriminate based on race, color, religion, sex, national origin, age, disability, genetics, or any other protected status under applicable law.