Engineering Intern (DevOps, Backend, Frontend, iOS) - applied for DevOps/Infrastructure team
Interview Date
Not Specified (Experience likely around February 2025)
Result
Selected (Implied, as it's an experience sharing g
Difficulty
Medium (Online Assessment DSA questions)
Rounds
3 rounds
Drive Type
Internship
Topics asked
Detailed experience
College: Not Specified (2024 batch)
Interview Date: Not Specified (Experience likely around February 2025)
Interview Type: Internship
Result: Selected (Implied, as it's an experience sharing guide)
Difficulty: Medium (Online Assessment DSA questions)
Rounds: 3 rounds
Topics Asked: CS Fundamentals (CN, DBMS, Linux, OS), DSA (Hashing, Binary Search Trees), System Design (Master-Slave Architecture, Downtime, Blueprint Deployment, Reliability), Behavioral, Project/Internship Experience, Implementation-based questions
This experience details the internship interview process for Titan (Directi) for an Engineering Intern position, specifically for the DevOps/Infrastructure team.
Round 1: Online Assessment (1 hour 15 minutes)
The online assessment included MCQs from basic core subjects like CS fundamentals (Computer Networks, DBMS, Linux-related questions). It also featured two medium-level DSA questions, often involving concepts from hashing and binary search trees. The time limit was sufficient.
Round 2: Technical Interview (More than an hour)
This round was taken by a team member. It covered extensive discussions on CS fundamentals, including Linux (file permissions, shells, symbolic links, standard streams, processes, threads). System design questions were asked, such as master-slave architectures, ensuring no downtime, and blueprint deployment. Scenario-based questions were presented to design solutions for database downtime and build reliable systems. The recruiter was supportive and provided reference materials for preparation.
Round 3: Managerial Interview (45-50 minutes)
This round was conducted by the manager of the team the candidate was recruited for. It included both behavioral and technical questions. Discussions covered previous internship experiences. Questions related to core DBMS and CN subjects were asked. An implementation-based question was given, requiring the candidate to explain a step-by-step pseudo-code for parsing a set of IP addresses and producing a required output, allowing the use of Python or any scripting language.
Overall Experience: The candidate implies selection as they are sharing a guide to cracking the internship process. Tips include consistent practice on LeetCode and GeeksforGeeks, researching the company's culture and projects, and starting early to build a resume with projects and internships.