Senior Software Engineer (.NET Ecosystem)

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. Each client has a primary owner, but no client belongs to one person: we review and co-maintain across languages and decide cross-client questions together.

The role

We're looking for a product-minded engineer to own the ClickHouse .NET client. You'll decide what the client should do by talking to the developers who use it, reading the issues and the telemetry, and listening to the community. Then you'll build it, with deep .NET expertise, and measure whether it worked. Your scope is the SDK and what builds on it: ADO.NET , Dapper and Entity Framework Core users, and the tools and integrations that depend on your client.

What you'll do

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

Be the voice of ClickHouse for .NET developers. Speak at .NET conferences and meet-ups, and write the posts, tutorials and samples that developers and AI assistants find when they search for how to use ClickHouse from .NET (SEO and GEO). Answer questions where the community asks them.

Own the .NET client and its ecosystem: the client, the EF Core provider and ORM integrations, NuGet releases and support. Evolve it without breaking the people who depend on it.

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

Bring what .NET and Windows users need to the ODBC driver, since that's how many Windows and BI tools reach ClickHouse. If you write C++, contribute to it directly.

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

Make the client enterprise-ready: TLS and certificate handling, authentication including Microsoft Entra ID, safe credential handling, signed and reproducible packages, and the audit and compliance questions large .NET shops ask before they adopt.

Shape the client 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. You decide what to build from user evidence, measure whether it worked, and can explain what you chose not to build.

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

Deep C# and .NET expertise: memory management, async and the TPL, Span and pooling, profiling and benchmarking. You reason about throughput and latency down to allocations and bytes on the wire, and you prove it with tests and benchmarks.

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

You've built or substantially extended a library other engineers depend on, and shipped NuGet packages across .NET Framework and modern .NET. You treat breaking changes accordingly.

Fluent in .NET data access ( ADO.NET , Dapper, EF Core) and at home in the wider .NET ecosystem: ASP.NET Core, Aspire, NuGet.

Security-minded. You've shipped a library into enterprise environments and know what security, compliance and procurement teams look for in a dependency.

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.

Thoughtful use of AI development tools, with the judgment to review what comes out.

Clear writing. Most coordination happens in design docs, PRs and RFCs.

Nice to have

ClickHouse, especially its type system, or another OLAP engine.

C++ and ODBC driver internals.

Building or maintaining an ADO.NET or EF Core provider.

Open-source contributions to .NET or data infrastructure.

Experience designing SDKs, docs or error messages with AI coding agents as the consumer.

Protocol or wire-format work on a database driver or network client.

Learn more

Introducing the (blazing fast!) native TCP client for .NET : zero-copy columnar reads, 1.5 to 2x faster than HTTP, over 99% fewer GC allocations (Oct 2026)

What's new in the ClickHouse .NET Driver: the road from 1.0 to 1.3 (Aug 2026)

Meet GroeneAI: our autonomous contributor to ClickHouse (Oct 2026)

Building a .NET API Gateway with ClickHouse and Aspire (Jun 2026)

The .NET client on GitHub and its documentation

ClickHouse Workload for Microsoft Fabric, now in public preview (Sep 2026)

Perks

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 team member who joins our company receives stock options.

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.

Culture - We All Shape It

As part of a rapidly scaling start-up, you will be instrumental in shaping our culture.

Are you interested in finding out more about our culture? Learn more about our values here . Check out our blog posts or follow us on LinkedIn to find out more about what’s happening at ClickHouse.

Equal Opportunity & Privacy

ClickHouse provides equal employment opportunities to all employees and applicants and prohibits discrimination and harassment of any type based on factors such as race, color, religion, age, sex, national origin, disability status, genetics, protected veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by federal, state or local laws.

Please see here for our Privacy Statement.