Senior Software Engineer - Cloud Partner Integrations
- Discuss this with your agent
- Open in Claude
- Open in ChatGPT
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Role details
Tech stack
+5 more
Job description
Most providers make customers migrate their data to them. Weβre doing the opposite: bringing ClickHouse Cloud into the environments our customers already trust, so their data stays useful right where it lives.
Those environments come in a few shapes. Some are major cloud data platforms that run ClickHouse as a native service, so customers get it without leaving the tool they already use. Some are BI and visualization tools that need ClickHouse to show up as a fast, first-class data source behind their dashboards. And some are developer and data platforms we connect through marketplaces and identity federation with a couple of clicks or agentic calls. Every integration is unique, but the goal is the same every time: ClickHouse should feel like a first-class citizen in every environment.
The craft is finding the patterns underneath different integrations. As one of the first backend engineers, youβll help shape the technical defaults for this team. Youβll have end-to-end ownership, but youβll also work inside the constraints of platforms you donβt own: thin documentation, unfamiliar deployment topologies, and timelines governed by partner approval cycles. A lot of the challenge is engineering across trust boundaries you donβt fully control.
You wonβt be doing it alone. Youβll work closely with your engineering manager, the product manager, a growing team, and experienced engineers across the broader org. If that sounds like your kind of challenge, letβs talk.
What youβll do
Youβll own an integration end to end: the design, the code, and the production system that keeps running after launch. The patterns you set there become defaults the rest of the team builds on.
Day to day, that looks like:
- 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
- Running what you build. Which means owning the infrastructure, CI, deployment, observability behind it and on-call
- Working on top of external platforms you canβt change, and being straight about which risks are yours to manage and which arenβt
- Partnering closely with the internal teams whose services you depend on: iterating on product requirements, agreeing on interfaces and protocols, and proactively finding ways to keep moving
Requirements
These are the attributes of someone who will perform well in this role:
- 8+ years building software, with a good chunk of it on data-heavy or integration-flavored systems
- Preferably proficient in TypeScript or Go or comfortable contributing to each
- Solid backend and systems instincts. You can reason about deployment topology, multi-tenancy, and data movement, and youβre comfortable owning architectural tradeoffs youβll have to live with later
- Youβve worked with modern auth protocols, service principals, and identity federation, and you know how to get it right across a trust boundary
- Youβve built on someone elseβs platform and know what thatβs actually like: incomplete docs, unintended breaking changes, etc.
- Youβre comfortable in ambiguity. You can ship before the spec is finished, make sensible calls under uncertainty, and flag the decisions thatβll be hard to undo to your team before we bake them in.
- Youβre good with other engineers. Much of the work runs through teams you donβt own, and you earn their trust by how you think, not just what you commit.
- Youβre mainly a backend engineer, but youβre comfortable enough to touch a modern React app
- You use AI tools well and honestly. Reach for Claude Code, Cursor, Copilot, or whatever helps, and be clear about where you did and didnβt
- You write well. Most of how we coordinate happens async in chats, design docs and RFCs, * Close familiarity with a major cloud data or analytics platform ecosystem
- Real depth in auth and identity federation, or experience building to a partnerβs security review, marketplace requirements or certification requirements
- Hands-on experience designing multi-tenant SaaS platforms, or the isolation and deployment topology behind them
- Working knowledge of ClickHouse, or another columnar / OLAP engine
Benefits & conditions
- US Premium Locations (LA/NYC/Washington)$170K - $238K * Offers Equity
- US General $155K - $215K * Offers Equity
For roles based in the United States, the typical starting salary range for this position is listed on the job posting. In certain locations, such as the San Francisco Bay Area, Seattle, and the New York City Metro Area, a premium market range may apply, as listed.
These salary ranges reflect what we reasonably and in good faith believe to be the minimum and maximum pay for this role at the time of posting. The actual compensation may be higher or lower than the amounts listed, and the ranges may be subject to future adjustments., * Time off - Flexible time off in the US, generous entitlement in other countries.
- A USD$500 Home office setup if youβre a remote employee.
- Global Gatherings - We believe in the power of in-person connection and offer opportunities to engage with colleagues at company-wide offsites.
About the company
- Flexible work environment - ClickHouse is a globally distributed company and remote-friendly. We currently operate in over 25 countries.
Apply for this position
This job is hosted externally. Click below to view the full posting and apply.
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Good distractions
Loading talks and stories from around this roleβ¦