Overview

We are looking for a Senior Full-Stack Developer with deep hands-on expertise in .NET Core, Azure cloud services, and modern Angular front-end development. The role requires someone who can independently own complex backend modules end-to-end, contribute to distributed system and microservice design, and work fluently across the full stack — from Azure Functions and Web APIs on the backend to Angular components and RxJS-driven data flows on the front end. Familiarity with Ruby (or another scripting language) is also required to support automation, integration, and operational tasks.

You will work closely with backend engineers, front-end developers, DevOps, QA, and product stakeholders to deliver production-grade, cloud-native software with strong engineering practices.

Key Responsibilities

• Design, build, and maintain scalable backend services using .NET Core, C, and Web APIs
• Build and operate cloud-native solutions on Microsoft Azure — Azure Functions, App Services, Storage, and Key Vault
• Contribute to and evolve CI/CD pipelines in Azure DevOps using YAML-based configurations and Git-based workflows
• Develop responsive front-end features in Angular, leveraging components, services, and RxJS for reactive data flows
• Write clean, testable, and maintainable code aligned to SOLID principles and modern software engineering practices
• Author scripts and utilities in Ruby (or an equivalent scripting language) to automate integration, deployment, and operational workflows
• Contribute to the design of RESTful services, distributed systems, and microservice architectures
• Model, query, and tune data structures across Cosmos DB, other NoSQL stores, or SQL databases as appropriate to the workload
• Participate actively in code reviews, technical design discussions, and architectural decision-making
• Troubleshoot production issues, drive root-cause analysis, and implement long-term fixes
• Take ownership of features from design through deployment, with a focus on quality, performance, reliability, and security
• Collaborate with distributed cross-functional teams across the full software delivery lifecycle

Required Skills

• 5+ years of professional hands-on software development experience
• .NET Core & C — strong proficiency in modern .NET, async / await patterns, dependency injection, and idiomatic C
• Web API development
• Async programming
• Azure cloud platform, with hands-on experience across:
• Azure Functions (serverless compute)
• Azure DevOps — CI/CD, YAML pipelines, repositories
• App Services
• Azure Storage (Blob, Queue, Table as relevant)
• Key Vault (secrets and configuration management)
• Databases — working knowledge of Cosmos DB, another NoSQL store, or the SQL Server suite (T-SQL, indexing, query tuning)
• Angular front-end
• Ruby or Python or PowerShell or Bash
• DevOps
• Distributed systems — strong understanding of RESTful services, service boundaries, eventual consistency, and microservice design patterns

Good to Have

• Containerisation with Docker; orchestration with Kubernetes (AKS)
• Messaging platforms — Azure Service Bus, Event Grid, RabbitMQ, or Kafka
• API security — OAuth 2.0, JWT, OpenID Connect, API gateway patterns
• Testing frameworks — xUnit, NUnit, MSTest on the backend; Jasmine, Karma, or Jest on the front-end
• Infrastructure as Code — Terraform, Bicep, or ARM templates
• Observability — Application Insights, Log Analytics, Prometheus / Grafana
• Front-end tooling — Vite, Webpack, Nx workspaces
• Domain-Driven Design and Clean Architecture patterns
• Agile / Scrum delivery experience

Soft Skills

• Strong analytical thinking and structured problem-solving
• Ability to own complex modules independently from design to production
• Clear written and verbal communication, comfortable working with distributed teams and client stakeholders
• Willingness to mentor junior engineers and contribute to team-wide engineering standards
• Proactive attitude to code quality, technical debt, and continuous improvement

Screening Questions for Vendors

• In ASP.NET Core, why is using .Result or .Wait() on an async operation dangerous even though it doesn't necessarily cause a traditional deadlock?
• What is the difference between Task and ValueTask, and when would you actually use ValueTask?
• You need to limit calls to a downstream API to 4 concurrent requests. What .NET mechanism would you use?
• A client retries POST /orders after a timeout and accidentally creates two orders. How would you make the API idempotent?
• Two users update the same record at nearly the same time. How would you prevent one user's update from silently overwriting the other?
• When would you choose Azure Functions Consumption vs Premium/Dedicated, particularly when you have strict latency requirements or VNET access?
• A Service Bus message is delivered twice and the operation charges a customer. Is duplicate delivery necessarily a bug? How should the consumer handle it?
• How should an Azure application access Key Vault secrets without putting credentials/connection strings in configuration?
• Two Cosmos queries return one document each, but one costs 3 RUs and the other 480 RUs. What could cause that difference?
• A SQL query uses WHERE CONVERT(date, OrderDate) = ... and scans a huge table despite an index on OrderDate. Why?
• An Angular typeahead sends a request for every keystroke and old responses sometimes overwrite newer results. Which RxJS approach would you use?
• What does Angular OnPush change-detection strategy mean, and why can items.push(item) cause a UI not to update?
• In Azure DevOps, how would you design a pipeline so that you build an artifact once and promote that same artifact through Dev → QA → Production?
• Your SQL transaction commits but publishing the corresponding Service Bus event fails. How do you solve the dual-write problem?
• Tell me about a production incident you owned end-to-end. What was the root cause, and what?