DATA ENGINEER / ARCHITECT

Meroka•Montreal, QC

1d•Hybrid

About The Position

Every business we acquire arrives with its own data — its own systems, its own schemas, its own decades of quirks — and none of it was designed to talk to anything else. Making sense of that, and building the architecture that lets it all connect, is one of the most important things we do. This role owns it: the data foundations that everything we build sits on top of. We're looking for someone who's genuinely comfortable in that ambiguity — mapping data fields between systems that were never meant to align, standing up integrations, and designing the architecture of large data systems from scratch. There's a real spectrum to how technical this can be, and we'll shape the role around your strengths. You'll have deep ownership over how our data is structured, moved, and trusted across the company.

Requirements

You've designed data architecture or infrastructure for real, large systems — ideally more than once.
You're at home mapping and integrating messy, mismatched data from scratch, and you like the puzzle.
Strong instincts for data modeling, pipelines, and the trade-offs that keep a system reliable as it grows.
You thrive in ambiguity and want deep ownership over the foundations, not just a piece of them.

Nice To Haves

Experience integrating data across acquisitions, mergers, or otherwise disparate systems.
Fluency with modern data tooling and cloud data platforms.
Interest in the physical, built world and the operational data that runs it.

Responsibilities

Design and own the architecture of our data systems — how data is modeled, stored, moved, and made reliable across the company.
Map and reconcile data across the different businesses we acquire, aligning systems that were never built to fit together.
Build and maintain the integrations and pipelines that connect acquired businesses into our platform.
Set the standards for data quality, structure, and access that everything else depends on.
Partner closely with engineering, product, and operations to make sure the data serves what we're building.