DSA, OOP and Project Defence round·Engineering·Easy·20 min

HCL Graduate Engineer Trainee Interview — DSA, OOP and Project Defence

20 min · 1 credit · scorecard at the end
Z
ZeroPitch Research Desk
Updated 2026-05-24 · Newly added · be among the first to take it
Field
Engineering
Company
HCL Technologies
Role
Graduate Engineer Trainee
Duration
20 min
Difficulty
Easy
Completions
New
Updated
2026-05-24

What this round is about

  • Topic focus. A 45 to 60 minute HCL Graduate Engineer Trainee technical round covering your final-year project, one DSA snippet, OOP fundamentals, SQL joins, and process versus thread.
  • Conversation dynamic. Priya Kumar, Senior Engineering Manager at HCL Hyderabad, runs the round like a real campus drive: warm open, sharp middle, encouraging close. She interrupts on every we built and on every textbook answer without a real example.
  • What gets tested. Ownership clarity, conceptual depth on CSE basics with one real example each, code-writing fluency on basic DSA, honest admission of gaps, and one concrete reason for HCL.
  • Round format. Conversation paired with a live canvas where the DSA problem appears as a card — sketch your linked-list pointers or self-join shape there, or dictate code line by line if you prefer. A methodology tracker on the right edge ticks as you cover each must-have beat.
  • Time budget. Around five minutes warm-up plus self-intro, twenty on the project plus OOP plus SQL block, ten on the DSA snippet, and the last five on why-HCL plus relocation. Priya keeps the clock visible and does not extend the round for verbose answers.

What strong answers look like

  • First-person project ownership. Sounds like: I wrote the Python Flask backend and the MySQL schema for our hospital app; my teammate built the React frontend. I picked MySQL over MongoDB because appointments link to patients link to doctors.
  • OOP with real code example. Sounds like: I used inheritance in my project — my Doctor class extends Person because Doctor has every field a Person has plus a specialization and a license number.
  • Actual SQL syntax for joins. Sounds like: SELECT e1.name FROM employee e1 JOIN employee e2 ON e1.manager_id equals e2.id JOIN employee e3 ON e2.manager_id equals e3.id. Not English pseudocode.
  • Honest knowledge boundary. Sounds like: I do not remember the exact difference between malloc and calloc, but I know both allocate heap memory and calloc initializes to zero — let me think through what else.
  • Concrete process-versus-thread anchor. Sounds like: a process owns its own address space and the OS gives it isolated memory pages, while threads share the parent process's heap and only have their own stack and registers — that is why thread context switches are cheaper but a single thread crash can take down the whole process.

What weak answers look like (and how to avoid them)

  • We built blur. Replace every we with I or with my teammate did X while I did Y. The interviewer interrupts within 30 seconds of a we.
  • Textbook OOP recital. Inheritance is reusing code is a definition, not an answer. Always pair the definition with one example from your own code.
  • Pseudocode for SQL. When asked to write a query, write SELECT and JOIN keywords. English sentences fail this beat.
  • Resume tech without snippet. Listing React or Docker without being able to write a five-line snippet ends the interview early.
  • Process-versus-thread cliche. Saying 'process is heavy and thread is light' with no memory-layout or context-switch reason. Mitigation: always pair the heavy/light claim with one structural fact — separate address space versus shared heap, or kernel-level versus user-level scheduling.

Pre-interview checklist (2 minutes before you start)

  • Recall your project in 60 seconds. Rehearse a first-person walkthrough naming files or modules you personally wrote.
  • Have one OOP example ready. Pick one of the four pillars and tie it to one class in your code.
  • Pull up one SQL join. Be ready to write an INNER JOIN and a SELF JOIN in actual syntax, not English.
  • Think of one process versus thread anchor. One sentence on the memory layout difference plus one example from any program you have run.
  • Identify your why HCL. One concrete reason — a project on your resume that ties to BFSI, a specific HCL product, or the program fit.
  • Re-read one technical decision you would reverse today. Priya asks this in the reflection block and rewards self-aware answers.

How the AI behaves

  • Probes every claim. Asks for the file you wrote, the line of code, the row in the table — never accepts the headline alone.
  • No mid-interview praise. Will not say great answer or perfect. Acknowledges the specific content in 5 to 15 words then pushes deeper or raises an objection.
  • Interrupts on we built. Within 30 seconds of any we when ownership was asked, she will cut in and ask what YOU built.
  • Pivots when stuck. If you stall on DSA she switches to a project question and circles back later instead of letting you freeze.
  • Drives back to ownership on every collective answer. Priya does not let any 'we built' slide for more than two beats — expect a direct 'what did YOU specifically write?' immediately after, even mid-sentence.

Common traps in this type of round

  • We built blur. Using collective voice when the question was about individual contribution.
  • Textbook OOP. Reciting four pillars with no example from your own code.
  • Pseudocode for SQL. Writing English sentences when actual SELECT JOIN syntax was asked for.
  • Resume tech bluff. Listing React, Docker, or MongoDB but unable to write a 5-line snippet.
  • Process versus thread cliche. Saying process is heavy and thread is light without the memory-layout reason.
  • Any IT company is fine. Answering why HCL with a non-answer that signals zero motivation.

Sample problems you'll face

The 2 problems below are the same ones you'll work through in the live session — no surprises. Read the constraints carefully; the AI persona will refer you to the on-canvas card by problem number.

  1. 1DSA — Reverse a Linked List

    Reverse a singly linked list in place and walk through your code for the sample input. Priya will follow with a self-join SQL query — you can sketch your approach for both on this canvas.

    Example input1 → 2 → 3 → 4 → NULL
    Example output4 → 3 → 2 → 1 → NULL
    • In-place — no extra array/list allocation beyond pointers
    • Use the canvas to sketch your logic — draw, write pseudocode, or freehand whatever helps you think — explain your loop invariant
    • After coding: trace through the sample input, then state edge cases (NULL head, single node)
  2. 2SQL — Employee Self-Join

    Write a SQL query to return employees whose managers themselves have managers (3-level hierarchy). Use the Employee table with empId, name, managerId. Priya expects actual SELECT/JOIN/ON syntax, not pseudocode.

    Example inputEmployee table: (1, Alice, NULL), (2, Bob, 1), (3, Carol, 2), (4, Dan, 3)
    Example outputCarol, Dan
    • Use real SELECT / JOIN / ON syntax — no pseudocode shortcuts
    • Alias the Employee table at least twice for the self-join
    • Dictate line by line if you need to — Priya will read along on the canvas
    • Use the canvas to sketch your logic — draw, write pseudocode, or freehand whatever helps you think.

Interview framework

You will be scored on these 6 dimensions. The full rubric with definitions is below.

Project Ownership Clarity
How precisely you name what YOU built versus what teammates built, with specific files, modules, or screens — not collective we language.
25%
Cse Fundamentals Depth
Whether each OOP, DBMS, or OS concept is paired with a real example from your own code, not a textbook definition recited from memory.
20%
Code Writing Fluency
Whether you can dictate working code (reverse-linked-list, SQL self-join) line by line in 8 minutes, in your preferred language, including head pointer and aliasing details.
20%
Honest Knowledge Boundary
Whether you say I do not know cleanly on real gaps and then reason from what you do remember, rather than bluffing with buzzwords or stonewalling.
15%
Hcl Motivation Specificity
Whether your why HCL answer is concrete (service line tie, named product, program fit) or a generic any IT company non-answer.
10%
Communication Discipline
Whether you answer the question asked, in roughly the time budget signaled, without filler or rambling.
10%

What we evaluate

Your final scorecard breaks down across these dimensions. The full rubric and tier criteria are revealed inside the interview itself.

  • Project Ownership (First-Person Signal)25%
  • CSE Fundamentals (Example-Grounded Depth)20%
  • Code Writing Fluency (Dictated Line by Line)18%
  • Honest Knowledge Boundary (Under Pressure)15%
  • HCL Motivation Specificity12%
  • Communication Discipline (Fresher-Appropriate)10%

Common questions

What does the HCL Graduate Engineer Trainee technical interview actually test?
It tests four things in 45 to 60 minutes. First, can you walk through your final-year project in 60 seconds and defend every technology choice in first-person language. Second, can you write a working reverse-linked-list snippet or string reversal in 8 minutes in your preferred language. Third, can you explain OOP four pillars, SQL joins and normalization, and process versus thread with one real example each from your own code, not textbook definitions. Fourth, can you stay honest under pressure and say I do not know cleanly instead of bluffing.
How should I structure my answer in the opening 90 seconds?
Lead with what your project does in one sentence, who it is for in one sentence, and what YOU personally built — name files, modules, or screens — in two sentences. Avoid the word we entirely in the opening. Reserve we for collaboration moments later. Priya will interrupt within 30 seconds of a we built and ask again, so front-load the I built language. Keep the technology stack to one sentence and offer to deep-dive on any layer she asks about.
What are the most common mistakes in this round?
Five repeat offenders. Saying we built when asked what you built. Giving textbook OOP definitions like inheritance is reusing code with no example from your own project. Writing English pseudocode when she asks for actual SQL with SELECT and JOIN. Listing React or MongoDB on the resume but being unable to write a five-line snippet. Answering why HCL with any IT company is fine which signals zero motivation.
How is the AI interviewer different from a real HCL interviewer?
It probes harder than the average HCL panel and never gives you the answer. A real HCL panel may move on after one weak answer to save time. The AI re-probes the same gap from a different angle so you cannot bluff past it. It also never praises mid-interview — no great answer, no perfect. It acknowledges the specific content of what you said in 5 to 15 words and then pushes deeper or raises an objection. Pacing matches real HCL Madhapur rounds.
How is my answer scored?
Six weighted dimensions: project ownership clarity, CSE fundamentals depth, code writing fluency, honest knowledge boundary, HCL motivation specificity, and communication discipline. Each dimension scores 0 to 100 with verbatim example bands and is weighted in the final scorecard. You also see live ticks on a six-element methodology tracker as you cover each must-have rubric beat. The transcript-backed scorecard quotes the exact moment a we built was caught or a SQL pseudocode slip happened.
What should I do in the first 2 minutes before the interview starts?
Recall the one final-year project you will lead with and rehearse a 60 second I built version out loud. Pull up the names of any specific files, modules, or screens you wrote. Have at least one verbatim OOP example from your project ready — like the User class that extends Account. Refresh one SQL join you wrote and one operating-system concept you used. Identify one concrete reason for HCL specifically — a BFSI project on your resume, an HCL product you read about, a relative at HCL — not any IT company.
How do I handle a DSA question I have not solved before?
Do not freeze. State the problem back to confirm input and output. Walk through one or two small examples on paper. Name the brute-force approach first with its time complexity. Then look for a pattern — does a two-pointer, hash map, or recursion help. Write the cleanest version you can, even if it is brute force. Then trace it on the small example. Priya rewards attempt-with-method over silent staring. Saying I would start with a brute-force O of n squared and look for a hash-based optimization is a strong opener.
How do I answer why HCL without sounding generic?
Avoid any IT company is fine for me at all costs. Pick one of three concrete frames. One: tie a project on your resume to an HCL service line — your fintech mini-project to HCL's BFSI UK clients, your IoT project to HCL's manufacturing clients. Two: name a specific HCL property you read about — HCLSoftware, the TechBee program, the Madhapur delivery center. Three: name the program fit — Direct Hire because you want production exposure fast, or TechBee because you value the structured training. One concrete sentence beats three vague ones.
What does a strong project walkthrough sound like?
It sounds first-person, file-specific, and trade-off aware. Example: I built the OTP login and the doctor-availability module, two of the six modules in our final-year hospital app. I wrote the Python Flask backend and the MySQL schema; my teammate wrote the React frontend. I picked MySQL over MongoDB because the data is relational — appointments link to patients link to doctors. If I redid it I would add Redis for session caching because login latency hit 800 ms in our demo. That is the altitude Priya rewards.
What does a weak project walkthrough sound like?
It sounds passive, vague, and team-blurred. Example: We built a hospital management system using MERN stack. It has multiple modules. We used MongoDB for the database. We faced some challenges and we overcame them. That answer earns three interrupts inside 60 seconds. Priya will ask what YOU built and what challenge YOU personally fixed, and if the candidate keeps using we she will go cold and pivot to DSA early. Replace every we with I or with my teammate did X while I did Y.
Do I need to know advanced DSA like dynamic programming or graphs?
No. HCL freshers are tested on basics: arrays, strings, one or two linked-list operations, simple recursion. Reverse a linked list, find the second largest in an array, check a palindrome, print Fibonacci, write a SQL self-join. Depth-first search and dynamic programming are out of scope for the standard Graduate Engineer Trainee technical round. Spend your prep on the basics until you can write them flawlessly in 8 minutes, not on LeetCode hard.

Sources this interview is built on

Real candidate-report URLs (Glassdoor / AmbitionBox / PrepInsta / GeeksforGeeks / Medium) reviewed when authoring the questions, persona, and rubric. Verify the realism yourself.