Senior Azure or .NET Application Engineer
Senior Azure or .NET Application Engineer
Posted today
SENIORITY
Lead
About the role
- Propose technical solutions.
- Delivery of well-designed, high-quality, fully functional, properly tested features, fixes, and enhancements.
- Responsible for the full application development lifecycle and support.
- Use your strong understanding of Continuous Delivery and Integration frameworks including deployment automation, configuration management, test, and source code/git repositories to help the team deliver
- Help troubleshoot and support our store partners with operational issues and update/correct/create knowledge base articles.
- Troubleshooting and debugging to optimize performance.
- Provide subject matter expertise and direction, guidance, and support on complex engagements.
- 7+ years of software engineering
- 5+ years of Microsoft. NET Core, C#, ASP.NET MVC experience
- 5+ years of cloud computing, preferably Azure, including Containerization, Service Bus, Event Grid, Event Hub, Virtual Networks, Load Balancers, Traffic Manager, and Application Gateway for networks
- 4+ years of SQL Server including database design, query optimization, and stored procedures
- 3+ years of API development, including RESTful services and third-party integrations
- 3+ years of Azure DevOps or other CI/CD tools to manage deployments, Git principals, release planning, branch management, GitHub Actions
- 2+ years of Azure EntraID formerly Azure Active Directory (AAD) for identity and access management
- Knowledge of application monitoring tools such as Application Insights, Datadog, Splunk, and New Relic Knowledge of Apigee
- Hands-on experience with Azure App Services, Blob Storage, Queues, Event Hubs, Key Vault, and Application Insights.
- Expertise in designing and implementing Azure Service Bus solutions for various messaging scenarios, including point-to-point (queues) and publish-subscribe (topics) patterns.
- Experience in designing and implementing infrastructure as code using Terraform, Ansible, etc.
- Experience in automating infrastructure provisioning and deployments using ARM, templates, Terraform, or Bicep.
- Knowledge of Infrastructure as Code (IaC) practices. Experience with moving workloads from IaaS (e.g., Virtual Machines, legacy applications) to PaaS services (e.g., Azure App Service, Azure SQL Database, Azure Functions).
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
