Quality & Adoption Specialist (QA)

About this role

<p><strong>EviSmart</strong></p> <h1><strong>Quality &amp; Adoption Specialist</strong></h1> <table width="624"> <tbody> <tr> <td width="624"> <p><em>“Engineering ships the feature. This role makes sure it was the right feature — and that every person who needs to use it actually can.”</em></p> </td> </tr> </tbody> </table> <p>📍 Manila, Philippines&nbsp; •&nbsp; On-site&nbsp; •&nbsp; Full-Time&nbsp; •&nbsp; Reporting to: Lead Systems Analyst<br><br></p> <h1>WHAT EVISMART IS BUILDING</h1> <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>&nbsp;</p> <p>We have multiple in-house AI teams building the next generation of dental design automation — and Manila is where it gets operationalized. Every feature we ship goes into the hands of real users running real operations. The Quality &amp; Adoption Specialist is the person who makes sure features land correctly — verified against requirements before release, and adopted completely on the day they go live.</p> <p>&nbsp;</p> <h1>WHY THIS ROLE, WHY NOW</h1> <p>EviSmart ships continuously. The engineering team builds against Functional Requirements Documents. The operations team runs a global platform. And in between those two realities sits a critical gap: who verifies that what was built matches what was asked for, and who makes sure every end-user is ready to use it on Day 1?</p> <p>&nbsp;</p> <p>Right now, that gap is managed informally. Features go live and edge cases surface in production. Support tickets accumulate around things that should have been caught in UAT or covered in training. Business stakeholders sign off without structured sessions. And when something is wrong, it takes longer to trace than it should.</p> <p>&nbsp;</p> <p>The Quality &amp; Adoption Specialist closes that gap permanently. This role owns the full bridge between Build and Live Operation — functional testing against FRDs, UAT management with business stakeholders, end-user training and documentation, and a 30-day post-launch audit to confirm adoption is real and support tickets are falling. When this role works, features land right the first time and users are ready for them.</p> <h1>&nbsp;</h1> <h1>WHY EVISMART</h1> <ul> <li>Leading dental Autopilot system in a $40B global healthcare industry — operating across 28 countries, live in production with thousands of dental labs depending on the platform every day</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. Every feature you verify and enable ships into that environment</li> <li>Manila is not a back office. It is the delivery engine — operations, AI, product, and engineering all run from here. Your sign-off matters 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 platform keeps scaling</li> </ul> <p>&nbsp;</p> <table style="height: 152px; width: 968px;" width="796"> <tbody> <tr> <td style="width: 952.99px;" width="624"> <p><em>“A feature that works but that nobody uses correctly is a failed feature. A feature that passes QA but ships with the wrong behavior is a failed feature. This role exists to make sure neither of those things happens — and to give us the confidence that what goes live is right, and that our users are genuinely ready for it.”</em></p> <p><strong>— Des Peraren, CTO / GM, EviSmart Manila</strong></p> </td> </tr> </tbody> </table> <h1>&nbsp;</h1> <h1>WHAT YOU’LL OWN</h1> <table width="624"> <tbody> <tr> <td width="160"> <p><strong>Area</strong></p> </td> <td width="464"> <p><strong>What You Do</strong></p> </td> </tr> <tr> <td width="160"> <p><strong>Functional Testing</strong></p> </td> <td width="464"> <p>Create and execute detailed manual and functional test cases based on Functional Requirements Documents (FRDs). You verify that what was asked for is what was built — every time, before release. Edge cases are not optional.</p> </td> </tr> <tr> <td width="160"> <p><strong>UAT Management</strong></p> </td> <td width="464"> <p>Lead User Acceptance Testing sessions with business stakeholders. You structure the sessions, ensure all business edge cases are covered, and are responsible for gathering formal sign-off. UAT is not a formality — it is the last gate before go-live.</p> </td> </tr> <tr> <td width="160"> <p><strong>Documentation &amp; Enablement</strong></p> </td> <td width="464"> <p>Own the creation of Help files, How-To videos, and tutorials. Every feature goes live with self-service documentation already in place. If a user has to ask a colleague how something works, the documentation is not done.</p> </td> </tr> <tr> <td width="160"> <p><strong>User Training</strong></p> </td> <td width="464"> <p>Conduct formal training sessions for end-users — Head of SaaS Ops, Data Annotation Leads, and others — before each feature goes live. 100% of targeted users are trained and able to perform the task on Day 1. Not most. All.</p> </td> </tr> <tr> <td width="160"> <p><strong>Post-Launch Audit</strong></p> </td> <td width="464"> <p>Monitor the first 30 days after every new feature launch. Verify the feature is being used as intended. Confirm that solvable support tickets related to the feature are declining. Document findings and flag any adoption gaps before they become support volume.</p> </td> </tr> </tbody> </table> <h1>&nbsp;</h1> <h1>WHAT SUCCESS LOOKS LIKE</h1> <table width="624"> <tbody> <tr> <td width="147"> <p><strong>Milestone</strong></p> </td> <td width="477"> <p><strong>What It Looks Like</strong></p> </td> </tr> <tr> <td width="147"> <p><strong>30 Days</str