Role: React/.Net C# Developer
Location: Boise, ID (ONSITE)
Interview type: In Person
Required: overall 12+ years of experience required.
It''''''''s built on a standard, modern .NET stack, using C# with ASP.NET Core (.NET 6/8) for backend REST and SOAP APIs, with AWS services such as Lambda for serverless processing. The frontend leverages React and Javascript/TypeScript.
React & Javascript
4+ years React: Building modern, component-based UIs (as indicated by the need for Node/NPM in the README).
4+ years JavaScript/TypeScript: Writing maintainable, modular code for the fronten
C# / .NET
4+ years Strong proficiency in C# and the .NET 6/8 ecosystem
4+ years’ Experience with ASP.NET Core for building RESTful APIs
2+ years Familiarity with dependency injection
2+ years Understanding of asynchronous programming using async/await
API Integration
4+ years Ability to implement and consume REST APIs (using controllers, attributes, and model validation)
Nice-to-have Any experience with SOAP APIs: constructing and parsing XML, using HttpClient, and working with XmlSerializer is nice to have
Testing
2+ years Writing and maintaining unit and integration tests using NUnit.
2+ years Using RestSharp for HTTP-based integration tests
4+ years Serializing/deserializing JSON with System.Text.Json and Newtonsoft.Json.
Cloud & Serverless
3+ years’ Experience with AWS Lambda (C#): writing handler functions, deploying with Amazon.Lambda.Tools, and using AWS SDKs (e.g., Secrets Manager, SES)
3+ years Understanding of serverless application patterns
Nice-to-have Any OpenSearch experience would be highly prized
Containerization & Local Development
2+ years Building and running services with Docker and Docker Compose
DevOps & Tooling
4+ years Git: Source control and branching strategies
Nice-to-have CI/CD: Familiarity with pipelines for automated builds, tests, and deployments
Nice-to-have Postman/Yakk: used for manual API testing and exploration
4+ years Visual Studio: our primary IDE for development and debugging
Security
2+ years Security best practices for AWS: IAM least privilege, secure secrets handling with AWS Secrets Manager, and protecting data in transit and at rest
Nice-to-have Application security: familiarity with OWASP Top 10, API authentication/authorization, and secure code review or remediation practices.