Data Solutions Engineer

<p><em>Establish the single source of truth for customer data. Then use it to get every customer to value, fast.</em></p> <p><em><span data-contrast="none">On-site | Vancouver Office – 675 W Hastings St.</span></em><span data-ccp-props="{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335551550&quot;:0,&quot;335551620&quot;:0,&quot;335559738&quot;:240,&quot;335559739&quot;:240}">&nbsp;</span></p> <p>&nbsp;</p> <p><strong>The Problem We're Solving</strong></p> <p>EviSmart™ has grown fast — data now lives in more places than it used to: the backend that runs the business, the CRM where sales and customer success work, and the data every lab brings with them when they join the platform. Reporting takes more cross-checking than it should, and the data-mapping step in lab onboarding — simple in concept but exacting in practice. This role exists to close that gap: one person who owns making EviSmart's customer data a single source of truth.</p> <p>&nbsp;</p> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 3">Why EviSmart</span></span></strong></p> <ul> <li>300 people. Two hubs: Vancouver HQ and Manila operations.</li> <li>145% year-over-year SaaS growth — the market is responding.</li> <li>28 countries. One platform. The dental industry's Autopilot.</li> <li>An in-house AI model research and development team building proprietary intelligence.</li> </ul> <p>&nbsp;</p> <p><strong>Why This Role, Right Now&nbsp;</strong></p> <p>Sales, Customer Success, and go-to-market teams need to open one system and trust what they see — today they can't. And as the platform scales, onboarding has to become a repeatable machine instead of a per-customer rescue effort. These aren't future problems; they're live ones. The first months of this role are deliberately concrete: specific systems, specific deliverables, measured outcomes. But the mandate behind them is bigger — every system the platform adds and every AI capability the company builds will sit on the customer data foundation this person establishes.&nbsp;</p> <h3 data-start="227" data-end="249">&nbsp;</h3> <p data-start="251" data-end="277"><strong data-start="251" data-end="275">What You'll Own</strong></p> <ul data-start="278" data-end="872"> <li data-start="278" data-end="493"> <p data-start="280" data-end="493"><strong>Own</strong> — Reconciliation of customer data across systems: pull a clean customer list from the backend into the CRM — no duplicates, no ghost accounts — audit what's already in HubSpot (call logs, deal history, contacts), and make the call on what stays, what gets cleaned, and what gets automated.</p> </li> <li data-start="494" data-end="652"> <p data-start="496" data-end="652"><strong>Build</strong> — A live two-way integration between HubSpot and the backend: data flows automatically, actions trigger from HubSpot, logic stays in the backend.</p> </li> <li data-start="653" data-end="755"> <p data-start="655" data-end="755"><strong>Establish</strong> — One trusted place to generate sales pipeline, retention rate, customer health, and all other sales, customer success, and go-to-market reporting.</p> </li> <li data-start="756" data-end="872"> <p data-start="758" data-end="872"><strong>Run</strong> — Customer onboarding data-mapping sessions directly with labs.</p> </li> </ul> <ul data-start="910" data-end="1254"> <li data-start="910" data-end="1042"> <p data-start="912" data-end="1042"><strong>Deliver</strong> — A written brief for engineering: where labs hit friction during mapping, what's causing it, and what to fix so labs can complete it independently.</p> </li> <li data-start="1043" data-end="1143"> <p data-start="1045" data-end="1143"><strong>Coordinate</strong> — With Customer Success on onboarding sessions and with our contracted HubSpot partner on integration.</p> </li> <li data-start="1144" data-end="1254"> <p data-start="1146" data-end="1254"><strong>Grow</strong> — Into the data foundation itself. As the early goals land, the scope expands toward owning and scaling customer onboarding as a repeatable machine — and toward the broader work of making EviSmart's data trustworthy end to end, across every system it touches.</p> </li> </ul> <p data-start="1256" data-end="1286">&nbsp;</p> <p data-start="1256" data-end="1286"><strong data-start="1256" data-end="1284">What You'll Get</strong></p> <ul data-start="1287" data-end="1619"> <li data-start="1287" data-end="1392"> <p data-start="1289" data-end="1392">A foundation-level seat: the data layer you build is what sales reporting, customer success, and the platform's AI and analytics ambitions will run on.</p> </li> <li data-start="1393" data-end="1485"> <p data-start="1395" data-end="1485">Direct customer contact from week one — labs across 28 countries, real workflows, immediate feedback on whether your work holds up.</p> </li> <li class="font-claude-response-body whitespace-normal break-words pl-2">Concrete goals with real gates: this role is defined by deliverables and measurable outcomes, not vague mandates.</li> <li class="font-claude-response-body whitespace-normal break-words pl-2">A role built to grow — the scope expands as the foundation you build proves out.</li> <li class="whitespace-normal break-words pl-2">Competitive compensation with salary range disclosed at offer.</li> </ul> <p><span data-ccp-props="{&quot;134233117&quot;:false,&quot;134233118&quot;:false,&quot;335559738&quot;:240,&quot;335559739&quot;:240}">&nbsp;</span></p> <p><strong>How We Work</strong></p> <p><span data-contrast="none">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.</span></p> <p>&nbsp;</p> <p><strong><span data-contrast="none">The Question You're Probably Asking&nbsp;</span></strong></p> <p><em><span data-contrast="none">"'Is this a CRM admin job?' No. The CRM is where the data problem surfaces first, so it's the first proving ground — but the work is data engineering end to end: cleansing, integration, sync logic, reporting architecture, and reconciling what the backend, the CRM, and the customer's own data each believe is true."</span></em></p> <p><em><span data-contrast="none"><strong>— EviSmart Talent Team</strong></span></em></p> <p>&nbsp;</p> <p><strong><span data-contrast="none">What We Need</span></strong></p> <ul> <li class="font-claude-response-body whitespace-normal break-words pl-2" style="line-height: 2;">Bachelor's degree in Statistics, Computer Science, Data Science, Economics, or a related field.</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" style="line-height: 2;">4–5 years of professional experience in data analysis, data engineering, or solutions/implementation engineering.</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" style="line-height: 2;">Advanced SQL skills (joins, CTEs, window functions, subqueries).</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" style="line-height: 2;">Proficiency in Python for data analysis and workflow automation.</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" style="line-height: 2;">Experience with ETL/ELT pipelines and workflow automation.</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" style="line-height: 2;">Hands-on CRM data experience — auditing, cleansing, deduplication, and data migration. HubSpot strongly preferred.</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" style="line-height: 2;">Systems integration experience — building or maintaining two-way integrations between platforms (APIs, middleware, sync logic).</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" style="line-height: 2;">Familiarity with Git/GitHub for version control and collaboration.</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" style="line-height: 2;">Comfortable running customer-facing working sessions and explaining data configuration to non-technical users.</li> <li class="font-claude-response-body whitespace-normal break-words pl-2" style="line-height: 2;">Able to translate customer friction into clear, actionable briefs for engineering.</li> </ul> <p><strong><span data-contrast="none">Apply today @&nbsp;<a href="https://evismart.com/careers" target="_blank">Evismart Careers&nbsp;</a></span></strong></p>