Remote .NET Software Engineer Jobs
Remote.NET Software Engineer jobs are open across the U.S. at remote-first firms and distributed engineering teams, with strong demand in sectors like enterprise software, financial services, and healthcare technology. Employers hiring remotely right now include WellSky, VetsEZ, and BV Teck. See the openings below and apply to the ones that match your experience.
Find JobsOverview
Showing 5 of 55+ Remote .NET Software Engineer jobs
Location
New York; Atlanta; Boston; Chicago; Detroit
Employment Type
Full time
Location Type
Remote
Department
Engineering
Compensation
- Premuim US Locations (Los Angles, New York, Washington)$167K – $238K • Offers Equity
- US General$147K – $215K • Offers Equity
For roles based in the United States, the typical starting salary range for this position is listed on the job posting. In certain locations, such as the San Francisco Bay Area, Seattle, and the New York City Metro Area, a premium market range may apply, as listed.
These salary ranges reflect what we reasonably and in good faith believe to be the minimum and maximum pay for this role at the time of posting. The actual compensation may be higher or lower than the amounts listed, and the ranges may be subject to future adjustments.
An individual’s placement within the range will depend on various factors, including (but not limited to) education, qualifications, certifications, experience, skills, location, performance, and the needs of the business or organization.
If you have any questions or comments about compensation as a candidate, please get in touch with us at paytransparency [at] clickhouse [dot] com.
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 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 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.
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.
Compensation Range: $147K - $238K
Location
New York; Atlanta; Boston; Chicago; Detroit
Employment Type
Full time
Location Type
Remote
Department
Engineering
Compensation
- Premuim US Locations (Los Angles, New York, Washington)$167K – $238K • Offers Equity
- US General$147K – $215K • Offers Equity
For roles based in the United States, the typical starting salary range for this position is listed on the job posting. In certain locations, such as the San Francisco Bay Area, Seattle, and the New York City Metro Area, a premium market range may apply, as listed.
These salary ranges reflect what we reasonably and in good faith believe to be the minimum and maximum pay for this role at the time of posting. The actual compensation may be higher or lower than the amounts listed, and the ranges may be subject to future adjustments.
An individual’s placement within the range will depend on various factors, including (but not limited to) education, qualifications, certifications, experience, skills, location, performance, and the needs of the business or organization.
If you have any questions or comments about compensation as a candidate, please get in touch with us at paytransparency [at] clickhouse [dot] com.
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 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 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.
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.
Compensation Range: $147K - $238K
See All 55 Remote .NET Software Engineer Jobs
Find roles that match your experience and apply in just a few clicks.
Find JobsRemote .NET Software Engineer Job Market
Who's Hiring
Top Industries Hiring
- Technology & Software
- Hospitality & Tourism
- Healthcare & Medical Services
- Consulting & Professional Services
What Employers Look For
The qualifications that appear most often in remote .NET software engineer jobs.
- Proficiency in C# and the .NET ecosystem including Core and Framework versions
- Experience building and consuming RESTful APIs and web services
- Familiarity with SQL Server or another relational database and ORM tools like Entity Framework
- Hands-on cloud experience with Azure or AWS for deployment and infrastructure
- Knowledge of software design patterns, SOLID principles, and clean architecture
- Bachelor's degree in computer science, software engineering, or a related technical field
Tips for Your Remote .NET Software Engineer Job Search
Apply early to remote roles that fit
Migrate Mate lists remote .net software engineer openings from across the U.S. in one place. Search roles by the skills and stack you know, then apply directly to the ones that match your experience before the applicant pool grows.
Show async collaboration on your resume
Remote engineering teams look for candidates who have shipped code without in-person oversight. Call out tools like GitHub pull requests, Jira, and Confluence in your work history to signal you can collaborate across time zones without daily standups.
Build a public .NET portfolio before applying
Distributed teams screen for self-starters who can demonstrate initiative. Push C# and .NET projects to a public GitHub repository, include a clear README for each one, and link the repository in your resume so hiring managers can verify your skills before the first interview.
Prepare for asynchronous technical screens
Many remote .net software engineer interviews include take-home assessments or recorded coding sessions instead of live whiteboard rounds. Practice writing clean, well-commented C# code that explains your reasoning, because the reviewer will not be able to ask follow-up questions in real time.
Remote .NET Software Engineer Jobs: Frequently Asked Questions
How do I get a remote.net software engineer job?
Remote.net software engineer roles go to candidates who can demonstrate self-direction and clear written communication alongside strong technical skills. Remote-first companies and distributed teams screen for proficiency in C#, the.NET ecosystem, and version control, but they also look hard at how you document decisions, communicate asynchronously, and ship without in-person oversight. A portfolio of shipped projects and experience with remote-friendly workflows like pull-request reviews and async standups gives you a real edge.
Which companies hire remote.net software engineers?
Companies hiring remote.net software engineers right now include WellSky, VetsEZ, and BV Teck, based on current remote listings on Migrate Mate as of November 2026. Remote-first software companies, distributed fintech teams, and enterprise technology firms account for the largest share of these openings.
Can you get a remote.net software engineer job with no experience?
Yes, but remote entry-level.net software engineer roles are harder to land because employers expect you to work independently from day one with minimal hand-holding. The companies most open to entry-level remote candidates are smaller remote-first startups and product agencies. What opens the door is a GitHub portfolio of.NET or C# projects, contributions to open-source repositories, and demonstrated comfort with async collaboration tools like GitHub, Jira, and Slack.
Do you need a degree for remote.net software engineer jobs?
Not always. Remote employers hiring.net software engineers consistently weigh demonstrated coding ability, a portfolio of shipped work, and real-world familiarity with the.NET stack over formal credentials. A degree can help you clear applicant tracking filters at larger companies, but many remote-first firms and distributed teams care more about what you have built, how you communicate in writing, and whether your code holds up in a technical screen.
Which industries hire the most remote.net software engineers?
Remote.net software engineer roles concentrate in Technology & Software, Hospitality & Tourism, and Healthcare & Medical Services, based on current remote listings on Migrate Mate as of November 2026. These sectors rely on distributed engineering teams that build and maintain complex backend systems, enterprise applications, and APIs where.NET is a standard part of the stack.
See All 55 Remote .NET Software Engineer Jobs
Find roles that match your experience and apply in just a few clicks.
Find Jobs