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
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.