Skip to content

Open nowPosted 19 hours ago

Staff Engineer, Datastores

nue.io1 open role

Where
Canada (Toronto), Canada (remote)
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowStaff Engineer, Datastoresnue.io · Canada (Toronto), Canada (remote)
  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on nue.io's own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

13.4% of postings close within 7 days. Measured by our own scanner across the market.

Share of postings closed within
  1. 2.2%1 day
  2. 4.6%3 days
  3. 13.4%7 days
  4. 21.6%14 days
  5. 36.2%30 days
  6. 59.0%60 days
This job: posted 19 hours ago

The posting

Why you'll love this Nue.io opportunity!

We're looking for a Staff Engineer, Datastores to be the technical lead for every system at Nue that stores, moves, and serves data. You'll set the long-term direction for our datastore platform, own its reliability, performance, and cost, and get it ready for 10x growth, while staying hands-on with the hardest problems. This is not a traditional DBA role, and it's broader than a single engine. Our data layer is polyglot: PostgreSQL on AWS (RDS, NeonDB) runs our multi-tenant transactional workloads, ClickHouse runs analytics and reporting, and caching and streaming systems connect them. As a dedicated datastore lead, you'll decide how these systems fit together, which workloads belong where, and the standards every product team follows. Then you'll lead the move to a highly scalable, highly available architecture. If you want company-wide scope, deep technical ownership, and the chance to build the datastore function from the ground up at a fast-growing SaaS company, this is the role for you.

Responsibilities

Set the datastore strategy — Own the multi-year technical vision and roadmap for Nue's data layer across PostgreSQL, ClickHouse, caching, and streaming, and align engineering leadership behind it. Own the fleet end to end — Be accountable for the reliability, availability, performance, and cost of every production datastore, and define the SLOs, error budgets, and operational standards they're held to. Lead the scale-out architecture — Assess how our multi-tenant data layer needs to grow, choose the right approach (partitioning, read scaling, tenant isolation, sharding, or a different datastore), and deliver it, including tenant placement and online rebalancing where needed, to support 10x growth. Lead the migration to fully managed, highly available PostgreSQL — Define the strategy, testing plan, and rollout for moving off self-managed RDS instances (Aurora/NeonDB), with zero data loss and minimal downtime. Own the analytics data layer — Lead ClickHouse architecture, including table engines, partitioning and ordering keys, materialized views, and the CDC and ingestion pipelines (e.g., Kafka, ClickPipes) that keep it in sync with our transactional systems. Decide what belongs where — Guide product teams on the right datastore and data model for each workload (OLTP, OLAP, cache, queue), and prevent sprawl with clear patterns and paved paths. Make performance proactive — Build the monitoring, alerting, load testing, and capacity models that catch slow queries, replication lag, connection saturation, merge pressure, and storage growth before customers do, and answer "How many more customers can we support?" with data. Architect for resilience — Own replication topologies, read/write separation, failover, backup and restore, and disaster recovery, with RPO/RTO targets that are defined, tested, and met through regular drills. Enable safe, continuous delivery — Establish zero-downtime schema migration practices (backward- and forward-compatible changes, online DDL, migration tooling in CI/CD) that every team uses. Raise the bar across engineering — Review schema and query designs, write the standards and design docs others build on, mentor engineers, and act as a force multiplier for Billing, Lifecycle, Data & Integrations, and DevEx. Secure the data layer — Own encryption in transit and at rest, access controls, secrets rotation, tenant isolation, and audit logging in line with SOC 2 Type II and GDPR. Lead with AI-powered tooling — Use AI throughout the role, from migration planning and query optimization to runbook automation and incident response, and set the example for how the team uses it. Be one of the team — You're a full member of the Infrastructure & Security team, not a specialist on the side. You take your turn on on-call, help ship releases, fix broken CI/CD pipelines, and pick up general infrastructure work when the team needs it, and you lead the response to major datastore incidents. Grow the function — Shape how datastore engineering grows at Nue, including hiring, onboarding, and the operating model as the team scales.

What We’re Looking For

10+ years in backend, infrastructure, or data platform engineering, including 5+ years owning production databases at scale in SaaS environments. A track record of Staff-level impact — you've set technical direction across multiple teams, led multi-quarter initiatives to completion, and aligned senior engineers and leadership around hard trade-offs. Expert-level PostgreSQL — internals (MVCC, vacuum, WAL, the planner), query optimization and EXPLAIN analysis, indexing, partitioning, and replication. Hands-on experience with a columnar/OLAP datastore, ideally ClickHouse (or Druid, Pinot, Snowflake, BigQuery): schema design, ingestion, and performance tuning for analytical workloads. Designed and operated horizontally scaled, multi-tenant database architectures (e.g., partitioning, read scaling, sharding) and replication topologies in production. Led large-scale database migrations with zero data loss and minimal downtime. Deep experience with managed databases on AWS — RDS, Aurora, and/or serverless PostgreSQL (NeonDB, Aurora Serverless v2, Supabase, etc.). Strong observability practice — CloudWatch, pganalyze, HyperDX, Datadog, or similar — including defining and running to SLOs. Solid platform engineering foundations — Infrastructure as Code (Terraform/OpenTofu, CloudFormation), connection pooling (PgBouncer, RDS Proxy), schema migration tooling (Flyway, Liquibase, or similar), and strong scripting (Python, Bash). Deep, hands-on fluency with AI coding agents and developer tools (e.g., Claude, Cursor, Copilot, Codex), with good instincts for where they create leverage. Excellent written and verbal communication — you can write the design doc, explain trade-offs to executives, and build consensus across teams. Team-first and hands-on — you thrive on a small infrastructure team where everyone shares releases, on-call, and pipeline work, and you'd rather fix the broken build than wait for someone else to. Bachelor's degree in Computer Science, Engineering, or equivalent practical experience.

Preferred Skills

Experience with in-memory datastores (Redis, Memcached) and streaming/CDC systems (Kafka, Debezium, ClickPipes). Experience with MySQL/MariaDB or NoSQL datastores (e.g., DynamoDB). Experience building internal data platforms or self-service database tooling for product teams. Experience with SOC 2, GDPR, or other compliance frameworks as they apply to data management. Domain knowledge in revenue operations, billing, or financial systems, where correctness and auditability matter. Experience with GitLab CI/CD pipelines. Contributions to open-source database projects, or public talks and writing on database engineering.

What Success Looks Like

A datastore strategy is in place and followed — A roadmap covering PostgreSQL, ClickHouse, caching, and streaming is published, backed by engineering leadership, and used by product teams to decide where new workloads go. The migration to fully managed PostgreSQL is complete — Planned, tested, and rolled out with zero data loss and minimal downtime, replacing self-managed RDS instances. The data layer is ready for 10x growth — A scaling approach is chosen on evidence, documented, and running in production, with clear headroom for 10x customer growth. Analytics scales independently — ClickHouse ingestion, schema, and query performance meet defined SLOs, and analytical load stays off the transactional databases. Reliability is measured, not hoped for — Every critical datastore has SLOs and error budgets, monitoring catches issues before customers do, and DR meets RPO/RTO targets in regular drills. AI is embedded across datastore operations — AI tooling is used every day for migration planning, query optimization, runbook automation, and operations: a force multiplier, not an afterthought. You're the go-to technical leader for data — Product engineering squads (Billing, Lifecycle, Data & Integrations, DevEx) bring you in early on schema design and data architecture, and the standards you set are how Nue builds.

Why You'll Love It

The opportunity to found and lead Nue's datastore function — company-wide scope, high ownership, and direct influence on our architecture. A collaborative and supportive team that invests in your growth, with a clear Staff+ individual contributor path. Flexible remote/hybrid work arrangement within Canada. The chance to work on challenging infrastructure problems at a company scaling rapidly in the revenue lifecycle space.

From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against nue.io's own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.
  3. We apply on nue.io's form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.
  4. Every reply, sorted

    nue.io's answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.
  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

By hand5–10
With CV Rocket100
applications a day

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.