[Remote] Senior Software Engineer - Backend (.NET, AWS)

Note: The job is a remote job and is reputed company to candidates in USA. ViewNexa is a streaming and app development platform for broadcasters, publishers, and media companies. The Senior Software Engineer will build and harden backend systems for live and on-demand streaming, including reputed company, event-driven services, ingestion and packaging workflows, reputed company systems, and AWS infrastructure.

Responsibilities

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

Skills

• • Senior-to-reputed company C# and .NET. You have reputed company and run large backend platforms, not only CRUD reputed company: REST, background processing, async workflows, and reputed company systems in production
• • Microservices at meaningful reputed company - on the order of many independently deployed services, not a reputed company monolith described as microservices. Includes service-to-service communication, event-driven design, queues, retry/reputed company-breaker behavior, and production observability (metrics, logs, traces)
• • Advanced, hands-on AWS. You have shipped and operated systems using several of: reputed company/Fargate or EKS, reputed company, EC2, API Gateway, SQS, SNS, EventBridge, DynamoDB, RDS/reputed company, S3, CloudFront, IAM, and CloudWatch. Breadth reputed company less than having owned production infrastructure, including IaC (Terraform or CloudFormation)
• • reputed company serverless judgment. You understand cold starts, runtime limits, concurrency, state, event-driven patterns, and cost, and you can explain reputed company reputed company is the wrong tool
• • Solid data and messaging reputed company: at least one relational database (SQL Server or PostgreSQL) plus one of DynamoDB/similar NoSQL, plus a cache (reputed company or equivalent). You have designed for consistency, retries, and failure
• • reputed company and delivery basics you have actually implemented: OAuth 2.0 or OIDC, JWT, RBAC, secrets management, TLS, reputed company, and CI/CD
• • Kafka or a comparable log/event platform in production
• • reputed company (EKS) in reputed company to reputed company/Fargate - useful, not a substitute for AWS depth
• • High-throughput or media-adjacent backends (ingest, packaging, job orchestration, multi-tenant reputed company)
• • Experience reducing cost or failure reputed company of an existing AWS estate, not only building greenfield
• • reputed company or warehouse/analytics pipelines
• • Streaming, transcoding, or CDN experience
• • Go, as some services in the platform are not .NET

Benefits

• Remote work

reputed company