The online assessment consisted of 3 coding questions to be solved within 90 minutes. The questions were focused on core data structures and algorithms:
Graph-based problem
Tested concepts like traversal (BFS/DFS), shortest paths, or connectivity.
Dynamic Programming (DP)
Required optimization using subproblems and efficient state transitions.
Tree-based problem
Focused on binary trees, recursion, or traversal techniques.
The difficulty level was moderate to high, requiring strong problem-solving skills, time management, and a solid understanding of DSA fundamentals.
I applied through other source. I interviewed at Infosys (Chennai) in Nov 2025
Interview
The interview process for a Systems Engineer is a multifaceted evaluation of how you bridge the gap between abstract requirements and reliable, physical, or virtual infrastructure. Unlike software-specific roles, this process prioritizes lifecycle management and inter-component integration.
1. Initial Screening (30 mins)
The recruiter assesses your foundational knowledge and "systemic" mindset. They look for experience in specific environments—be it cloud-native (AWS/Azure), traditional data centers, or specialized sectors like aerospace.
2. The Technical Deep-Dive (2–3 Rounds)
This is the core of the process, typically divided into two distinct areas:
System Architecture: You’ll be asked to design a high-level solution for a problem, such as a global content delivery network or a redundant satellite ground station. You must demonstrate an understanding of the V-Model, showing how high-level requirements flow down into verifiable system components.
Breadth of Knowledge: Expect "probing" questions across networking (OSI model), storage (SAN/NAS), and virtualization. A common scenario involves "Root Cause Analysis," where you must diagnose a systemic failure that isn't immediately obvious.
3. Practical Assessment
Many firms now require a hands-on component. This might involve a troubleshooting lab—where you are given a "broken" environment and tasked with restoring service—or a scripting challenge in Python or Bash to demonstrate your ability to automate infrastructure (IaC).
4. Behavioral & Cross-Functional Fit
Systems Engineers are the "glue" of an organization. This round evaluates your ability to communicate technical trade-offs to stakeholders who may not be technical. You’ll be asked about managing conflicting requirements and how you prioritize reliability, availability, and maintainability (RAM).
5. Final Review
A meeting with senior leadership focuses on long-term strategy, such as migration paths or technological "future-proofing," ensuring your technical vision aligns with the company's five-year roadmap.
There was one round of interviews,
It was a technical round.
Later on, it took 3 months for them to process the offer letter directly.
With a year of working contract.