🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Build the quality infrastructure that enables AI agents to transact globally. AI is changing how software is built. We believe it will fundamentally change how commerce works. Millions of AI agents will soon discover products, negotiate prices, make purchases, and manage financial workflows on behalf of consumers and businesses. Existing payments infrastructure wasn't designed for autonomous software. Manif is building the infrastructure and control plane for agentic commercea neutral layer that enables AI agents to transact safely across payment providers, protocols, regions, and payment methods while ensuring consumers and merchants remain in control. We are currently operating in stealth and are well funded by leading venture investors and strategic partners. With fundraising behind us, our full attention is on building the infrastructure that will power the next generation of global commerce. The Role Quality is not a function at Manifit is a core engineering discipline. We are looking for aFounding QA Leadto build a modern, AI-native quality engineering organization from the ground up. This is not a traditional manual QA role. We expect software to be specified, implemented, tested, and validated with AI deeply embedded throughout the development lifecycle. You will define how quality is engineered across the company by building a continuous, automated validation platform that gives us confidence to ship quickly without compromising reliability. You will work closely with the founding engineering team to build: Automated API, integration, end-to-end, and regression test frameworksAI-assisted test generation from specifications and product requirementsContinuous validation pipelines integrated into CI/CDPerformance, load, resilience, and chaos testing infrastructureSecurity and compliance validation for financial systemsTest environments, synthetic data generation, and developer toolingProduction monitoring and automated regression detectionRather than validating software after it is written, you'll help define a development process where quality is continuously verified from specification through production. Qualifications We're looking for someone who views quality engineering as a software engineering discipline. Successful candidates will typically have: A deep technical foundation in computer science, mathematics, engineering, or a related quantitative discipline.Significant experience building automated testing platforms for distributed systems rather than primarily performing manual testing.Strong programming ability (JavaScript/TypeScript, Python, or similar) and the ability to build internal engineering tools.Experience testing APIs, distributed systems, databases, authentication systems, and cloud-native applications.Strong understanding of CI/CD, observability, production monitoring, and release engineering.Familiarity with modern testing approaches including property-based testing, fuzz testing, contract testing, mutation testing, and synthetic test data generation.Experience with payment systems, financial infrastructure, or other high-reliability distributed systems is highly desirable. You'll Probably Thrive Here If You. Already use AI as a core part of your daily engineering workflow.Believe the future of QA is continuous, automated, and AI-assistednot manual test execution.Think like a software engineer who happens to specialize in quality.Can build frameworks that thousands of tests run onnot simply write individual test cases.Sweat the details that matter: correctness, determinism, idempotency, security, resilience, and edge cases.Enjoy designing systems that prevent defects instead of merely finding them.Have high agency, enjoy ambiguity, and are excited about creating engineering practices from first principles. Our Philosophy Quality is our identity. Quality is not something we inspect into softwareit is something we design into the system. Every specification, architecture decision, test, and deployment contributes to long-term reliability. Users above all. We measure ourselves by the trust our platform earns. High agency. Low ego. We communicate directly, challenge ideas respectfully, and optimize for the best solution. Design creates leverage. As AI increasingly generates code, engineering leverage shifts toward specifications, architecture, validation, and systems thinking. AI-native by default. AI is embedded throughout our engineering workflow. Humans remain accountable for design, judgment, and stewardship of outcomes. If you're excited about redefining how software quality is engineered in an AI-native worldand helping build the infrastructure behind the next generation of global commercewe'd love to talk. .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.