QA Engineer, Neoflo

Experience: Minimum 3 years

Reports to: Shubham Shrivastava, Head of Product

Neoflo is building an AI-native agentic platform that automates high-volume back-office operations for the enterprise. We are ~40 people, backed by Lightspeed and Peak XV, with customers across the US and Southeast Asia.

We process invoices, POs, and customer orders for finance teams who can't afford to be wrong. A missed bug isn't a UI annoyance — it's a misposted journal entry, a duplicate payment, an audit flag. That's the bar this role is built around.

What you'll actually do

You'll own quality across three surfaces that most QA roles don't combine:

• The platform — web app, RBAC, dashboards, workflows. The standard stuff, done well.

• The integrations — SAP, NetSuite, Freshdesk, email pipelines, file drops. Where most enterprise bugs actually live.

• The AI outputs — agent decisions, extraction accuracy, edge cases that don't fit a deterministic test. This is the part most QA engineers haven't done before. We'll figure it out together.

Day to day, you'll write and maintain automated test suites, run manual exploratory testing on new features, review PRs for testability, build out our regression coverage, and partner with engineering on CI/CD quality gates. You'll also help define how we evaluate AI agent outputs at scale — what does "correct" mean when there are 50 valid ways to extract a vendor name?

You'll work closely with me (Product) on what to test, with engineering on how to test it, and with our CS team on what's actually breaking in the wild.

Who this is for

You are probably a fit if:

• You have 3+ years of hands-on QA experience, with at least 2 years writing automated tests (any stack — pick what works).

• You've tested integrations, APIs, and async pipelines, not just UI flows.

• You think in edge cases. You break things on purpose.

• You've worked on a product where bugs had real consequences — finance, healthcare, payments, infra.

• You can write a clear bug report that engineers don't have to ping you about.

• You're curious about AI products and how to test them, even if you haven't done it before.

You are probably not a fit if:

• You're looking for a pure manual QA role with no automation expectations.

• You need a fixed test framework handed to you. We'll pick the stack together.

• You see QA as a gate at the end of the SDLC, not a partnership through it.

• You haven't shipped to production in the last 12 months.

What we care about (and what we don't)

We care about:

• How you think about coverage trade-offs when you can't test everything.

• How you debug a flaky test — and whether you fix it or delete it.

• Whether you can explain a bug to a non-engineer in two sentences.

• How you'd test something you've never tested before (hint: AI outputs).

We don't care about:

• Which automation framework you've used. Tools change.

• ISTQB certifications.

• Whether you can recite the testing pyramid.

How to apply

The form will ask you for:

1. Your resume — link to Google Drive, Dropbox, or any URL we can open.

2. An application document — a single Google Doc with your bug write-up (300–500 words) and a link to your code or test sample. Pick a bug you've found that you're proud of. Tell us: how you found it, what the impact would have been if it shipped, and what you changed in your process so similar bugs get caught earlier. Real bug, real product. No hypotheticals. For the code sample, link a test suite, framework setup, utility, or anything you've written that shows how you think about test design — GitHub, gist, or any public URL works.

3. A screen recording (under 7 minutes) covering two things. Spend the first three minutes on your bug story — don't read the write-up, talk to us like you're presenting it and show us your thought process. Spend the next four minutes on a live test design walkthrough: pick any product you use often, open it on screen, and walk us through how you'd test it. What's the first thing you'd try to break? What would you automate vs leave manual? What edge cases worry you most? Your choice of product is part of the signal — pick something you find interesting to test. Use Loom, QuickTime, OBS — whatever works. At the end, tell us how many hours you spent on this application and one thing about Neoflo you're curious about.

4. One question for us — One question you'd want us to answer if we offered you the role tomorrow. Just the question.

No cover letter. We watch the recording first. If it stands out, we read the doc and look at the code sample for context. The thinking is what gets you in.

What happens next

• If your application stands out, you'll have a 1-hour video call with me to talk through your experience and how you think about quality.

• If that goes well, you'll do a take-home or live exercise with engineering.

• Final round is with one of the founders.

This role is in-person in Bengaluru, Monday to Friday. If you're not here, you'll need to relocate. We'll help with the logistics.

We're hiring this role because we're scaling our customer footprint and the cost of a bug is going up. If that sounds like a problem you want to own, we want to hear from you.

Shubham, Head of Product, Neoflo