Data Engineer

Design and build the architecture underneath both client engagements and a product portfolio built to scale well beyond where it is today. This isn't a maintenance seat.

Architecting the Future: Our Data Engineering Role

We're hiring a Data Engineer to design and build the architecture underneath both client engagements and a product portfolio built to scale well beyond where it is today. This isn't a maintenance seat. It's the seat where the next major architecture decision has your name attached to it, and where what you build this quarter is still running the show two years from now.

What You'll Do

• Design and build data pipelines, ELT/ETL processes, and data models across client and product environments, with real technical ownership from sprint one.
• Contribute to Well-Architected Framework-aligned architecture assessments and target-state designs for enterprise clients.
• Build and scale the data infrastructure powering a product portfolio designed to grow well past its current footprint.
• Sit directly with technical leadership on architecture calls, technical debt trade-offs, and build-vs-buy decisions, not three layers removed from where they get made.
• Document architecture clearly enough for a non-technical executive to sign off on, a skill that compounds your value everywhere you go after this.

What You Bring

• 3-5 years' experience as a data engineer, ideally with both greenfield build and legacy/enterprise migration exposure.
• Strong SQL, Python, and hands-on experience with a modern cloud data stack.
• Experience with pipeline orchestration (e.g. Airflow, Data Factory, dbt) and version-controlled infrastructure.
• The instinct to build for scale, because what you ship here isn't a one-off, it's infrastructure for a company on a genuine growth trajectory.
• Ability to explain architecture trade-offs to both engineers and executives.

Nice to Have

• Experience with AI/ML pipeline architecture (feature stores, vector databases, RAG infrastructure).
• Exposure to insurance, financial services, or regulated data environments.

Why This Is the Move

• Architecture with your name on it: real ownership of decisions that shape the company's technical foundation, not ticket-driven maintenance work on someone else's system.
• A rare dual credential: enterprise-grade client architecture and modern product engineering in one role, the kind of breadth that defines a career, not just a CV line.
• Speed as a feature: technical calls get made in days here, not committee cycles, so your ideas ship instead of waiting in a queue.
• Early-team trajectory: you're building the engineering foundation of a company still writing its growth story, and you're in the room while it happens.