ClickHouse logo

ClickHouse

More roles at ClickHouse

Senior Software Engineer - Cloud Partner Integrations

Work from home

Remote role where the employee must remain based in a particular country.

Listed for United States

From the listing details: Source listing states candidate location: "United States, Remote"

Employer listed it 4 months ago · Added 8 weeks ago

Been open since 4 months ago. Long-running listings are sometimes left up after the role is filled.

Salary

$155k to $238k per year

Location

Listed for United States

Work style

Async

Contract

Full-time

Experience

Senior

Category

Software

Published by the employer

What the advert says

Quoted word for word from the employer's advert. Where it says nothing, we say so.

Working hours
Most of how we coordinate happens async in chats, design docs and RFCs
Where you can work from
Location eligibility not confirmed
Contract
Not mentioned in the advert
Experience asked for
Not mentioned in the advert
Pay
A USD$500 Home office setup if you’re a remote employee.

Remote flexibility

Work from home

This is a remote role, but the employee must be based in United States. It is work from home rather than work from anywhere.

What the employer says

  • Source listing states candidate location: "United States, Remote"

What Nomaders makes of it

  • Residency required in United States
  • Payroll and tax are likely handled in that country only

The quotes above are the employer's own words; the reading is ours. Always check the original listing and employment terms before working from another country.

Before you apply

Questions worth asking: Nomaders interpretation

  • The advert does not say where you can be based. Ask which countries they can legally employ or contract you from.
  • The advert does not say whether this is employment or a contractor arrangement. Ask, as it affects tax and benefits.

Produced automatically from this advert's text; not reviewed by a person. The employer's own page is the final word.

About the role

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

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

Benefits

  • ·Flexible work environment - ClickHouse is a globally distributed company and remote-friendly. We currently operate in over 25 countries.
  • ·Healthcare - Employer contributions towards your healthcare.
  • ·Equity in the company - Every new eligible team member who joins our company receives equity.
  • ·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.

How to apply

  1. 1Check the flexibility label above, work from home, matches where you plan to live and work.
  2. 2Tailor your CV to the role at ClickHouse, mentioning your remote working experience and working hours (Async).
  3. 3Apply directly on the employer's careers page using the button below. Nomaders never handles your application.

Found 2mo ago. Last checked today. Always confirm the details on the original posting, salary and location can change after publication.

Listing sourced from Company boards.

Similar roles

Other open software roles with comparable remote rules.

Browse all open roles

$155k to $238k per year · You'll be taken to the employer's careers page.