Senior Software Engineer (.NET)

About the Role

We’re looking for a Senior Software Engineer who enjoys finding and fixing bugs. You’ll work on our customer-facing web app and internal tools, taking each issue from the first report to a tested fix in production.

This is a hands-on coding role, not just ticket sorting. You’ll reproduce issues on your own machine, find the root cause, write the fix in C# or JavaScript/TypeScript, add tests so the bug doesn’t come back, and send it through code review.

What You’ll Be Working With

Much of our code is older and has grown quickly over the years. Expect large backend files, a mix of older server-rendered pages and newer React components, legacy jQuery, and complex SQL databases. You should enjoy digging into unfamiliar code, figuring out how it works, and making small, safe changes that don’t break anything else.

Fix bugs end to end: Reproduce the issue, find the cause, write the fix, and confirm it works in production.

Work in older code: Troubleshoot .NET/C#, SQL, server-rendered templates, jQuery, and React, often using the code itself as the main documentation.

Keep Jira tickets clear: Record steps to reproduce, the root cause, and how the fix was verified, so engineering and support stay on the same page.

Clarify unclear reports: Work with whoever submitted the ticket to get missing details, logs, or context before starting.

Make small, safe fixes: Write focused pull requests that follow existing patterns and keep risk low.

Work independently: Manage and prioritize your own ticket queue, and know when to ask for help instead of getting stuck.

Experience: 4+ years debugging and writing code in software development, application support, or Tier 3 technical support.

Backend: Able to read and debug C# in ASP.NET MVC or ASP.NET Core apps.

Frontend: Comfortable debugging React and JavaScript/TypeScript, older jQuery code, and Razor (.cshtml) templates.

Databases: Solid SQL skills (SQL Server preferred, PostgreSQL is fine), including writing queries to investigate issues and understanding ORM data models

Git: Comfortable with branching, pull requests, reviewing changes, and using git history/blame to investigate.

Ownership: Organized and accountable; you manage your time well and see tickets through to completion.

Communication: Able to explain technical findings clearly in writing, especially in Jira tickets and pull requests.