About this role
Job Summary:
Rausch Sturm LLP is looking for a Senior .NET Developer to own the backend and data layer of the systems that run our business. You will design and ship ASP.NET Core APIs, background services, and the T-SQL that sits underneath them — and you will keep the existing ones healthy. Both halves are the job. Correctness matters here, because the data is regulated (PCI DSS), and the downstream consequences of a bad record are real.
We move fast and the work is not always the work you planned. Production escalations, client-driven deadlines, and requests from other teams are a normal part of the week. We need someone who can pivot cleanly, triage under pressure, and then get back to what they were building — not someone who only functions with a quiet backlog.
Our backend platform spans roughly 40 .NET repositories: internal and partner-facing REST APIs, Windows and worker services, Azure Functions with Durable orchestrations, EDI interchange with major financial issuers, and document/PDF automation pipelines. Behind those sits a large SQL Server estate — thousands of stored procedures, functions, and tables across a dozen databases, all version-controlled with Flyway in Azure DevOps.
You will also help us finish modernizing. Some of the estate is on .NET 8/9; some are still on legacy .NET frameworks. Charting and executing that path is part of the job.
Essential Duties and Responsibilities:
- Design, build, and maintain ASP.NET Core Web APIs (REST, OpenAPI/Swagger, API versioning) consumed by internal apps, partner integrations, and Azure API Management.
- Write and tune T-SQL: stored procedures, functions, views, and indexes against a large, busy SQL Server estate. Diagnose slow plans, rewrite non-SARGable predicates, and choose set-based solutions over row-by-row ones.
- Build and support background processing — Windows services, .NET worker services, Quartz-scheduled jobs, and Azure Functions (including Durable Functions) for long-running and orchestrated workloads.
- Work in our document automation stack: PDF generation, splitting, merging, redaction, stamping, and OCR (Aspose, QuestPDF, Tesseract/IronOCR), plus Excel generation for reporting handoffs.
- Manage schema change through Flyway migrations in source control — no ad hoc production changes, ever.
- Instrument what you build: structured logging with Serilog, telemetry to Azure Application Insights, and alerting that catches failures before a client does.
- Maintain, debug, and improve existing applications and database code — including systems you did not write and code that predates the current standards. Meaningful ongoing maintenance is a permanent part of this role, not a temporary onboarding phase.
- Respond to production escalations: diagnose failed jobs and integrations, identify root cause, deliver a fix through the proper promotion path, and communicate status clearly while it is in flight.
- Shift priorities as the business requires — supporting other development teams, assisting operations, or taking on an urgent client request ahead of planned sprint work.
- Write unit and integration tests alongside your code (xUnit / MSTest / NUnit, Moq).
- Participate in code review, threat modeling, and the SDLC stage gates. Resolve CodeQL and dependency-scan findings before promotion.
Required Qualifications:
- 5+ years of professional C# / .NET development experience, including meaningful time on .NET Core / .NET 6+ (not just .NET Framework).
- 5+ years writing production T-SQL against SQL Server — you are comfortable being the person who owns a stored procedure, not just the person who calls one.
- Demonstrated ability to read an execution plan and act on it. Indexing strategy, SARGability, and set-based rewrites should be familiar territory.
- Strong ASP.NET Core Web API experience: dependency injection, middleware, configuration, authentication/authorization, and versioning.
- Practical experience with a data access approach in both directions — an ORM (Entity Framework Core) and direct SQL / micro-ORM (Dapper, Microsoft.Data.SqlClient).
- async/await fluency and an understanding of where concurrency bugs actually come from.
- Git-based source control with pull-request review discipline; comfortable in Azure DevOps (repos, boards, build/release pipelines).
- Secure coding fundamentals: parameterized queries, no secrets in source, no PII in logs, least-privilege service accounts, OWASP Top 10 awareness.
- Proven ability to maintain and troubleshoot code you did not write, including older codebases with limited documentation.
- Track record of working effectively in a fast-paced environment with shifting priorities — comfortable being pulled into an escalation and comfortable putting work down and picking it back up.
- Clear written communication. You can explain a design decision to a stakeholder who is not an engineer, and you can give a useful status update while an incident is still open.
Preferred Qualifications:
- 7+ years total experience, with time in a regulated environment — PCI DSS, financial services, healthcare, or legal.
- Experience with database migration tooling (Flyway, DbUp, SSDT/DACPAC) and treating schema as version-controlled code.
- Azure experience: App Service, Functions, Key Vault, Application Insights, API Management, Entra ID / Microsoft Identity platform, Microsoft Graph.
- Identity and access: IdentityServer / Duende, OAuth 2.0, OIDC, JWT bearer tokens.
- EDI or fixed-width/flat-file interchange experience with large trading partners.
- Managed file transfer experience — GoAnywhere MFT, SFTP automation, PGP.
- Document/PDF processing at scale (Aspose, iText, QuestPDF) or OCR pipelines.
- Browser/robotic process automation in .NET (PuppeteerSharp, Playwright, Selenium).
- Legacy modernization: migrating .NET Framework or .NET Core 3.1 workloads forward.
- SSRS, Power BI, or reporting-layer database design.
- Experience mentoring, leading a small team, or owning an architectural domain.
Our Environment:
Area | What we use |
Languages / Runtime | C#, T-SQL, PowerShell; .NET 8 / 9 (some .NET 10, legacy 3.1 and Framework) |
APIs | ASP.NET Core Web API, OpenAPI/Swashbuckle, Azure API Management |
Data | SQL Server, Entity Framework Core, Dapper, Flyway migrations |
Background work | Windows / worker services, Quartz, Azure Functions + Durable Task |
Identity | IdentityServer, Microsoft Entra ID, JWT bearer, Microsoft Graph |
Observability | Serilog, Azure Application Insights |
Testing | xUnit, MSTest, NUnit, Moq, FluentAssertions, coverlet |
DevOps | Azure DevOps Repos + Pipelines, CodeQL SAST, dependency and secret scanning |
Integration | GoAnywhere MFT, SFTP (SSH.NET), PGP, EDI with major card issuers |
Documents | Aspose PDF/Words, QuestPDF, ClosedXML, Tesseract / IronOCR |
How we work: feature/bug/release/hotfix branching tied to work items, mandatory peer review (no self-approvals), automated SAST on every build, stakeholder-approved UAT, and release-manager approval for production. Developers do not deploy to production alone, and they do not run ad hoc changes against production databases.
The position is primarily an in Office.
Schedule:
Standard business hours, Monday Through Friday with occasional evening and weekends for maintenance updates.
Physical Requirements:
- Prolonged periods of sitting at a desk and working on a computer.
- Frequently required to talk or hear, and use hand to type, handle, or touch objects.
- Regularly required to stand and walk, and may be required to stoop, bend, or reach above the shoulders.
- Must be able to occasionally lift up to 25 pounds at times.
- Must be able to access and navigate each department at the organization’s facilities
Tired of cold applications?
Sign up with Clera and we'll reach out the moment a role actually fits you — no more spraying applications into the void.
Know someone who'd be great for this?