Senior Software Engineer - Cloud Partner Integrations

ClickHouse ClickHouse · Data AI · EMEA · Integrations Engineering

Senior Software Engineer focused on building cloud partner integrations for ClickHouse, a real-time analytics and data warehousing platform that also supports AI workloads. The role involves end-to-end ownership of integrations, including design, coding, and production systems, with a focus on auth, multi-tenancy, data movement, performance, and observability. The engineer will work across trust boundaries with external platforms and partner teams.

What you'd actually do

  1. Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production
  2. Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it
  3. Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't
  4. Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked

Skills

Required

  • 5+ years building software
  • backend and systems instincts
  • reason about deployment topology, multi-tenancy, and data movement
  • comfortable owning architectural tradeoffs
  • worked with modern auth protocols, service principals, and identity federation
  • get it right across a trust boundary
  • built on someone else's platform
  • comfortable in ambiguity
  • ship before the spec is finished
  • make sensible calls under uncertainty
  • flag the decisions that'll be hard to undo
  • good with other engineers
  • backend engineer
  • comfortable enough in JavaScript / TypeScript
  • use AI tools well and honestly
  • write well

Nice to have

  • Familiarity with a major cloud data or analytics platform ecosystem
  • Real depth in auth and identity federation
  • experience shipping through a partner marketplace or certification process
  • Experience designing multi-tenant SaaS platforms
  • isolation and deployment topology behind them
  • Working knowledge of ClickHouse, or another columnar / OLAP engine

What the JD emphasized

  • end-to-end ownership
  • production system
  • technical defaults
  • thin documentation
  • unfamiliar deployment topologies
  • timelines governed by partner approval cycles
  • engineering across trust boundaries
  • owning the infrastructure, CI, deployment, and observability
  • external platforms you can't change
  • risks are yours to manage
  • partnering closely with the internal teams whose services you depend on
  • agreeing on interfaces
  • keeping moving instead of waiting around to be unblocked
  • ship before the spec is finished
  • make sensible calls under uncertainty
  • flag the decisions that'll be hard to undo