Skip to content
ClickHouse

Senior Software Engineer - Go SDK - Language Clients

New York; Detroit; Chicago; Atlanta; BostonRemote · United States
Senior · FullTime · Engineering
POSTED 18 NOVVERIFIED 3M AGO
Apply Ask
Role
0 days opentrue age
Closes in ~69d at the median (69d)
Posted 18 Nov · n=31
Payats field
$147k–238kposted
▲ +1% vs market median $191k
$147k$238k
Market p25–p75
$170k–$219k
ClickHouse p25–p75
$191k–$196kn=7
New York · n=369 · 365d to 15 Nov
CompanyClickHouse →
204open roles
Opened · 30d
+18
Closed · 30d
−23
Signal
● Steady−5 net
17d of snapshots · 30d window
Market
17,173open · Senior Software engineering
Opened · 7d
+1,1957% of open
All software engineering
74,992open
All tracked boards · live 18 Nov · n=17,173
Visa
4H-1B LCAs · FY26
PERM · FY25
2
Median wage
$200k
NL recognised sponsor
✓
LCAs FY26 · n=4 · to 2026-06-10
JavaScriptPythonGoJavaRustC++C#/.NETSQL

About the team

The Integrations Ecosystem org builds the drivers, SDKs, connectors and BI integrations that make ClickHouse feel native in any stack. The Language Clients team maintains the official clients for Python, JavaScript, Java, Go, Rust, C++ and C#, plus the ODBC, JDBC and ADBC drivers. We're small, senior and remote across North America and EMEA.

The role

We're looking for a product-minded engineer to own ClickHouse's Go clients. You'll decide what the clients should do by talking to the developers who use them, reading the issues and the telemetry, and listening to the community. Then you'll build it, with deep Go expertise, and measure whether it worked. Your scope is the SDK and what builds on it: clickhouse-go and ch-go, and the collectors, pipelines, agents and tools that write millions of rows per second through your code.

What you'll do

Know who uses the clients and what they're trying to do. Define what good looks like (time to first query, error clarity, throughput, adoption by key integrations), measure it, and let that drive the roadmap.

Be the voice of ClickHouse for Go developers. Speak at GopherCon and Go meetups, and write the posts, tutorials and examples that developers and AI assistants find when they search for how to use ClickHouse from Go (SEO and GEO). Answer questions where the community asks them.

Own the Go clients and their ecosystem: clickhouse-go, ch-go, database/sql, releases and support. Evolve them without breaking the people who depend on them.

Keep the clients the fastest Go option for the fastest analytical database, and make sure the client is never the bottleneck. Performance is part of every release, not an afterthought: profile, change, measure again, catch regressions in CI, and publish the numbers.

Partner with the projects built on the clients, from the OpenTelemetry Collector to ClickHouse Grafana datasource and ClickPipes, and catch their regressions before they ship.

Review and co-maintain other clients, and take part in cross-client decisions on types, errors and protocol features.

Bring written proposals about where we invest next. You set direction rather than wait for it.

Make the clients enterprise-ready: TLS and mTLS, cloud authentication, safe credential handling, vulnerability response, a small dependency footprint, and the questions large Go shops ask before they adopt.

Shape the clients for agents as users: an API, docs and error messages an AI coding agent can use correctly on the first try.

Extend our AI development platform, with new workflows for maintaining the clients: consistency checks across languages, issue triage, release checks.

About you

Product-minded with a bias for action. You'd rather run an experiment and bring back data than wait for approval, you measure whether it worked, and you can explain what you chose not to build.

5+ years in software, much of it on data-intensive systems: drivers, SDKs, ingestion, streaming, observability or analytics.

Deep Go expertise: the runtime and garbage collector, escape analysis, the memory model, pprof and the execution tracer. You reason about throughput and latency down to allocations and bytes on the wire, and you prove it with tests and benchmarks.

Strong Go concurrency instincts: context, goroutines and channels, bounded pools, backpressure, clean shutdown, and the leaks and races that come with each.

Beyond Go, productive in at least one more of our client languages (Python, JavaScript, Java, Rust, C++, C#). You'll review and co-own across clients.

You've built or substantially extended a Go module other engineers depend on. You understand semantic import versioning and treat breaking changes accordingly.

Strong grasp of database fundamentals: SQL, query execution and analytical workloads. Judgment about when to use database/sql and when to drop down to the protocol.

Enthusiastic about working in public. You've given talks or written technical content, or you're keen to, and you see it as part of the job rather than a distraction from it.

Source · ClickHouseFirst seen 18 NovOriginal ↗