← Back
Software Engineer II

Software Engineer II

Microsoft

Company

Microsoft

Location

Bangalore, Karnataka, India

Salary Range

₹22 LPA – ₹40 LPA

Work Mode

Hybrid

Who Can Apply

BE/BTechMCAME/MTechComputer Science GraduatesSoftware Engineers with 3+ years experience

Skills Required

C#JavaGoC++Distributed SystemsBackend DevelopmentAzureAWSGoogle Cloud Platform (GCP)REST APIsDockerKubernetesQueueing SystemsLoad BalancingScheduling SystemsHigh Throughput SystemsAsynchronous ProcessingMicroservicesMonitoringObservabilityTelemetryPerformance OptimizationData StructuresAlgorithmsGitSystem Design

Job Description

Microsoft is hiring a Software Engineer II for its Bangalore office. This opportunity is ideal for experienced backend software engineers who enjoy solving challenging distributed systems problems at massive scale. The selected candidate will become part of Microsoft's AI infrastructure engineering team responsible for building the backend systems that power large-scale Generative AI inference across Microsoft cloud services.

As a Software Engineer II, you will build highly scalable backend services responsible for processing millions of AI inference requests efficiently. Your work will directly impact how Microsoft's AI services allocate compute resources, schedule workloads, balance traffic, and deliver reliable AI experiences to enterprise customers worldwide.

You will work closely with engineers designing cloud-native distributed systems capable of handling asynchronous workloads while maintaining high availability, low latency, and optimal resource utilization. The role provides excellent exposure to hyperscale cloud infrastructure, intelligent scheduling systems, backend architecture, and production-grade service engineering.

Key Responsibilities

  • Design scalable backend services supporting AI inference workloads.
  • Develop intelligent scheduling systems for efficient compute utilization.
  • Build request routing systems for large-scale distributed infrastructure.
  • Optimize latency, throughput, and infrastructure cost.
  • Improve service reliability and availability.
  • Develop production-quality backend software.
  • Write clean, maintainable, and well-tested code.
  • Participate in architecture discussions.
  • Perform performance profiling and optimization.
  • Implement telemetry and monitoring solutions.
  • Build alerting systems for production services.
  • Participate in on-call engineering rotations.
  • Collaborate with AI platform teams.
  • Support deployment of new AI models.
  • Improve scalability of existing backend services.
  • Review pull requests and mentor fellow engineers.
  • Follow engineering best practices.
  • Ensure system security and compliance.
  • Contribute to continuous service improvements.

Required Qualifications

  • Bachelor's Degree in Computer Science or related field.
  • Minimum 3 years of software engineering experience.
  • 2+ years developing backend or distributed systems.
  • Experience with C#, Java, Go, or C++.
  • Cloud platform experience (Azure, AWS, or GCP).
  • Strong understanding of distributed system fundamentals.

Preferred Qualifications

  • Experience with distributed computing.
  • High throughput system design.
  • Queueing systems.
  • Load balancing.
  • Request routing.
  • Container technologies.
  • Docker.
  • Kubernetes.
  • Monitoring tools.
  • Production service operations.
  • System observability.

Why Join Microsoft?

  • Work on cutting-edge Generative AI infrastructure.
  • Solve engineering challenges at hyperscale.
  • Hybrid work flexibility.
  • Competitive salary.
  • Learning and career growth.
  • Global engineering collaboration.
  • Excellent work culture.
  • World-class engineering practices.
  • Exposure to Azure AI platform.
  • Opportunity to work with industry-leading engineers.

Expected Interview Questions

  1. Explain how load balancing works in distributed systems.
  2. What is the difference between synchronous and asynchronous processing?
  3. Explain microservices architecture.
  4. How does Docker differ from virtual machines?
  5. What is Kubernetes?
  6. Explain CAP theorem.
  7. How would you design a scalable backend service?
  8. What are message queues?
  9. Difference between horizontal and vertical scaling.
  10. Explain REST API principles.
  11. What is eventual consistency?
  12. How do distributed transactions work?
  13. Explain thread synchronization.
  14. What is latency vs throughput?
  15. Explain circuit breaker pattern.
  16. How would you optimize API performance?
  17. Explain caching strategies.
  18. Difference between SQL and NoSQL.
  19. Explain cloud scalability.
  20. What monitoring tools have you used?

Skills Explanation

Distributed Systems

Understanding how multiple servers communicate and coordinate while maintaining scalability and reliability.

Backend Development

Building APIs, business logic, databases, and cloud services that power applications.

Cloud Platforms

Deploying, scaling, and maintaining applications on Azure, AWS, or GCP.

Docker

Packaging applications into lightweight containers for consistent deployment.

Kubernetes

Managing containerized applications automatically at scale.

Scheduling Systems

Efficiently assigning workloads to available computing resources.

Queueing Systems

Managing asynchronous processing through reliable message queues.

Load Balancing

Distributing incoming requests across multiple servers.

Observability

Monitoring logs, metrics, and traces to maintain application health.

System Design

Designing scalable, maintainable, and fault-tolerant software systems.

Resume Tips For This Role

Highlight backend development projects.

Mention distributed systems experience.

Include cloud deployment projects.

Showcase Docker and Kubernetes knowledge.

Mention API development experience.

Demonstrate scalability improvements.

Include performance optimization work.

Highlight system design knowledge.

Mention monitoring or logging tools.

Add projects involving asynchronous processing.

Include GitHub repositories if available.

Quantify project impact wherever possible.

Last Date

2026-08-15