Senior.NET Software Engineer

About the role

The team delivers secure identity and authorization management for a multi-tenant platform. The position reports directly to the Engineering Manager.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

The SQL Server data layer is architected and maintained to support identity security operations.

Consistent, automated deployments are enabled through contributions to CI/CD pipelines in Azure DevOps.

Engineering peers are mentored to foster continuous improvement and technical excellence in authorization and identity lifecycle management.

Requirements

A Bachelor's or Master's degree in Computer Science, Software Engineering, or a related technical discipline is required.

Professional software engineering experience over 5 years with a strong focus on .NET (C#), including .NET Framework, is essential; exposure to modern .NET is a plus as some smaller services run on newer versions.

Designing and building RESTful APIs and back-end services in production environments for identity and security platforms is required.

SQL Server skills must include writing and optimizing queries and stored procedures for high-throughput security data.

Hands-on experience with Microsoft Azure, including App Services and Azure-native services for hosting and scaling secure services, is required.

A solid understanding of multi-tenant SaaS and web application architecture and the trade-offs of operating at scale for global identity systems is required.

Problem-solving, communication, and collaboration skills must enable thriving in an Agile team environment focused on security delivery.

Nice to have

Occasional full-stack contributions are supported by front-end experience with AngularJS for identity management interfaces.

Background or asynchronous processing using Azure WebJobs or Azure Functions is expected for secure async operations.

Integration with third-party ERP and SaaS systems such as SAP, Oracle, Microsoft Dynamics, Salesforce, and NetSuite is preferred.

AI-driven development practices, including the use of AI coding agents like Claude, Codex, or Cursor, is valued to accelerate development workflows.

CI/CD in Azure DevOps and pipeline-based deployments for identity platforms is preferred.

Structured logging and application monitoring using tools such as Serilog and Application Insights is valued for security observability.

Practical notes

The position is fully remote within the U.S. Remote framework, with standard expectations for collaboration across time zones and on-call responsibilities for production services. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.