Job Title:
Mid-Level .NET Developer (Backend / Distributed Systems)
Overview
We are seeking a mid-level .NET Developer to join a backend-focused engineering team building and enhancing distributed services in AWS. This role is heavily backend and API-driven, with a strong emphasis on asynchronous processing, system-to-system integration, and resilient service design. The engineer will work on both net-new services and enhancements to existing systems, collaborating closely with product owners and other engineering teams.
Key Responsibilities
- Design, build, and enhance backend services using .NET and C#
- Develop RESTful APIs and backend components that operate within distributed systems
- Build and maintain asynchronous processing workflows using messaging patterns
- Upgrade and modernize existing .NET applications (e.G. .NET 8 to .NET 10)
- Implement system-to-system integrations, including external-facing services
- Consume and process messages from event-driven sources, handling retries and failure scenarios
- Participate in unit and integration testing as part of CI/CD pipelines
- Deploy services to Kubernetes environments in AWS
- Collaborate with product owners, engineers, and cross-functional teams in a ticket-driven environment
- Contribute to design discussions with a system-wide, not just code-level, mindset
Technical Requirements
- Strong proficiency with C# and modern .NET development
- Experience building backend services and RESTful APIs
- Solid understanding of distributed systems and asynchronous processing
- Hands-on experience with event-driven architectures (pub/sub, messaging systems)
- Experience working in AWS environments
- Familiarity with Kubernetes-based deployments (e.G. EKS)
- Experience using relational databases (e.G. AWS RDS)
- Exposure to CI/CD pipelines, preferably GitHub Actions
- Experience with unit testing and integration testing in .NET applications
Preferred / Nice to Have
- Experience with AWS messaging services such as SNS and SQS
- Familiarity with Infrastructure as Code tools such as Terraform
- Experience deploying applications via GitHub Actions
- Exposure to configuration management patterns (e.G. externalized config services)
- Experience working alongside teams using different technology stacks (e.G. Clojure or functional programming environments)
- Familiarity with authentication and service-to-service security (e.G. Okta)
- Comfort using AI-assisted development tools such as GitHub Copilot
Work Environment & Team Culture
- Backend-heavy role with minimal frontend expectations
- Collaborative, low-micromanagement engineering culture
- Engineers are expected to work independently but ask questions when needed
- Ticket-driven work with varying levels of requirement detail
- Strong emphasis on respectful cross-team collaboration
- Encouragement of thoughtful technical pushback and design discussions
- Regular pairing and open communication via Slack and ad-hoc calls
- Focus on sustainable delivery rather than perfection under time constraints
What Success Looks Like
- Quickly ramping into existing systems and development patterns
- Owning backend services end to end, from design through deployment
- Demonstrating a strong systems mindset beyond individual features
- Building reliable, maintainable services within a distributed architecture
- Collaborating effectively across teams with different technical bac