Senior Software Engineer – Backend (.NET, AWS) – Remote

Calance; United States; Remote; USD 140,000 - 190,000; Full time

Job summary

Calance is seeking a Senior to Principal Backend Architect to lead the design and operation of large-scale .NET services on AWS. You will shape a distributed backend with REST APIs, asynchronous processing, and robust service boundaries.

Expect to decide between serverless and containers, optimize for latency, cost, and reliability, and raise observability across multiple services. You will own security by design, implement OAuth/OIDC, JWT, and RBAC, and guide IaC practices.

Qualifications

• Senior-to-Principal C#/.NET experience in large backend platforms.
• Production systems with distributed design and service boundaries.
• Hands-on AWS with deep depth in ECS/Fargate, EKS, Lambda, API Gateway, DynamoDB, RDS/Aurora, S3.

Responsibilities

• Design and ship C#/.NET services: REST APIs, background workers, async processing.
• Evolve a microservice architecture with messaging, retries, circuit breakers, idempotency.
• Build on AWS with various services and appropriate compute models.

Skills

C#/.NET

AWS

Microservices

Distributed systems

REST APIs

Serverless vs containers

Observability

Security

Tools

Terraform/CloudFormation

Docker

Kubernetes

SQS/SNS/EventBridge

DynamoDB

RDS/Aurora

S3

CloudWatch

Job description

The Role

You will build and harden the backend that runs ViewNexa: APIs, event-driven services, ingestion and packaging workflows, and the distributed systems behind live and on-demand streaming.

We need someone who has already operated a large .NET estate on AWS – dozens of services, real failure modes, and opinions about serverless vs. containers that come from production, not from a conference talk.

Principal candidates should have led architecture for a substantial backend domain, not only implemented tickets inside one.

What You Will Do

Design and ship C#/.NET services: REST APIs, background workers, async processing, and service-to-service communication.
Evolve a microservice architecture: messaging, retries, circuit breakers, idempotency, and clear service boundaries.
Build on AWS with intent – ECS/Fargate or EKS, Lambda, API Gateway, SQS/SNS/EventBridge, DynamoDB, RDS/Aurora, S3, CloudFront, IAM, CloudWatch – and choose the right compute model for the workload.
Make serverless vs. container decisions explicitly: cold starts, timeouts, concurrency, state, cost, and when a long-running service is the honest answer.
Raise the operational bar: distributed tracing, alerting, service level objectives, and the ability to debug a failure across multiple services.
Treat security as part of the design: OAuth 2.0/OIDC, JWT, RBAC, IAM, secrets, TLS/mTLS.

Required Experience

Senior-to-Principal C# and .NET. You have built and run large backend platforms, not only CRUD APIs: REST, background processing, async workflows, and distributed systems in production.
Microservices at meaningful scale – on the order of many independently deployed services, not a modular monolith described as microservices. Includes service-to-service communication, event-driven design, queues, retry/circuit-breaker behavior, and production observability (metrics, logs, traces).
Advanced, hands-on AWS. You have shipped and operated systems using several of: ECS/Fargate or EKS, Lambda, EC2, API Gateway, SQS, SNS, EventBridge, DynamoDB, RDS/Aurora, S3, CloudFront, IAM, and CloudWatch. Breadth matters less than having owned production infrastructure, including IaC (Terraform or CloudFormation).
Proven serverless judgment. You understand cold starts, runtime limits, concurrency, state, event-driven patterns, and cost, and you can explain when Lambda is the wrong tool.
Solid data and messaging foundation: at least one relational database (SQL Server or PostgreSQL) plus one of DynamoDB/similar NoSQL, plus a cache (Redis or equivalent). You have designed for consistency, retries, and failure.
Security and delivery basics you have actually implemented: OAuth 2.0 or OIDC, JWT, RBAC, secrets management, TLS, Docker, and CI/CD

Strongly Preferred

Kafka or a comparable log/event platform in production.
Kubernetes (EKS) in addition to ECS/Fargate – useful, not a substitute for AWS depth.
High-throughput or media-adjacent backends (ingest, packaging, job orchestration, multi-tenant SaaS).
Experience reducing cost or failure rate of an existing AWS estate, not only building greenfield.

Nice To Have

Snowflake or warehouse/analytics pipelines.
Streaming, transcoding, or CDN experience.
Go, as some services in the platform are not .NET.

This role IS a fit if…

You can walk through a production incident that spanned multiple services and queues, and you can defend a Lambda vs. Fargate choice with latency, cost, and failure-mode numbers.

This role IS NOT a fit if…

Your AWS experience is limited to S3 + a single EC2 box, or your .NET work has been primarily MVC websites without distributed backend ownership.