> Markdown version of [/jobs/ext/3876439-software-engineer](https://www.wearedevelopers.com/jobs/ext/3876439-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Software Engineer

- **Company:** NST MARKETING GROUP LLC
- **Location:** Denmark, SC, United States
- **Experience:** Experienced
- **Salary:** $132,974 - $166,217
- **Contract:** Permanent contract
- **Skills:** Java (Programming Language), .NET Framework, Artificial Intelligence, Amazon Web Services, Microsoft Azure, C Sharp (Programming Language), Cloud Computing, Continuous Integration, Cross-Site Request Forgery, Federal Information Processing Standards (FIPS), Identity and Access Management, Key Management, OAuth, Open Source Technology, Openid Connect, Security Assertion Markup Language (SAML), Software Engineering, Systems Integration, Okta, Backend, Model Context Protocol
- **Published:** October 22, 2026
- **Apply:** https://jobs.military.com/career/372005/principal-software-engineer-washington-wa-bellevue

## About the Role

* Engineering depth: 6+ years of professional software engineering, with at least 3 years building or running authentication, authorization, or identity systems in production.\n
 * Backend stack: Strong backend skills in C#/.NET or Java, and a willingness to work in whichever one a given service uses.\n
 * Protocol expertise: Deep, practical knowledge of OAuth 2.0/2.1, OpenID Connect, and SAML 2.0: grant types, token formats JWT, PKCE, token lifetimes and revocation, and assertion signing and encryption.\n
 * IdP experience: Hands-on experience with at least one IdP, whether in-house, open source (such as Keycloak), or commercial (such as FusionAuth, Auth0, Okta, Entra ID, or Cognito), including integrating customer IdPs for enterprise SSO.\n
 * Authorization design: Experience designing authorization models and permission services that stay correct and fast at scale.\n
 * Security mindset: A solid grasp of identity threats (token theft and replay, session fixation, CSRF, open redirects, IdP-initiated SSO risks) and how to design against them.\n
 * Cloud-native systems: Experience building distributed services on AWS or Azure, including containers, CI/CD, and production observability.\n
 * AI-native delivery: You use AI tools every day to understand code, generate tests, and ship faster.\n
 * Clear communication: You can explain a tricky identity trade-off to engineers, product managers, and auditors.\n, * Experience with FedRAMP, or other government compliance programs, and with NIST SP 800-63 identity and federation assurance levels.\n
 * Experience with FIPS 140-validated crypto modules, HSM or KMS-backed key management, and certificate lifecycle automation.\n
 * Experience with policy engines or fine-grained authorization systems such as OPA, Cedar, OpenFGA, or other Zanzibar-style systems.\n
 * Familiarity with the Model Context Protocol (MCP) authorization spec, OAuth token exchange, or workload identity (CIMD, IAM roles for service accounts).\n
 * Experience with SCIM 2.0.\n
 * Experience leading a migration between identity platforms without disrupting customers.\n