CaseGuard
Software Engineer - Backend
About this role
Join CaseGuard as a Backend Software Engineer to design and build scalable REST API microservices using ASP.NET Core and AWS infrastructure. You'll work on a collaborative file redaction platform with features like live editing and image processing, handling complex backend challenges independently.
What you'll do
- Design and build scalable REST APIs using ASP.NET Core (C#) for microservices
- Model business domains into relational and NoSQL data structures
- Build file-processing workers optimized for CPU, memory, and throughput
- Design AWS infrastructure using Infrastructure as Code
- Participate in architectural discussions and contribute to system design decisions
- Work independently on complex, underspecified backend problems
What they're looking for
- ASP.NET Core and C#
- REST API design and development
- Relational databases and SQL (schema design, indexing, transactions)
- Redis or distributed caching
- Object-oriented programming and system design
- AWS services (EC2, S3, Lambda, RDS, DynamoDB)
- Infrastructure as Code (AWS CDK, Terraform, CloudFormation)
- File processing and handling large binary data
Benefits
- Competitive salary
- Stock options
- Medical, dental, and vision insurance
- 401(k) retirement plan
- Paid vacation and ten paid holidays annually
- Friendly and learning-focused environment
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
CaseGuard
CaseGuard builds a C# WPF-based redaction platform with computer vision and machine learning capabilities for law enforcement and federal agencies. The company is hiring Software Engineers in Test, Machine Learning Engineers, and DevOps Engineers to strengthen its quality assurance, AI model development, and cloud infrastructure teams.
View all jobs at CaseGuardLikely interview questions
- Walk us through your experience designing and building REST APIs at scale—what challenges did you face and how did you solve them?
- Describe a complex backend system you've architected. How did you approach modeling the business domain into your database schema?