Copy of Senior Software Engineer - Cloud Partner Integrations

About the Team 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 About You 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 Nice to Have None of these are required, but any of them would be a bonus: 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 ce