Senior Software Engineer – Cloud Partner Integrations

ClickHouse

Senior Software Engineer owning end-to-end integrations for ClickHouse Cloud. Collaborating with internal teams, handling architecture, and working with external platforms.

Posted 7/15/2026full-timeRemote • 🇺🇸 United StatesSenior💰 $141,000 - $208,000 per yearWebsite

Core Competencies

Role fit

Core Competencies

Use this summary to align your resume positioning with the role.

Demonstrates expertise in backend engineering, particularly in designing and managing data-heavy integration systems, while effectively collaborating with cross-functional teams. Proficient in modern authentication protocols and capable of navigating ambiguity in software development.

Highest-signal resume keywords

Backend EngineeringData MovementModern Auth ProtocolsMulti-TenancyJavaScript / TypeScript

ATS Keywords

Tailor your resume

Applicant Tracking System Keywords

Tip: use these terms in your resume and cover letter to boost ATS matches.

Hard Skills

Software DevelopmentIntegration SystemsArchitectural TradeoffsDeployment TopologyIdentity FederationCI/CDObservabilitySaaS Platform DesignOLAP Engine KnowledgeCloud Data Ecosystem Familiarity

Soft Skills

CollaborationCommunicationTrust BuildingProblem SolvingAdaptability

Tools & Technologies

Claude CodeCursorCopilotDesign DocsPRsRFCs

Industry Keywords

Data-Heavy SystemsIntegrationAuth and Identity FlowsTrust Boundary ManagementPartner Marketplace Experience

Tech Stack

Tools & technologies

CloudJavaScriptTypeScript

About the role

Key responsibilities & impact

You'll own an integration end to end: the design, the code, and the production system that keeps running after launch.
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. 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.
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: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked.
Expecting you to have opinions about where this should go, and to write them down.

Requirements

What you’ll need

5+ years building software, with a good chunk of it on data-heavy or integration-flavored systems
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 instead of quietly baking 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 in JavaScript / TypeScript to jump in when it helps
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 in design docs, PRs, and RFCs.
None of these are required, but any of them would be a bonus: Familiarity with a major cloud data or analytics platform ecosystem, Real depth in auth and identity federation, or experience shipping through a partner marketplace or certification process, Experience designing multi-tenant SaaS platforms, or the isolation and deployment topology behind them, Working knowledge of ClickHouse, or another columnar / OLAP engine.

Benefits

Comp & perks

Flexible work environment - ClickHouse is a globally distributed company and remote-friendly. We currently operate in over 20 countries.
Healthcare - Employer contributions towards your healthcare.
Equity in the company - Every new team member who joins our company receives stock options.
Time off - Flexible time off in the US, generous entitlement in other countries.
A $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.