Quick overview
Job description
About Us
Meraki Labs (founded by Mukesh Bansal & Peeyush Ranjan) builds and rapidly scales AI-first, "moonshot" startups. We're looking for a sharp, hands-on QA Engineer to help ship 0-to-1 products alongside founders.
About Proofline
Proofline is building the infrastructure for scientific reasoning. Scientific discovery depends on more than papers and datasets. It depends on the reasoning behind every experiment, decision, and breakthrough. Proofline preserves that reasoning so knowledge compounds instead of disappearing. Proofline is live in production with institutional pilots underway with research institutions and enterprise research teams. Learn more: https://prooflinehub.com/about/
About the role
As QA Engineer, you will own product quality across Proofline's releases, making sure every feature works reliably on a live system before it reaches researchers and institutions.
Responsibilities
Own manual testing across the product: write test plans and test cases, run exploratory, functional, and regression testing.
Run smoke tests on every build and release to catch critical issues before they reach users.
Use AI tools to speed up testing: generating test cases, test data, and edge-case scenarios, and triaging issues.
Log, track, and verify bugs with clear reproduction steps; work closely with engineers to drive them to closure.
Help define release checklists and quality standards as the product scales.
Requirements
Experience - 2-5 years in QA / software testing.
Strong hands-on manual testing experience (web applications preferred).
Smoke testing experience as part of build and release cycles.
Experience using AI tools in your testing workflow.
Sharp attention to detail and clear written communication of issues.
Exposure to test automation or API testing is a plus.
How We Work
Small team, high trust, written decisions. Designs get adversarial review before code; PRs get automated review driven to zero open findings; features aren't done until verified on a live system. AI agents do a large share of the implementation, which makes rigorous verification and knowing when the machine is wrong central to how we ship.
You Should Apply If
You enjoy breaking things and finding the edge cases others miss.
You thrive in fast-moving, low-process environments.
You're excited about using AI to make testing faster and smarter.
You Should Not Apply If
You want remote/hybrid (this is onsite Bangalore only).
You prefer narrow tickets and minimal ambiguity.
You prefer highly structured, slow-moving product organizations.
