Snr/Mid Level .Net Developer

MID-LEVEL (~3–5 yrs) Productive across the stack with guidance. Ships features, follows existing patterns, writes tests.

• C#/.NET: Solid C# on .NET Framework; comfortable with async/await; avoids blocking calls
• Web/API: Builds ASP.NET Web API endpoints; uses DI; basic auth (Identity/OWIN)
• SQL Server: Writes/edits stored procedures + solid T-SQL; reads execution plans; understands transactions
• Cosmos/Redis: Uses existing repos correctly; basic partition-key + cache-aside understanding
• Messaging: Writes Service Bus / Storage Queue producers + consumers; handles retries; basic idempotency
• Azure: Deploys to App Service + Functions; uses Key Vault + App Insights
• Integration: Consumes REST/SOAP-WCF services with timeouts and retries
• Architecture: Understands and follows existing layered architecture
• Logging: Adds structured logs with correlation IDs + correct levels
• Practices: Git workflows; writes unit/integration tests; secure-coding basics

SENIOR-LEVEL (~6+ yrs) Owns design + tradeoff decisions, leads reliability/architecture/observability, modernizes legacy code, mentors. Minimal supervision. (Everything above, plus:)

• C#/.NET: Designs concurrency strategy; diagnoses deadlocks, memory leaks, GC issues; sets standards
• Web/API: Owns API contracts, versioning, backward compatibility
• SQL Server: Owns schema/index design; tunes production perf; designs concurrency-safe + idempotent data flows
• Cosmos/Redis: Decides what goes in SQL vs Cosmos vs Redis; designs partition + consistency + caching strategy
• Messaging: Picks the right tech per use case; designs idempotent, ordered, scalable processing; dead-lettering
• Azure: Owns cloud architecture — scaling, managed identity, cost, multi-tenant config; leads Durable Functions design
• Integration: Designs resilient boundaries — retry/backoff, circuit breaker, bulkhead, backpressure
• Architecture: Makes architectural calls (CQRS/Outbox, Saga, event-driven); solves dual-write + race conditions; leads legacy modernization without halting delivery
• Observability: Defines metrics/tracing/alerting + SLI/SLO; leads incident diagnosis + post-mortems
• Others: Sets testing/quality bar; drives code-review standards