Senior Software Engineer - Cloud Partner Integrations

ClickHouse ClickHouse · Data AI · EMEA · Integrations Engineering

Senior Software Engineer focused on Cloud Partner Integrations for ClickHouse, a company specializing in real-time analytics, data warehousing, observability, and AI workloads. The role involves end-to-end ownership of integrations, including design, development, and production systems, with a focus on working within external platform constraints and ensuring ClickHouse is a first-class citizen in various environments.

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

  • backend software engineering
  • systems engineering
  • auth protocols
  • identity federation
  • JavaScript
  • TypeScript

Nice to have

  • major cloud data or analytics platform ecosystem
  • partner marketplace or certification process
  • multi-tenant SaaS platforms
  • ClickHouse
  • columnar / OLAP engine

What the JD emphasized

  • end-to-end ownership
  • setting the technical defaults
  • owning the architecture
  • Running what you build
  • owning the infrastructure, CI, deployment, and observability
  • working on top of external platforms you can't change
  • partnering closely with the internal teams whose services you depend on
  • 5+ years building software
  • Solid backend and systems instincts
  • worked with modern auth protocols, service principals, and identity federation
  • 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
  • mainly a backend engineer
  • comfortable enough in JavaScript / TypeScript
  • use AI tools well and honestly
  • write well