Senior Backend / Cloud Engineer (Azure & DevOps Focus)

Key Responsibilities:

• End-to-End Product Engineering: Own the entire lifecycle of backend services and APIs—from initial architecture design and coding to comprehensive testing and production deployment.

• Event-Driven Ecosystems: Architect and maintain highly scalable, asynchronous solutions on Microsoft Azure, utilizing Azure Service Bus or Kafka for robust messaging.

• Infrastructure as Code (IaC): Orchestrate and manage cloud environments using Terraform, ensuring all infrastructure aligns with enterprise security and performance benchmarks.

• Container Orchestration: Deploy and fine-tune containerized workloads within Azure Kubernetes Service (AKS) environments.

• DevOps Ownership: Drive the automation of build, test, and release cycles, taking full accountability for the CI/CD pipelines of your assigned services.

• Data Persistence & Management: Design efficient data storage strategies (SQL, Cosmos DB, Storage) and expose secure, high-performance interfaces through Azure API Management (APIM).

• Strategic Collaboration: Partner with architects and platform teams to monitor system health via App Insights/Log Analytics, ensuring continuous reliability and optimization.

Required Skills & Experience:

• Technical Mastery: Extensive professional experience in backend development using C# and the .NET ecosystem.

• Cloud Expertise: Deep practical knowledge of Microsoft Azure core services, specifically AKS, APIM, and distributed messaging platforms.

• Architectural Literacy: Proven ability to work with Microservices and distributed systems, including sophisticated data modeling in both relational and NoSQL databases.

• DevOps Mindset: Hands-on proficiency with CI/CD automation tools and a strong commitment to Infrastructure as Code (Terraform).

• Agile Adaptability: Experience thriving in fast-paced, iterative delivery teams with a focus on solving complex technical challenges.

• Impactful Communication: Ability to articulate technical concepts clearly to both technical and non-technical stakeholders while adhering to best practices in documentation.