Lead Front End Engineer

Job description

*You define how the codebase is built.* *On-site | Vancouver Office – 675 W Hastings St.* **The Problem We're Solving** 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. **Why EviSmart** - 300 people. Two hubs: Vancouver HQ and Manila operations. - 145% year-over-year SaaS growth — the market is responding. - 28 countries. One platform. The dental industry's Autopilot. - An in-house AI model research and development team building proprietary intelligence. **Why This Role, Right Now** 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. **A Note from the Team** *“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.”* **— Paolo Kalaw, CEO, EviSmart** **What You’ll Own** - **Own** the React JS / TypeScript frontend architecture for a new dashboard platform — the unified interface where all products connect. - **Define** the foundation from Day 1: component architecture, state management, API consumption patterns, and design system implementation. - **Assess** existing codebases with the Manila engineering team — determine what to reuse, refactor, or rebuild, and set the direction forward. - **Establish** how the frontend integrates with backend systems — including API/data contracts, data flow, and system behavior - **Ship** the first end-to-end feature connected to live backend APIs early, validating the architecture and approach in production - **Establish** engineering standards across the team: code review, story breakdown, documentation, and development practices - **Lead and mentor** frontend engineers, with a clear and structured approach to improving their output over time - **Operate** independently across the stack — managing your own environment, deployments, and technical decisions without relying on dedicated support layers - **Build** a strong working rhythm with product, backend, and cross-functional teams to ensure consistent delivery. **What You'll Get** - First-mover architectural ownership — the dashboard platform has no frontend codebase yet. - Real ownership — you assess what exists, make the recommendation, and execute on it. No committee approval for architectural decisions. - Production AI tooling from day one: Claude, Cursor, and LLM-powered workflows built in-house — not a sandbox, not a pilot. - A frontend team that grows around the decisions you make — the engineers who join after you build within your architecture from day one. - Clear growth trajectory: lead frontend today, principal engineer as the platform scales. Defined by output, not tenure. - Competitive compensation: $145,000–$160,000 CAD (depending on experience) **How We Work** We ship before we’re 100% certain. We write things down because we have two offices and memory is lossy. We debate loudly and move without resentment. We treat the customer’s real problem as more important than an elegant internal process. If you’ve spent time waiting for permission to try something obvious — you’ll notice the difference here immediately. **The Question You're Probably Asking** *“If they’re building from scratch, why didn’t they hire a frontend architect months ago? The backend is ready and the product direction is set — the architecture decision was the thing that needed to wait. We wanted the product vision locked before the engineer who sets the frontend foundation for the next several years comes in. You’re not inheriting someone else’s rushed decisions. You’re making the considered ones.”* **— EviSmart Talent Team** **What We Need** - Frontend-primary engineer (React / Next.js essential) with strong full-stack understanding - 10+ years experience, including 2+ years in a lead or tech lead role - Proven ability to **drive technical direction**, not just contribute within it - Experience establishing code review practices, engineering standards, and team processes - Demonstrated ability to mentor engineers with a clear and structured approach - Enough DevOps knowledge to manage your own environment (CI/CD, deployments, infrastructure basics) - Comfortable working without heavy support layers (BA, QA, DevOps) - Bonus: Experience integrating AI features, working with offshore teams and you’ve evaluated and extended an existing codebase rather than only building greenfield. - SaaS or B2B platform experience preferred; dental or healthcare background not required. Apply today @ [Evismart Careers](https://evismart.com/careers)