Network & IT Support Engineer
at Evismart
- Work model
- Onsite
- Location
- BGC, Taguig, Philippines
- Posted
- 10d ago
at Evismart
<p><strong>📍 BGC, Taguig, Philippines • On-site • Full-Time • Scope: Philippines, Canada, South Korea, China</strong></p> <table style="width: 739px;" width="624"> <tbody> <tr> <td style="width: 724.875px;" width="624"> <p><em>"Most IT roles fix problems after people notice them. This one is the reason people never notice — because the network is always up, the device is always ready, and the account is always right."</em></p> </td> </tr> </tbody> </table> <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> </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> <h1>WHY THIS ROLE, WHY NOW</h1> <p>EviSmart runs a live global platform that 300 people across four countries depend on every single day. Right now, that infrastructure relies on a small team managing a growing surface area — devices, accounts, network, security controls, and compliance — without a dedicated engineer who owns the full stack from the Manila office outward.</p> <p> </p> <p>The Network & IT Support Engineer is the role that closes that gap. The person who joins now will own the Manila physical network end-to-end, build out the endpoint support model for all four countries, and embed security controls into the network layer in close partnership with our Cybersecurity FPE. When a new hire's device isn't ready on Day 1, the whole company sees it. When the Manila network goes down, 200 people stop working. When an account stays live after a departure, it's a security incident.</p> <p> </p> <p>None of those failures should be possible — and this hire builds the system that makes them impossible.</p> <p> </p> <h1>WHY EVISMART</h1> <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> <table style="width: 813px;" width="624"> <tbody> <tr> <td style="width: 798.875px;" width="624"> <p><em>"We are running a global platform on a network that one person will own entirely. When that network is stable and every device is ready and every account is clean, I barely hear about this role — and that's exactly what success looks like. I need someone who takes the absence of incidents as seriously as the incidents themselves."</em></p> <p><strong>— Des Peraren, CTO / GM, EviSmart Manila</strong></p> </td> </tr> </tbody> </table> <h1> </h1> <h1>WHAT YOU'LL OWN</h1> <table style="width: 818px;" width="624"> <tbody> <tr> <td style="width: 265.469px;" width="173"> <p><strong>Area</strong></p> </td> <td style="width: 524.948px;" width="451"> <p><strong>What You Do</strong></p> </td> </tr> <tr> <td style="width: 265.469px;" width="173"> <p><strong>Physical Network — Manila</strong></p> </td> <td style="width: 524.948px;" width="451"> <p>Own and operate the Manila office network: Wi-Fi, switches, routers, ISP management, and ExpressRoute hardware. ~200 staff depend on this daily. Network issues are productivity emergencies, not help desk tickets.</p> </td> </tr> <tr> <td style="width: 265.469px;" width="173"> <p><strong>Network Security (with Joseph)</strong></p> </td> <td style="width: 524.948px;" width="451"> <p>Own the enforcement and operation of network security controls — firewall rules, VPN, WAF, IP management, DNS, SSL certificates. Joseph sets the standards; you implement and maintain them on the network and device layer. Nothing changes on the security posture without Joseph's awareness.</p> </td> </tr> <tr> <td style="width: 265.469px;" width="173"> <p><strong>Endpoint Support — Four Countries</strong></p> </td> <td style="width: 524.948px;" width="451"> <p>All employee devices and accounts across Philippines, Canada, South Korea, and China. Device ready before Day 1 for every new hire. Issues resolved same business day. IT asset inventory current within 24 hours of any change.</p> </td> </tr> <tr> <td style="width: 265.469px;" width="173"> <p><strong>Account Provisioning & Deprovisioning</strong></p> </td> <td style="width: 524.948px;" width="451"> <p>Accounts created before Day 1 when People Ops confirms a new hire. Accounts locked on the last day when a departure is triggered. No delays — a live account after departure is a security risk.</p> </td> </tr> <tr> <td style="width: 265.469px;" width="173"> <p><strong>HIPAA / SOC2 Network Controls</strong></p> </td> <td style="width: 524.948px;" width="451"> <p>Implement and maintain the network-layer technical controls that feed into Joseph's compliance program. Maintained continuously — not assembled before an audit.</p> </td> </tr> <tr> <td style="width: 265.469px;" width="173"> <p><strong>Cloud-to-Physical Migration Architecture</strong></p> </td> <td style="width: 524.948px;" width="451"> <p>Design and document the architecture for eventual test environment migration from cloud to physical machines. Joint design with DevOps. Blueprint must be