Academic snapshot
Marks: 60% or 6.0+ CGPA throughout 10th, 12th, graduation (candidate-reported)
Degree: B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT/Maths/Stats/Physics and related)
Backlogs: None active
Gap: Typically max ~2 years
HCLTech is one of India’s largest global IT services companies, providing software development, infrastructure management, and digital engineering to clients worldwide. Founded in 1976 and headquartered in Noida, it employs over 227,000 people and is a major campus recruiter across engineering colleges.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
HCL is a volume campus hirer. The academic floor is the usual Indian IT 60% throughout story; the OA still deletes people who cannot finish one program and a quant block.
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus / pool | PPT, college % list, possible GD + paper-pen track (GFG 2025) | Aptitude + coding bar |
| Careers / Naukri | Form + platform invite | Same OA flavour |
| Referral | Visibility | You still sit every elimination round |
Off-campus does not mean easier quant. It often means more applicants who skip sectional practice and fail one MCQ block.
Is 6.0 CGPA enough? It matches the commonly reported floor across 10th, 12th, and graduation. A 6.2 who finishes aptitude and one coding problem beats an 8.5 who leaves coding blank. A 7.9 B.Tech with 58% in 12th is how people get dropped after the form.
10th / 12th: They count. Keep marksheets. “Throughout” is not a slogan.
Gaps and backlogs: Active backlogs are a hard blocker. Max about 2 years education gap appears in many tables (wider than some peers at 1 year). Full-time degrees only.
What helps the resume screen: Readable English, one project, any internship. See certifications after aptitude and one language, not instead of them.
Academic snapshot
Marks: 60% or 6.0+ CGPA throughout 10th, 12th, graduation (candidate-reported)
Degree: B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT/Maths/Stats/Physics and related)
Backlogs: None active
Gap: Typically max ~2 years
Skills they actually filter
OA: Aptitude + technical MCQs + 1-2 coding
Interview: OOP, SQL, one live problem, project
Languages: C, C++, Java, Python
Extra on some pools: GD + paper-pen domain track
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| Graduation | 60% or 6.0 | Mailer wins |
| 10th & 12th | Same throughout rule | Keep scans |
| Branches | Wide engineering + listed science | Confirm drive |
| Backlogs | None live | Clear before joining |
| Shifts / relocate | Often asked in HR | Answer a city |
Good fit: You can finish a 90-minute mixed paper without freezing, you will relocate, and you can explain one project in two minutes. You already write loops in one language.
Harder path: You only practiced hard DSA and skipped school quant; you refuse shifts; you blank the coding section. HCL HR is a logistics round.
Branch myth: Non-CS is welcome on listed drives. The coding section does not care that you are ECE. It cares that you submit.
Download 2026 HCL placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
HCL does not publish a permanent official paper set. Papers on this site are pattern trainers for the 90-minute filter and early technical themes, not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Aptitude | Quant, logical, verbal under ~45 min |
| Technical MCQ | OOP, DBMS, DS basics |
| Coding | 1-2 array/string/easy algorithm submits |
| Technical interview | Linked list reverse, frequency maps, SQL GROUP BY |
| HR | Why HCL, city, shifts |
Think of papers as simulators for sectional stamina. HCL reuses themes more than exact clones.
| Theme you saw | Drill next | Why HCL asks it |
|---|---|---|
| Arrays / strings | Two easies back to back | OA coding |
| Linked list reverse | Two pointers | Technical |
| Frequency map | Hashing cousins | Technical |
| SQL GROUP BY | Joins + HAVING | Technical |
| Quant speed | Percentages, time-work | OA aptitude |
HCL hires freshers through campus cells, pool drives, careers / job portals, and referrals. After eligibility, the shape is classic Indian IT services: mixed OA, short technical, HR. Some 2025 pools added GD and a handwritten domain paper.
Campus recruitment
Through college placement cells. PPT, then OA and interviews on a batch timeline. Listen for GET vs other titles.
Pool / off-campus
Multi-college GET drives (see GFG Feb 2025). Careers portal and Naukri/LinkedIn posts through the year.
Referrals
Help the screen. You still need sectional OA and one coding submit.
60% throughout, listed degrees, no live backlogs. Gate.
| Section | Questions (reported) | Time feel | Focus |
|---|---|---|---|
| Aptitude | 15-18 | ~45 min | Quant, logical, verbal |
| Technical | 5-7 | ~20 min | Programming, DS, DBMS, OOP |
| Coding | 1-2 | ~25 min | Arrays, strings, basic algorithms |
Platform: drive-specific. Negative marking: often none claimed. Cutoffs: sectional and overall (older tables: ~60-65% overall; aptitude/technical ~50-55%; at least one coding problem solved).
Pass habit: do not leave coding for “if time.” Bank one green problem, then return to leftover MCQs. No negative marking is not a reason to random-fill if your mailer says otherwise.
Success rate (older hub estimates): about a quarter to a third clear OA. Treat as a vibe.
The February 2025 GET pool note included GD before the paper-pen test. If named: 60-second opinion, do not dominate, do not stay silent. One fact beats five slogans.
Same 2025 note: track choices such as Python/Networking vs Automation/Selenium. They evaluated papers during lunch, then called interviews. If your invite lists tracks, pick the one you can write without an IDE.
Live coding or dry-run (linked list reverse, frequency), OOP, SQL, project. Short answers. “We used React” is not a project story; “I wrote the login query and fixed a null on empty email” is.
Why HCL, relocation, shifts, family, any bond language on the PPT. Know ₹4-4.5 LPA GET from public reports and say you will read the letter.
| Phase | Duration | Notes |
|---|---|---|
| Apply / screen | 3-5 days | Eligibility list |
| OA | 1 day | Sometimes plus GD / written |
| Shortlist | 2-3 days | Or same-week pool |
| Technical + HR | 1-2 days | Sometimes same day |
| College list / letter | 3-7 days | Feb 2025: written 12th, results 20th |
| End to end | ~2-3 weeks common | Pools can compress or slip |
| Component | Focus | Prep move this week |
|---|---|---|
| Aptitude | Speed | Timed mock quiz |
| Technical MCQ | OOP, SQL, DS | 20 one-liners |
| Coding Q1 | Arrays / strings | One complete submit |
| Interview | Linked list, hash, JOIN | Dry-run on paper |
| HR | City, shifts | Two STAR stories |
You can score 70% overall and still miss if coding is zero or aptitude is below the floor. Practise three separate clocks, not one blended mood.
Safe-score habit from older tables: aptitude 60%+, technical 60%+, one full coding solve. Excellent is two coding solves if time remains.
Saturday 10:00: 90-minute full OA.
Saturday 12:00: 20-minute OOP + SQL oral.
Saturday 16:00: one GD topic if your pool names it.
Sunday 11:00: handwritten track sheet (Python or Selenium) if named.
Sunday 12:00: HR including city and shifts.
Two weekends of that beat twelve nights of random TCS dumps.
10th, 12th, all semesters, ID, photo if asked, resume one page. Throughout 60% means the 12th PDF matters. Name and percentages must match the form.
Campus mailers usually say Graduate Engineer Trainee. Some pools mention infrastructure, engineering, or applications tracks after you clear the same OA. Do not prep three syllabi. Clear the 90-minute filter first. If a paper-pen track is named (Python/Networking vs Automation/Selenium), that is the only extra syllabus.
Infrastructure flavour: OS one-liners, IP vs TCP, what a ticket queue is.
Applications flavour: OOP, SQL, one language.
Automation flavour: locators, waits, one test you can draw.
If the PPT never names those words, ignore this subsection.
Older explainers claim no negative marking. That is not permission to tap random options in the last 40 seconds. Some platforms still score honesty flags or sectional attempt patterns. Finish every easy question you can read. Guess only if the mailer says there is no penalty and you have leftover seconds, not leftover panic.
GET tables sometimes split a training stipend then full ₹4-4.5 LPA. Ask HR when the annual number starts. Do not spend the stipend month as if the CTC is already in your account. Confirm PF language on the letter like an adult.
If the pool lists GD: pick a side in the first 20 seconds, give one fact, let two other people talk, come back with a close. Do not recite a newspaper. Do not stay silent. Do not attack. The bar is “can this person sit on a client call without freezing,” not a debate trophy.
That sequence is how the linked-list reverse and frequency questions in 2024-2025 notes actually go. Skipping step 1 is how people code the wrong thing.
Volume hiring needs a cheap first filter. Aptitude deletes people who cannot finish school math under time. Technical MCQs delete people who never opened DBMS. Coding deletes people who cannot submit. Interviewers then only see a smaller room. Your job is to be cheap to say yes to: all three sections green, project in two minutes, city answer ready.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a HCL Technologies invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for HCL Technologies sits around ₹4-4.5 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Candidate-reported campus floors commonly cite 60% or 6.0+ CGPA across 10th, 12th, and graduation; B.E./B.Tech/M.E./M.Tech/MCA/M.Sc (CS/IT/Maths/Stats/Physics and related); final-year and recent grads (often within 2 years); no active backlogs; max about 2 years education gap; full-time degrees. Always verify the drive notice.
What you are training for: Common fresher shape: online assessment (~90 min: aptitude, technical MCQs, 1-2 coding) → technical interview (~30-45 min) → HR (~20-30 min). Some 2025 pool campuses added GD and a paper-pen domain test with track choices (Python/Networking vs Automation/Selenium). End to end is often 2-3 weeks.
Short version of the prep split: Split time roughly: 40% timed aptitude, 30% one complete coding problem in C/C++/Java/Python, 20% OOP/SQL/DBMS one-liners, 10% HR (relocation, shifts). Clear sectional cutoffs; at least one coding submit. Full plan: /hcl/preparation-guide/.
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the HCL Technologies previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most HCL Technologies drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at HCL Technologies usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why HCL Technologies?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a HCL Technologies-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the HCL Technologies story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed HCL Technologies papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many HCL Technologies papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in HCL Technologies-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed HCL Technologies paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why HCL Technologies. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Week-by-week calendars live on the preparation guide. This section is the focus split so you do not spend August on the wrong sport.
| Bucket | Share | What “done” looks like |
|---|---|---|
| Timed aptitude | 40% | One 45-min block at cutoff pace |
| One complete coding submit | 30% | Green on arrays/strings without IDE panic |
| OOP / SQL / DS one-liners | 20% | Four pillars + one JOIN + list reverse dry-run |
| HR + (if named) track / GD | 10% | City sentence; 20 handwritten track notes |
The biggest miss is leaving coding for last and failing the sectional. Invert that: write one program first in mocks, then mop MCQs.
Mon-Tue: two full 90-min OAs.
Wed: only coding, two complete easies.
Thu: OOP + SQL oral.
Fri: HR + city.
Sat: combined mock.
Sun: error log only, then sleep.
If you have eight weeks, follow the nested guide instead of inventing a third calendar.
Reuse the aptitude muscle. Do not start a new dump site. Add HCL’s sectional coding submit and, if the pool names it, a GD plus handwritten track. Keep one language. Keep one resume PDF. If two OAs land on the same morning, sit the one whose cutoff you have mocked this week. Sleep still wins. Keep the same email thread from PPT to offer so you can prove what the cell announced if the college list moves later. A classroom “selected” list that shrinks the next morning is a services-hiring story, not a rumour. Wait for the PDF before you resign anything else. Keep a backup services process live until both the letter and the cell list agree.
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on role, location, hiring year, and written components (base / variable).
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Graduate Engineer Trainee | ₹4-4.5 LPA | Primary band for this hub |
| Associate (1-2 YOE) | ₹6-7 LPA | Not the fresher campus default |
| Software Engineer (2-3 YOE) | ₹8-10 LPA | Lateral |
| Senior Software Engineer | ₹12-15 LPA | Outside fresher prep scope |
Confirm base vs variable and joining location on the written offer. Do not treat blog midpoints as guarantees.
Health insurance, training period length, shift norms, relocation to Noida/Bengaluru/Chennai/Hyderabad/Pune. Day-one work is still project staffing.
Know GET ~₹4-4.5 LPA. Ask stipend vs full CTC if the PPT splits them. Ask any service agreement amount in the letter.
GET remains the campus title
₹4-4.5 LPA style bands persist in student reports. Do not prep as if HCL became a 20 LPA product company.
Some pools add GD + paper-pen
February 2025 GFG: OA, GD, handwritten track, then interviews. Read the schedule twice.
Sectional OA still bites
One blank coding section still kills a decent MCQ score.
Interview themes are fundamentals
Linked lists, hashing, SQL, OOP. Not distributed systems.
Net for 2026: do not wait for HCL to become coding-only. Double down on timed aptitude, one complete program, and a city answer.
Yes. Free HCL placement papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the archive.
OA (~90 min) → technical → HR. Some pools add GD and a paper-pen domain track. Often 2-3 weeks. Details: online assessment.
Usually 3 after apply. Pools may add GD and written. Count the mailer.
Not always. A Feb 2025 GET pool GFG note had OA, GD, then Python/Networking vs Automation/Selenium paper-pen before interviews. Prepare the extra round only if named.
Common report: ~90 minutes, aptitude 15-18, technical 5-7, coding 1-2. Sectional plus overall cutoffs. At least one coding submit.
Older tables: overall ~60-65%, sectional ~50-55%, one coding problem solved. Drive-specific. Clear every section.
C, C++, Java, Python on most invites. Pick one. Interview follows that language plus OOP/SQL.
Commonly 60% or 6.0 throughout; listed degrees; no live backlogs; gap ≤ ~2 years. Your mailer wins.
GET ~₹4-4.5 LPA (candidate-reported, August 2026). Confirm the letter.
Noida HQ plus Bengaluru, Chennai, Hyderabad, Pune and other centres. Relocation and shifts are common HR questions.
Timed aptitude, one complete coding submit, OOP/SQL, HR logistics. Guide: preparation guide.
Finish one coding problem completely. Clear every OA section. If a domain track is named, pick one sheet and revise it by hand.
All volume services GET-style hiring. HCL’s twist on some pools is GD + handwritten track. TCS NQT is a different branded exam. Prep aptitude+one language for all; add HCL’s sectional coding habit.
Same family: mixed aptitude plus coding. HCL’s reported 25-30 item / 90 min split is compact. Virtusa ASE notes sometimes run longer multi-section papers with communication. Practise skip rules either way.
If the PPT mentions a bond, decide yes/no before HR. If it does not, do not invent one. Ask for the clause in writing if they name a number.
Often yes on listed drives. You still sit coding. Submit one program.
Registration shared 1 February. OA, group discussion, then a 12 February paper-pen test with track choices (Python/Networking vs Automation/Selenium). “After completing the test, we were given lunch while the HCL team evaluated the papers,” then technical and HR. College results landed 20 February. Takeaway: read the pool schedule; a handwritten track is not a rumour if the mailer says so. Source: GeeksforGeeks GET pool 2025.
B.Tech CSE ~8.0: OA matched the mailer; technical asked linked-list reverse (two pointers) and character frequency (hash map), plus OOP/SQL and a project bug story; HR on Why HCL and night shifts. Selected. Another IT/ECE ~7.2 profile saw tighter OA time and a SQL GROUP BY warm-up. Takeaway: fundamentals plus a coherent project beat a high CGPA with weak explanation. More: interview experience.
What to steal: sectional OA clock; one complete coding submit; linked list + hash + JOIN dry-runs; city/shift sentence.
What to ignore: Paying for “HCL dumps”; assuming every drive is OA-only; quoting 8 LPA on GET.
OA composite: Candidates who banked one green coding problem and mopped MCQs passed. Candidates who chased a second algorithm with zero submits failed the sectional. Complete is the bar.
Pool composite: GD plus handwritten track plus lunch-time evaluation is a real 2025 story. Keep a pen that works. Name and percentages must match the form.
Technical composite: Interviewers who asked linked-list reverse wanted to hear “two pointers, O(n), empty list and single node.” Interviewers who asked SQL wanted GROUP BY, not a stored-procedure lecture. Short correct beats long vague.
HR composite: Night-shift and Noida/Bengaluru relocate questions are not small talk. A 30-second honest answer (“I can do 6-month rotational shifts; I cannot do permanent night from month one”) is cleaner than a fake yes you will reverse after the PDF.
HCL is volume services GET. ₹4-4.5 LPA is a real job. The OA is a mixed filter. Some pools add GD and a domain paper. Students who treat coding as optional and aptitude as “I’ll manage” are the ones sectional cutoffs are about.
Use timed papers on this site. Follow the preparation guide for a week calendar. Read the HR page for location and shift questions. Finish one program. Print 10th and 12th. Then sit the drive like an adult, not like a dump-PDF scavenger.
If HCL and TCS/Infosys/Wipro all land the same week, compare city, shifts, and joining date. A 4.5 LPA GET you will join beats a rumour 5 LPA with a location you will reject in HR. Keep the same email thread from PPT to offer. Classroom “selected” is not a letter. Wait for the PDF.
Day-one work is still a project and a stack you are assigned. “I will only do GenAI” is a bad HR answer. “I will learn the stack and I already write Java/Python” is the GET answer. Keep that sentence ready.
Interview day logistics: Laptop charged if OA is remote; college ID if on campus; pen for paper-pen tracks. Do not sit a proctored test on hostel Wi-Fi that drops every three minutes.
Keep practising until skip rules and one complete submit are automatic. That is HCL. Everything else is decoration.
More narratives: HCL interview experience.
TCS · Wipro · Infosys · Accenture · Cognizant · Mphasis
Last updated: August 2026.