Senior Software Engineer (.NET Ecosystem)

Overview

Own the ClickHouse .NET client and its ecosystem, including the ADO.NET, Dapper and Entity Framework Core integrations, deciding what the client should do from user evidence and building it with deep .NET expertise.

What you'll do

• Know who uses the client and what they are trying to do; define what good looks like (time to first query, error clarity, adoption by key integrations), measure it, and let it drive the roadmap.
• Be the voice of ClickHouse for .NET developers: speak at .NET conferences and meet-ups, and write posts, tutorials and samples that developers and AI assistants find when searching 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 dependents.
• 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; if you write C++, contribute to it directly.
• Write proposals about where to invest next, setting direction rather than waiting 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 adopting.
• 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 the AI development platform with workflows for maintaining the clients: consistency checks across languages, issue triage, release checks.

What you'll need

• Product-minded: decide what to build from user evidence, measure whether it worked, and 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; reasoning about throughput and latency down to allocations and bytes on the wire, proven with tests and benchmarks.
• Fluent in C#, and productive in at least one more client language (Python, JavaScript, Java, Go, Rust, C++).
• Built or substantially extended a library other engineers depend on, and shipped NuGet packages across .NET Framework and modern .NET; treats 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, with experience shipping a library into enterprise environments and knowing what security, compliance and procurement teams look for in a dependency.
• Enthusiastic about working in public: given talks or written technical content, or keen to.
• 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.

Details

• Location: Berlin.
• Remote-friendly; the team is small, senior and remote across North America and EMEA.