
Candidates describe Infosys cloud and platform interviews as hands-on technical conversations on AWS or Azure, covering Kubernetes, Terraform, CI/CD, networking and project walkthroughs, with managerial scenarios in at least one loop.
$93K
Avg. Base Comp
$110K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Across three candidate reports, Infosys cloud and platform interviews lean toward hands-on proof of tool use rather than definitions. The cloud provider varied: one candidate faced Azure, AKS, Terraform and Docker questions, another was pressed on EKS, and a third described an AWS and Python loop covering EC2, Lambda, Step Functions and API Gateway.
Kubernetes was the most repeated theme. The Azure candidate was asked for the steps they would take when a pod fails, how to check routing from inside a pod with exec, and how to set up Ingress. The EKS candidate was asked about cluster setup and operations from past projects. The Azure candidate said conceptual answers fell short where the interviewer wanted specific steps, and the EKS candidate likewise advised describing past projects in concrete terms.
Infrastructure as code came up in two of the three loops. Questions included Terraform implicit versus explicit dependencies, modules across multiple subscriptions, and provisioning EC2 with CloudFormation or Terraform. Expect CI/CD questions too, such as why Jenkins is used, Jenkins versus GitHub for deployment, and what to inspect first in a slow pipeline.
One candidate who accepted an offer described a managerial round built on scenarios: improving availability, securing Lambda and EC2, and choosing Lambda versus EC2. Their takeaway was to justify each service choice. Two of the three reports ended without an offer, so prepare to talk through real projects in specific detail.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Infosys process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Infosys
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Find the Missing Number | |
| Normalize Grades | |
| Find Duplicate Numbers in a List | |
| Swap Variables | |
| Hurdles In Data Projects | |
| Terraform Subscriptions | |
| Concurrent LLM Serving | |
| Check Matching Parentheses | |
| Client Solution Pushback | |
| The Longest Journey | |
| String Palindromes | |
| Cloud-Agnostic Deployments | |
| Safe Deployments | |
| Pipeline Transformation Failures | |
| Text Editor With OOP | |
| Scalable Data Pipelines | |
| Azure Kubernetes Infrastructure | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Singly Linked List | |
| Prime to N | |
| Find Bigrams | |
| String Shift | |
| Find the First Non-Repeating Character in a String | |
| Scrambled Tickets | |
| Get Top N Frequent Words | |
| Minimum Change | |
| Good Grades and Favorite Colors | |
| Payment Data Pipeline |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports being shortlisted by a third-party recruitment agency, which discussed the role and checked skills against Infosys's needs before arranging the interview. Other candidates did not describe a screen, so this step may not apply to every route into the process.
Candidates report technical questions on AWS or Azure services, Kubernetes (EKS or AKS), Terraform or CloudFormation, networking such as VNets and VPCs, and CI/CD. One interview lasted about 30 minutes. Interviewers appear to probe real project experience and want specific steps, not conceptual answers.
Some candidates were asked fundamentals alongside the cloud topics. One was asked about Python tuples versus lists, pandas error handling and object-oriented concepts. Another was asked what the numeric Linux file permission notation means. These likely depend on the interviewer and the team's stack.
One candidate who accepted an offer describes a managerial round of scenarios on availability, securing Lambda and EC2, Lambda versus EC2, and deploying an application on AWS, followed by a smooth HR portion. Another reported a few behavioral questions at the end of a single round, so the format may vary.