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 problem that sits for 48 hours is a retention problem. An ambiguous requirement is a build problem. We fix things before they escalate, and we expect everyone here to do the same.
If you’ve spent time waiting for permission to solve something obvious — 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.”
This is not a ticket-taking role with someone else owning the outcome. You work within a structured sprint cadence - requirements come from the Systems Analyst team, architecture is owned by a Principal Engineer, and deployment is owned by DevOps. That structure exists to let you build fast with clear handoffs, not to take ownership away from you. What you own completely is the quality of what you build and the reliability of what you commit to. If you’re looking for a role where “I built it” is enough - this isn’t it. If you want a role where “I built it, tested it, and it passed the gate” is the standard, that’s exactly what this is.
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 expanded AI pipeline infrastructure supporting dental design automation at increased scale across new markets - and the application layer that carries it needs to be built now, ahead of that growth.