Dotnet Developer

Role - .Net Developer

Location – Berkeley Heights, NJ – Onsite

W2 Contract position

Long Term Position

Core expectations

1. Own technical strategy and architecture for migrating .NET Framework monoliths to .NET Core/.NET (6 ), microservices, or containerized platforms.
2. Design and implement active‑active, highly available application architectures across regions/availability zones, with proven hands‑on experience in multi‑region deployments, automated failover, and conflict resolution strategies.
3. Deliver migration plans that balance risk, cost, and timelines: assessment, prioritization, proofs of concept (POCs), cutover strategy and rollback plans.
4. Lead hands‑on implementation: refactor code, remove platform‑specific dependencies (WebForms, .asmx), implement APIs, containerize apps, and automate deployments.
5. Design and implement cloud‑native architectures on Azure (App Services, AKS, Functions, Storage, Key Vault) and/or OpenShift (on‑prem or managed), including networking, security, and scaling for active‑active operation.
6. Build CI/CD pipelines (GitHub Actions, Jenkins) and infrastructure as code (ARM/Bicep, Terraform, OpenShift templates).
7. Establish observability (logging, metrics, tracing), performance baselines, chaos‑testing and production runbooks to validate active‑active behavior.
8. Coach and lead engineering teams through architecture, code reviews, runbooks and operational readiness.
9. Communicate clearly with product owners, stakeholders and operations to align migration risks, timelines and acceptance criteria.

Scope and typical responsibilities

1. Perform technical discovery and legacy‑code analysis across applications, libraries and integrations.
2. Produce migration artifacts: target architecture diagrams (including active‑active topology), migration backlog, component decomposition, POC results, and cutover/rollback plans.
3. Execute migration sprints: code changes, container builds, configuration management, infra provisioning, testing, and blue/green or canary cutovers.
4. Define security, compliance and governance for cloud and container deployments.
5. Implement data replication and synchronization strategies needed for active‑active deployments.
6. Mentor 3–10 engineers and serve as technical escalation point.
7. Collaborate with QA, SRE/DevOps, product and enterprise architecture teams.

Required skills and competencies

1. Deep .NET expertise: 8 years developing in .NET and .NET Framework; 3 years migrating/architecting to .NET Core / .NET 6 .
2. Proven hands‑on experience migrating legacy .NET apps (WebForms, Windows Services, older libs) to modern .NET or microservices.
3. Strong architecture experience: system decomposition, APIs, event‑driven patterns, messaging, data migration strategies, and integration patterns.
4. Cloud experience: substantial experience with Azure services and/or OpenShift/Kubernetes platforms, designed for active‑active operation.
5. Containerization and orchestration: Docker, Kubernetes (AKS/OpenShift), Helm, Operators and multi‑cluster management.
6. CI/CD and IaC: GitHub Actions, Jenkins; Terraform, Bicep/ARM or OpenShift templates.
7. Databases — hands‑on experience with relational and distributed SQL:
8. SQL Server: high availability, AlwaysOn Availability Groups, replication, transactional consistency and performance tuning.
9. Oracle: Data Guard, GoldenGate, replication strategies, and schema migration experience.
10. YugabyteDB (or similar distributed SQL DBs such as CockroachDB): hands‑on experience or demonstrated familiarity with distributed transactions, geo‑partitioning, and multi‑region read/write configurations.
11. Experience with schema evolution, data migrations, CDC (Change Data Capture) and ETL patterns for active‑active topologies.
12. Data consistency and replication: design for eventual and strong consistency tradeoffs, conflict detection/resolution, distributed transactions or compensation patterns.
13. Messaging & caching: experience with RabbitMQ, Kafka, Azure Service Bus, Redis and distributed cache patterns for multi‑region deployments.
14. Security and identity: OAuth2/OpenID Connect, Azure AD, secrets management, TLS and security best practices for cross‑region deployments.
15. Observability: Application Insights, Prometheus/Grafana, ELK, distributed tracing and operational runbooks.
16. Software engineering best practices: automated testing, TDD, modular design and backward compatibility strategies.
17. Leadership and communication: proven ability to lead engineers, facilitate technical decisions, present to stakeholders and write concise migration documentation.

Nice‑to‑have / differentiators

1. Microsoft Certified: Azure Solutions Architect or related certifications.
2. Kubernetes certifications (CKA/CKAD) or strong OpenShift operator experience.
3. Experience modernizing systems in regulated industries (financial services, healthcare).
4. Experience with multi‑master DB setups and multi‑region networking optimizations.