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 the new dashboard platform: component architecture, state management patterns, API consumption layer, routing strategy, and design system implementation.
- Establish Engineering best practices and champion a scrum development process across the frontend team.
- Define The integration patterns the frontend team uses to consume backend APIs — auth, data fetching, caching, error handling — setting the standard the whole squad follows.
- Build The technical connection between the dashboard platform and the AI Design module: own the integration contract and keep it clean as both products evolve.
- Nurture Two frontend engineers through architectural reviews, code quality standards, and component patterns — set the bar for how the team writes code.
- Make Build-vs-buy decisions on frontend tooling: component libraries, testing frameworks, monitoring, and performance profiling.
- Assess Existing code across EviSmart’s broader product surface in collaboration with the offshore engineering team — deliver a written recommendation on what to leverage, what to build fresh, and why.
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 with salary range disclosed at offer.
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
- 6+ years React JS / TypeScript experience, with at least 2 years setting frontend architecture for a team — not just contributing features, but making the decisions the team built on.
- You’ve led a React application from architectural decisions to multi-engineer delivery: component libraries, state management patterns, API consumption layers.
- Strong in: TypeScript, design system implementation, performance optimization, and testing strategies across unit, integration, and e2e.
- Experienced with REST / GraphQL APIs, auth flows, real-time data patterns, and responsive design across desktop and tablet at production scale.
- You conduct real code reviews, write architectural decision records, and nurture mid-level engineers — without needing a process to make it happen.
- Bonus: you’ve evaluated and extended an existing codebase rather than only building greenfield. That’s exactly Day 1 here.
- SaaS or B2B platform experience preferred; dental or healthcare background not required.
Apply today @ Evismart Careers
