Interview Experience – UPTIQ | SDE
Batch: 2027 | Branch: Computer Engineering | Total Rounds: 3
Process Snapshot 📸
Drive: On-campus recruitment drive
Total Rounds: 3
Process: Online Assessment → Technical Interview 1 → Technical Interview 2 (CTO Round)
Round-by-Round Breakdown 📝
Round 1: Online Assessment (OA) 💻
Duration: 2 hours
Date: 24 September 2026
Timing: 8:00 AM – 10:00 AM
Participants: Around 500 students
The OA consisted of 2 DSA questions and 84 MCQs.
DSA Questions (Easy - Medium):
MCQs covered:
HTML & CSS
React
OOP
C Programming
SQL
Database Concepts
Database Optimization
System Design
Operating Systems
Computer Networks
The shortlist was announced around 11:00 AM, and 77 students were shortlisted for the L1 interview.
Round 2: Technical Interview 1 💡
Duration: Around 30–40 minutes
The interview started with a brief introduction about myself. After the introduction, the interviewer moved directly into my internship experience.
Internship Deep-Dive
The interviewer asked detailed questions about my internship and wanted to understand my actual contribution rather than just the technologies mentioned on my resume.
The discussion included:
What was my role?
What problem was I solving?
What implementation did I perform?
What was my approach to solving the problem?
What technologies did I work with?
What exactly did I contribute to the project?
The internship discussion was a fairly deep dive into my practical experience.
DSA — Binary Tree + Linked List
Next, I was given a medium-level DSA problem involving a binary tree and linked lists.
The problem was essentially:
Given a binary tree, create a separate linked list for every level of the tree and return an array containing the heads of those linked lists.
So, for each level of the binary tree, the nodes at that level had to be connected into a new linked list, and the answer had to contain the head of each linked list.
This required combining concepts of tree traversal and linked-list manipulation.
SQL Query
The interviewer then asked me an SQL question:
Find the employees whose salary is greater than the average salary of all employees.
I had to write the SQL query and explain the logic behind it.
Computer Networks
The interviewer also asked a Computer Networks concept:
What is the difference between a public network and a private network?
I explained the distinction between the two and their typical use cases.
DBMS — Indexing
Next, she asked about indexing in DBMS.
The discussion focused on understanding:
What is indexing?
Why is it used?
How does it improve database query performance?
LLD — Factory Design Pattern
The interviewer also asked about the Factory Design Pattern as part of LLD.
I had to explain the concept and how the pattern is used to create objects without directly exposing the object-creation logic to the client.
Resume Project Deep-Dive
After the core technical questions, the interviewer went through my projects mentioned on the resume.
The discussion again focused on practical understanding:
What was my role in the project?
What problem were we solving?
What technologies did I use?
How did the project work?
How did I solve the problems encountered during development?
The interviewer was interested in understanding whether I actually knew the implementation details of the projects I had mentioned.
Questions at the End
At the end of the interview, the interviewer asked whether I had any questions.
I asked:
What are some of the challenges UPTIQ faces while solving engineering problems?
I also asked:
What would the internship period be like, and what kind of projects would interns work on?
That concluded my first technical interview.
Round 3: Technical Interview 2 — CTO Round 🧠
Duration: Around 30–40 minutes
The second technical round was conducted with the CTO of the company.
The interview again started with a brief introduction about myself.
Internship Deep-Dive
The CTO then asked me about my internship experience in detail.
The discussion covered:
What I did during my internship
My role and responsibilities
The problem I worked on
The technology stack I used
The solution I implemented
How my solution addressed the problem
I explained the internship and the implementation in detail.
System Design / Problem-Solving — Elevator System
The CTO then gave me a system design / problem-solving question involving an elevator system.
The problem was:
There are 3 elevators with different floor ranges. Design an energy-efficient algorithm such that only one elevator gets assigned to a request at a time.
The important part of this question was not simply arriving at an algorithm. I first had to clarify the requirements and assumptions.
Whenever I clarified a requirement, the CTO would ask cross-questions based on that assumption.
So the discussion became an interactive problem-solving session where I had to:
Clarify requirements → Make assumptions → Design the approach → Explain the decision-making logic → Handle follow-up questions
This made the question more about system thinking and reasoning rather than simply writing code.
Resume Project Deep-Dive
After the system-design discussion, the CTO moved to my resume projects.
He asked me to explain:
My role in the project
The problem we were solving
The challenges we faced
The complete workflow of the project
How the different parts of the problem were solved
The technical implementation
The focus was again heavily on practical understanding of my own projects.
Rather than just asking what technologies I used, the discussion focused on whether I understood how the complete system worked and why particular decisions were made.
Career Preference — Data Engineering vs Coding
The CTO also asked me about my career preference:
Would you be more interested in a Data Engineering role or a coding/development-oriented role?
This led to a discussion around the type of work I would be interested in pursuing.
HR / Personal Questions
Towards the end, the CTO also asked some HR-type questions, including:
What are your ambitions in life?
What are your weaknesses?
The interview therefore covered not only technical knowledge but also career interests, ambitions and self-awareness.
That concluded my CTO round.
Difficulty, Topics, and Interview Focus 🎯
Based on my experience, the interview process focused heavily on practical understanding rather than purely theoretical knowledge.
The major areas covered were:
Projects and internship experience
DSA
SQL
DBMS
Computer Networks
LLD / Design Patterns
System Design and Problem Solving
Career Preferences
HR / Personality Questions
One of the strongest themes across both technical rounds was the importance of being able to explain the things mentioned on your resume in depth.
The interviewers were interested in:
What did you actually build?
What problem were you solving?
What was your contribution?
Why did you choose that approach?
How does the system actually work?
The CTO round placed additional emphasis on requirement clarification and problem-solving ability, especially during the elevator system-design question.
Final Outcome 🎉
The final selection was divided into:
9 students: Internship + PPO (Fixed)
7 students: Internship + PPO based on performance
My Result: Selected for 6-month Internship + PPO (Fixed)
Final Takeaway 🚀
My UPTIQ interview experience was primarily focused on practical understanding.
The interviewers were interested not just in whether I knew DSA or theoretical concepts, but whether I could explain my actual work, reason through open-ended problems, and defend my technical decisions.
For this type of interview, preparation should cover a combination of:
DSA + SQL + DBMS + Computer Networks + LLD + System Design + Projects + Internship + HR Questions
And most importantly, be ready to go deep into anything you mention on your resume.
