<p><strong>EviSmart</strong></p> <p><strong>Automation & Stability Engineer</strong></p> <table width="624"> <tbody> <tr> <td width="624"> <p><em>"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."</em></p> </td> </tr> </tbody> </table> <p> </p> <p>📍 BGC, Taguig, Philippines • On-site • Full-Time</p> <p><strong>WHAT EVISMART IS BUILDING</strong></p> <p>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.</p> <p> </p> <p>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.</p> <p> </p> <p><strong>WHY THIS ROLE, WHY NOW</strong></p> <p>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.</p> <p> </p> <p>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.</p> <p> </p> <p>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.</p> <p> </p> <p><strong>WHY EVISMART</strong></p> <ul> <li>Leading dental Autopilot system in a $40B global healthcare industry — operating across 28 countries, live in production</li> <li>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</li> <li>Manila is not a back office. It is the delivery engine — operations, AI, product, and engineering all run from here. Your work ships globally</li> <li>We promote based on output, not tenure. The people who move fastest here are the ones who own their work completely</li> <li>300+ people and growing — the career path is real because the company is growing into it</li> </ul> <p> </p> <table width="624"> <tbody> <tr> <td width="624"> <p><em>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.</em></p> </td> </tr> </tbody> </table> <p> </p> <p><strong>WHAT YOU'LL OWN</strong></p> <ul> <li>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.</li> <li>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.</li> <li>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.</li> <li>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.</li> <li>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.</li> <li>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.</li> </ul> <p> </p> <p><strong>WHAT SUCCESS LOOKS LIKE</strong></p> <table width="624"> <tbody> <tr> <td width="104"> <p><strong>Milestone</strong></p> </td> <td width="520"> <p><strong>What It Looks Like</strong></p> </td> </tr> <tr> <td width="104"> <p><strong>30 Days</strong></p> </td> <td width="520"> <p>Global Regression Library audit complete. First automated test suite running in CI/CD. All five quality gates mapped to the release pipeline.</p> </td> </tr> <tr> <td width="104"> <p><strong>60 Days</strong></p> </td> <td width="520"> <p>Full regression, API, performance, and security gates running for every sprint release. Change Failure Rate trend established and reported.</p> </td> </tr> <tr> <td width="104"> <p><strong>90 Days</strong></p> </td> <td width="520"> <p>KPIs hitting target: Change Failure Rate <5%, Release Integrity ≥99%, MTTR <1 hour. Rollback system tested and verified for every build.</p> </td> </tr> </tbody> </table> <p> </p> <p><strong>WHAT YOU'LL GET</strong></p> <ul> <li>A seat at the AI table — work dire