Senior BackEnd Engineer + Azure DevOps
What you will be doing
• Modernization: Lead the upgrade of C# codebases from older versions (e.g., .NET Core 3.1) to modern standards (.NET 8+).
• DevOps & Infrastructure: Improve and maintain build pipelines (Azure DevOps, Bitbucket). Manage Azure resources using Terraform or Bicep.
• Cloud Maintenance: Proactively handle cloud deprecations and ensure our Azure footprint is optimized and secure.
• Security & Compliance: Implement and maintain security best practices and ensure adherence to compliance standards.
• Observability & Support: Ensure systems are observable and supportable, leveraging tools like Application Insights.
• Core Development: Fix bugs and develop features for core backend services. Manage database schema changes via migrations (Entity Framework).
• Legacy Support: Maintain and refactor legacy applications while planning their modernization.
• Collaboration: Participate in team code reviews and contribute to architectural discussions. You often think about non functional requirements and if they are being achieved.
• Autonomy: Prioritize, plan, and execute your own work streams effectively.
• Support: participate in on-call rotation for critical systems. (every 4 weeks).
• DevOps & Infrastructure: Improve and maintain build pipelines (Azure DevOps, Bitbucket). Manage Azure resources using Terraform or Bicep.
• Cloud Maintenance: Proactively handle cloud deprecations and ensure our Azure footprint is optimized and secure.
• Security & Compliance: Implement and maintain security best practices and ensure adherence to compliance standards.
• Observability & Support: Ensure systems are observable and supportable, leveraging tools like Application Insights.
• Core Development: Fix bugs and develop features for core backend services. Manage database schema changes via migrations (Entity Framework).
• Legacy Support: Maintain and refactor legacy applications while planning their modernization.
• Collaboration: Participate in team code reviews and contribute to architectural discussions. You often think about non functional requirements and if they are being achieved.
• Autonomy: Prioritize, plan, and execute your own work streams effectively.
• Support: participate in on-call rotation for critical systems. (every 4 weeks).