Lead Front End Engineer

About this role

<p><em>You define how the codebase is built.</em></p> <p><em><span data-contrast="none">On-site | Vancouver Office – 675 W Hastings St.</span></em><span data-ccp-props="{"134233117":false,"134233118":false,"335551550":0,"335551620":0,"335559738":240,"335559739":240}">&nbsp;</span></p> <p><span data-ccp-props="{"134233117":false,"134233118":false,"335551550":0,"335551620":0,"335559738":240,"335559739":240}">&nbsp;</span></p> <p><strong>The Problem We're Solving</strong></p> <p>EviSmart is building the unified dashboard platform where every product surface comes together — the interface lab owners use to manage cases, access analytics, and launch AI-powered tools. It doesn’t have a frontend foundation yet. What exists is a clear product direction, a backend that’s ready to connect, and an engineering team that needs someone to draw the lines before anyone starts building.</p> <p>&nbsp;</p> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 3">Why EviSmart</span></span></strong></p> <ul> <li style="line-height: 2;">300 people. Two hubs: Vancouver HQ and Manila operations.</li> <li style="line-height: 2;">145% year-over-year SaaS growth — the market is responding.</li> <li style="line-height: 2;">28 countries. One platform. The dental industry's Autopilot.</li> <li style="line-height: 2;">An in-house AI model research and development team building proprietary intelligence.</li> </ul> <p>&nbsp;</p> <p><strong>Why This Role, Right Now</strong></p> <p>Most senior frontend engineers join products with foundations already in place — someone else made the hard calls, and your job is to build within them. This is the opposite. There is no existing dashboard frontend, no technical debt to inherit, and no architectural decisions that constrain you yet. The person who joins now makes the foundational choices that the entire frontend team builds on for the next several years. The first product milestone is aggressive, the customer base is real and global, and the backend is ready. What doesn’t exist yet is the engineer who sets the direction.</p> <p>&nbsp;</p> <p><strong>A Note from the Team&nbsp;</strong></p> <p><em>“We’re not looking for someone who needs a clear spec before they can move. We need someone who can audit what exists, make a recommendation, and execute on it. If you’ve been the person who sets the technical direction that your team builds on, and you want to do that at a scale that actually matters, this is that conversation.”</em></p> <p><strong>— Paolo Kalaw, CEO, EviSmart</strong></p> <p>&nbsp;</p> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 3">What </span><span data-ccp-parastyle="heading 3">You’ll</span><span data-ccp-parastyle="heading 3"> Own</span></span></strong><span data-ccp-props="{"134233117":false,"134233118":false,"134245418":true,"134245529":true,"335551550":0,"335551620":0,"335559738":281,"335559739":281}">&nbsp;</span></p> <ul> <li style="line-height: 2;" data-start="278" data-end="422"><strong>Own</strong> the React JS / TypeScript frontend architecture for a new dashboard platform — the unified interface where all products connect.</li> <li style="line-height: 2;" data-start="425" data-end="563"><strong>Define</strong> the foundation from Day 1: component architecture, state management, API consumption patterns, and design system implementation.</li> <li style="line-height: 2;" data-start="566" data-end="716"><strong>Assess</strong> existing codebases with the Manila engineering team — determine what to reuse, refactor, or rebuild, and set the direction forward.</li> <li style="line-height: 2;" data-start="719" data-end="844"><strong>Establish</strong> how the frontend integrates with backend systems — including API/data contracts, data flow, and system behavior</li> <li style="line-height: 2;" data-start="847" data-end="977"><strong>Ship</strong> the first end-to-end feature connected to live backend APIs early, validating the architecture and approach in production</li> <li style="line-height: 2;" data-start="980" data-end="1103"><strong>Establish</strong> engineering standards across the team: code review, story breakdown, documentation, and development practices</li> <li style="line-height: 2;" data-start="1106" data-end="1218"><strong>Lead and mentor</strong> frontend engineers, with a clear and structured approach to improving their output over time</li> <li style="line-height: 2;" data-start="1221" data-end="1377"><strong>Operate</strong> independently across the stack — managing your own environment, deployments, and technical decisions without relying on dedicated support layers</li> <li style="line-height: 2;" data-start="1380" data-end="1493"><strong>Build</strong> a strong working rhythm with product, backend, and cross-functional teams to ensure consistent delivery.</li> </ul> <p>&nbsp;</p> <p><strong>What You'll Get</strong></p> <ul> <li style="line-height: 2;">First-mover architectural ownership — the dashboard platform has no frontend codebase yet.&nbsp;</li> <li style="line-height: 2;">Real ownership — you assess what exists, make the recommendation, and execute on it. No committee approval for architectural decisions.</li> <li style="line-height: 2;">Production AI tooling from day one: Claude, Cursor, and LLM-powered workflows built in-house — not a sandbox, not a pilot.</li> <li style="line-height: 2;">A frontend team that grows around the decisions you make — the engineers who join after you build within your architecture from day one.</li> <li style="line-height: 2;">Clear growth trajectory: lead frontend today, principal engineer as the platform scales. Defined by output, not tenure.</li> <li style="line-height: 2;">Competitive compensation: $145,000–$160,000 CAD (depending on experience)&nbsp;</li> </ul> <p>&nbsp;</p> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 3">How We Work</span></span></strong></p> <p>We ship before we’re 100% certain. We write things down because