Careers

Senior .NET Backend Developer

  1. • Hybrid
  2. • New Cairo, Egypt

Posted 94 days ago

Job Description

Lead the design and delivery of scalable, secure backend services using .NET, applying Clean Architecture/CQRS, and enforcing code quality, performance, and reliability.

Responsibilities

·       Design and implement RESTful and real-time APIs (SignalR).

·       Apply Clean Architecture and CQRS for clear domain boundaries and maintainability.

·       Implement validation, background jobs, notifications, caching, and observability.

·       Ensure security-by-design, performance, and reliability (SLA/SLO).

·       Own CI/CD pipelines and production deployments (IIS/Azure).

·       Mentor engineers; write and review technical designs and RFCs.

Requirements

Core Skills

·       NET & APIs: .NET 6/7/8, ASP.NET Core Web API, middleware, filters, configuration.

·       Data & Persistence: SQL (SQL Server) and NoSQL (e.g., MongoDB/DocumentDB); EF Core (LINQ, migrations, performance), query tuning, repository/unit-of-work.

·       IoC/DI: Autofac (modules, lifetimes, scopes).

·       Validation & Jobs: FluentValidation; Hangfire (recurring jobs, retries, dashboards).

·       Real-Time & Notifications: SignalR (scale-out/backplanes), FCM integration.

·       Architecture & Design: Clean Architecture, CQRS; strong command of design patterns, SOLID, system design (scalability, resilience, fault tolerance).

·       Security: OAuth2/OIDC, JWT, RBAC/claims, secrets management, OWASP ASVS practices.

·       API Quality: OpenAPI/Swagger, versioning, pagination, idempotency, robust error handling.

·       Testing: xUnit/NUnit, integration tests; Postman/REST Client; basic load/perf testing.

·       Observability: Serilog (structured logging), health checks, OpenTelemetry (traces/metrics).

·       Deployments: IIS administration; Azure App Service/VMs; environment configuration.

·       Cloud Basics: Storage, messaging, networking fundamentals and cost/perf trade-offs.

·       Agile, DevOps & Compliance: Agile/Scrum, Azure DevOps (boards, work items, dashboards.

·       Version Control & Automation: GitHub (Repos, Projects/Issues, PRs, CODEOWNERS, protected branches), branching strategy (e.g. GitFlow), required checks & reviews, GitHub Actions for CI/CD (build/test/security scans, Docker image build/publish, deploy to IIS/Azure), environments/secrets, semantic versioning and automated releases.

 

Advantages Skills

·       Microservices: API gateway, service discovery, saga/outbox patterns.

·       Messaging/Caching: RabbitMQ/Kafka, Redis.

·       Containers/Orchestration: Docker; Kubernetes (Helm, probes, HPA).

·       Integration with different cloud services.

·       DDD, event sourcing, gRPC, feature flags.

·       Advanced performance profiling and GC tuning.

 

Experience

·       3-5+ years professional back-end experience.

·       Proven delivery of high-throughput, production systems.

·       Bachelor’s degree in CS/CE or equivalent experience.

·       Excellent communication, documentation, and mentoring skills.

 

AI Tools & Recommendations

Required/Supported Tools:

·       GitHub Copilot / Copilot Chat (primary) for C#/.NET code generation, refactoring, and test scaffolding.

·       ChatGPT (or equivalent) for system design reviews, API contract drafting (OpenAPI), threat modeling checklists, and migration playbooks.

·       Optional: Amazon CodeWhisperer/Codeium for additional completion coverage if needed.

 

Documentation (Required)

What to document

·       Overview: what the feature/service does and why it exists.

·       Interfaces: APIs or UI contracts (inputs, outputs, errors).

·       Data: key models/fields and any persistence notes.

·       Security & Privacy: auth, sensitive data handling, known risks.

·       Run & Deploy: how to run locally, how to deploy, basic troubleshooting.

·       Testing: what’s covered (unit/integration/E2E) and how to run tests.

·       Change Log: what changed in this version and any migration notes.

·       Ownership: main contacts and links to related work items.

Where to keep it

·       In-repo README and a short /docs note per feature; update Storybook for UI components when applicable.

Quality gates

·       Before merge: docs updated and linked to the work item.

·       PR checklist: “Docs updated?” must be checked.

·       Release: add/update release notes and link to PRs/issues.

All the above requirements and responsibilities are crucial for you to be able to take on in this role. We are looking for someone who has the energy and passion to bring together new ideas.


© Copyright by Digital Hub – All right reserved.