| |
| --- |
| "Most QA roles are the last line of defense — they catch failures after they happen. This one is the system that makes failures impossible to reach production in the first place." |
📍 BGC, Taguig, Philippines • On-site • Full-Time
WHAT EVISMART IS BUILDING
EviSmart is the leading dental Autopilot system operating across 28 countries in a $40B healthcare industry — and the Manila team builds and ships it. Not an MVP. Not a pilot. Live, in production, with thousands of dental labs and dentists depending on the platform every day to run their business. We have multiple in-house AI teams building the next generation of dental design automation — and Manila is where it gets operationalized. We are one of the few genuinely AI-first companies in the Philippines. The models are being built here. The product is scaling here. The opportunity is here. WHY THIS ROLE, WHY NOW
Every sprint, EviSmart ships to a live global platform that 2,000+ dental labs depend on daily. Right now, quality gating is partially manual — a human eye, a checklist, and delivery pressure that competes with thoroughness. That is not a process problem. It is an infrastructure problem. The Automation & Stability Engineer is the role that fixes it at the source. The person who joins now will build the Global Regression Library from the ground up, embed automated security scanning in the CI/CD pipeline, and define what a zero-regression deployment looks like at EviSmart — before those patterns are set by someone else. In 12 months, every release will pass through five automated quality gates that this person built. The Change Failure Rate will be a published number, not a guess. The rollback system will be tested before every deployment, not after. That infrastructure does not exist yet — and this hire builds it.
WHY EVISMART
Leading dental Autopilot system in a $40B global healthcare industry — operating across 28 countries, live in production
Multiple in-house AI teams building proprietary models — not just consuming APIs. Claude, Cursor, Luvable, and LLM-powered workflows are part of the daily stack
Manila is not a back office. It is the delivery engine — operations, AI, product, and engineering all run from here. Your work ships globally
We promote based on output, not tenure. The people who move fastest here are the ones who own their work completely
300+ people and growing — the career path is real because the company is growing into it
| |
| --- |
| The engineering team ships every week. What we don't have yet is the automated layer that makes every release safe — systematically, not by luck. We need someone who will build that quality factory from scratch: the regression library, the performance gates, the security scanning, the rollback verification. If you have built automated test infrastructure before and want to own it end-to-end, this is the role. If you're looking for a QA checklist job, this isn't it. |
WHAT YOU'LL OWN
Global Regression Library — build, maintain, and expand the automated test suite that every sprint output must pass. Every new feature adds new regression tests. Coverage gaps are closed, not carried. - API & Integration Testing — develop and maintain automated tests for critical API endpoints and external integrations (payment, file handling, notification delivery). Every integration point is tested in the pipeline, not discovered in production. - Performance Gatekeeping — design and run automated load and performance tests per release. No feature ships if it causes database spikes, portal slowdowns, or degraded API response times. You define the baseline and enforce it. - Security Gates — implement and monitor SAST/DAST security scanning embedded in the CI/CD pipeline. New critical or high vulnerabilities do not reach production. Security scanning is not skipped under delivery pressure. - Rollback Readiness — verify the technical integrity of every rollback plan for every new build. The one-click rollback system is operational and tested before deployment is approved. MTTR target: under one hour. - Risk Signal — you are the first to know when a quality gate is at risk, a regression test coverage gap has opened, or a performance baseline is trending toward a breach. You act on it before it reaches production. WHAT SUCCESS LOOKS LIKE
| | |
| --- | --- |
| Milestone | What It Looks Like |
| 30 Days | Global Regression Library audit complete. First automated test suite running in CI/CD. All five quality gates mapped to the release pipeline. |
| 60 Days | Full regression, API, performance, and security gates running for every sprint release. Change Failure Rate trend established and reported. |
| 90 Days | KPIs hitting target: Change Failure Rate <5%, Release Integrity ≥99%, MTTR <1 hour. Rollback system tested and verified for every build. |
WHAT YOU'LL GET
A seat at the AI table — work directly alongside in-house AI model teams using Claude, Cursor, Luvable, and LLM-powered workflows. You'll work with these tools daily, including using AI to accelerate test generation and pipeline automation
Global reach, Manila-built — EviSmart operates across 28 countries. The production environment you protect is the platform that dental businesses across North America, Europe, and beyond depend on every single day — from your desk in Manila
Quality infrastructure ownership — your regression library, your performance gates, your security scanning. The Change Failure Rate the engineering team publishes is the number you built the system to hit
A concrete career path — Automation & Stability Engineer → Senior Automation Engineer → QA Engineering Lead. As the product and team scale, the quality infrastructure scope scales with it
Above-market compensation for engineers who have personally owned automated test infrastructure end-to-end. Range disclosed at first screen. - HMO coverage, 13th month pay, and all government-mandated benefits
HOW WE WORK
We share work before it's ready. We debate decisions loudly and execute them quietly. We default to fixing problems instead of escalating them. Manila is the delivery engine for a global platform — the standard is high and the pace is real. A quality gate that gets skipped under delivery pressure is a quality gate that doesn't exist. A regression failure that reaches production is a test coverage problem that was already there. We fix things before they escalate, and we expect everyone here to do the same. If you've spent time waiting for someone else to own the test infrastructure — you'll notice the difference on your first week. | |
| --- |
| "Why EviSmart and not a bigger company? Because at a bigger company, your work goes into a queue. Your output is handled by a template. Here, what you build ships to 28 countries. That's the kind of ownership most roles never give you — and we think the best people want it."— EviSmart Talent Team |
A NOTE ON WHAT WE'RE NOT
The most common hesitation we hear from strong candidates for this role: "Is this actually a build role, or is it a testing checklist job with a better title?"
It is a fair question. This role exists to build quality infrastructure that does not yet exist — not to run scripts someone else wrote or manually check features against acceptance criteria. You will design and build the automated factory: the regression library, the performance test harness, the security gate integration, the rollback verification system. The engineers deliver features. You build the system that decides whether those features are safe to ship. Those are different jobs — and this is the second one. This is not a cost-center role and Manila is not a support function. Our Manila team leads engineering and operations — the product ships from here. If you've seen "Philippines office" mean something smaller at other companies, that is not what this is. On AI: EviSmart's AI is not a marketing claim. We have in-house model research and development teams, and the tools we use daily — Claude, Cursor, Luvable, LLM-powered workflows — are part of the actual stack, not a slide in a deck. The next 12 months will see the automated quality layer become a core part of how EviSmart's AI-powered product ships safely at scale. WHAT WE NEED
3+ years building and owning automated test infrastructure in a SaaS or enterprise software environment — regression libraries, API test suites, or CI/CD-integrated quality gates — where you personally designed and maintained the system, not just executed existing scripts
Track record of reducing production incidents through automated quality gating — the Change Failure Rate moved because of something you built, not just because someone else improved the code
Hands-on experience implementing SAST/DAST security scanning in a CI/CD pipeline and automated load and performance testing — not configuring a tool once, but owning the integration and acting on the results
Judgment to act on a coverage gap or a drifting performance baseline before it becomes a production incident — you notice what's missing before someone tells you to look
Communication that is clear, fast, and written — we are distributed and async writing is a core skill, not a soft one
Familiarity with Jira as a workflow tool, experience in a Agile/Scrum delivery environment, and exposure to dental, healthcare, or regulated SaaS environments are strong advantages
