Inside HCL Technologies’ 4-Stage Placement Drive at Parul University: The Autonomics Engineer Role, the IBM Letter of Intent, and the Decision Between Them

HCL Technologies‘ placement drive at Parul University for the 2026 batch was structured across four sequential stages, conducted partly online and partly on-campus. The four stages collectively assessed quantitative aptitude, communication, technical fundamentals, and behavioural fit for the Autonomics Engineer role.

• Stage 1, Online MCQ test: the standard first-round filter covering aptitude, logical reasoning, and basic technical fundamentals. Conducted online with all eligible candidates from the campus drive.
• Stage 2, Offline English proficiency test: conducted on the Parul University campus in October 2025. The English assessment was designed to verify communication readiness for a customer-facing engineering role and is the stage that produced the logistical complication described below.
• Stage 3, Online technical interview: covered the core computer science subjects directly relevant to the Autonomics Engineer role, including operating systems, DBMS concepts, OOP principles, and applied problem-solving.
• Stage 4, HR interview: conducted approximately two days after the technical interview. Covered behavioural assessment, role-fit questions, and the practical conversation about start dates, location, and joining logistics.

The most chaotic moment of the entire HCL placement journey was not a technical interview question. It was a notification. The intimation that the HCL offline English test would be held on 24 October 2025, on the Parul University campus, arrived at night while Chandrika was on a train travelling from Ahmedabad to Andhra Pradesh. She was midway through the journey, heading home, with no plan to be back on campus that week.

I was travelling from Ahmedabad to Andhra Pradesh on train. It was midway. I would be reaching home on 22nd. If I want to be there on 24th, I need to travel back. So I just reached home, stayed for half a day, and travelled back at night. I reached college by one. I even enquired with Vijaya ma’am: can we take this test online? There was a whole confusion about whether it was online or offline. She told me to show up.

Naga Chandrika Eluru, on the HCL English test logistics

She made the journey. Reached home, stayed for half a day, travelled back overnight, and arrived at Parul University campus by 1 PM. She sat the offline English test on 24 October 2025 as scheduled. What that sequence reveals is not just logistics. It is the structural measure of how committed the candidate was to the placement she had spent two years preparing for. A student willing to make a return train journey across two states to sit a single English proficiency test was not going to be derailed by a difficult question in the technical round.

Read More: Green job initiative with free EV training at Parul University.

Chandrika’s technical interview at HCL drew directly from the concepts covered in Parul University’s Impact Training programme. Operating systems fundamentals, database management system concepts, object-oriented programming principles, and applied problem-solving in DSA all featured. The complete account of how Impact Training prepared her for exactly these interview themes is in the dedicated article on the Impact Training programme and the Striver DSA path. The headline observation she made directly was that the material she had been preparing through structured training was the material the interviews tested. No reinvention. No frantic last-minute learning. Application of work already done.

The technical interview also tested her project portfolio. The interviewer questioned her on the architecture choices behind her Perplexity-style AI search assistant, the data integration approach in the Agriculture Assistant final-year project, and the deployment workflow she had used to push her Argo-XIT project to Render’s platform. The four months at Keyanna Technology Pvt Ltd as a Python Developer on a live AIOps project provided the practical context for many of these answers. She did not have to invent industry references. She had real production deployment experience to anchor her technical answers to.

After the four-stage drive, the HCL selection result was released in a structurally unusual way. A preliminary selected-candidates list was shared after the interviews. Chandrika’s name was not on that initial list. She had given the interview and felt it had gone well. The absence of her name was disorienting.

There was a sheet I got before the selection was final. It was stated after my interview that my name wasn’t in there. I was shocked. I gave the interview pretty well. And then after two days we got another sheet. The selection was not static; it was growing. First it was for only ten, then twenty-three, then thirty-three. They were taking interviews and selecting in batches. I was confused because I thought the first result might be the final result.

Naga Chandrika Eluru, on the HCL selection process

The structural insight here is operationally important for any candidate going through a large corporate placement drive. HCL Technologies’ selection at Parul University was not a single binary release of the final candidate list. The selection was rolled out in waves as additional interview batches were processed. The first list represented an initial cohort. The second and third lists represented subsequent batches of approved candidates as the company worked through the full interview load. Chandrika’s name appeared in the subsequent batch. The HCL offer was confirmed. The pattern is worth documenting because the initial absence from a list does not signal rejection in this drive structure.

Over approximately the same placement window, IBM conducted a separate on-campus placement drive at Parul University for the Associate Software Engineer role. Chandrika cleared the IBM process and received a Letter of Intent for the role. The IBM LoI status differs from the HCL full offer in two important ways: the IBM Associate Software Engineer role does not specify the technology stack or specific engineering team at the time of the LoI, with that assignment happening after formal joining; and the joining date and final compensation details are confirmed through the post-LoI onboarding process rather than at the LoI stage itself.

Both outcomes (the HCL full offer and the IBM LoI) are documented placement results from the Parul University 2026 placement cycle. The simultaneous management of two corporate placement processes is itself an operational test that candidates are not always prepared for. Maintaining application discipline, interview preparation continuity, and decision composure across two parallel drives requires capacity that single-process candidates never have to demonstrate.

When Chandrika ultimately chose HCL Technologies over IBM, the decision was structurally rational rather than driven by prestige or compensation. The HCL Autonomics Engineer role was defined upfront. The skill set required for the role was known. The engineering domain was identified. The candidate knew, before signing the offer, what she would be working on at the start of her career.

The skills I have for HCL: I know them. IBM is an Associate Software Engineer, but we are not sure until we get into the company. Until we get in, we don’t know where we will be working or what technology we will work on. But for HCL it was already known: the role was defined. That is why.

Naga Chandrika Eluru, on the HCL versus IBM decision

The IBM Associate Software Engineer role, by contrast, assigns the specific technology stack and team after joining. For some candidates, this is acceptable or even attractive: the variety of possible assignments represents broader optionality. For Chandrika, role definition before joining was the decision-controlling factor. She wanted to know what skills she would be exercising on day one, and what skill development trajectory she would be building on top of. The HCL role gave her that clarity. The IBM role asked her to commit before knowing.

Chandrika is currently undergoing pre-joining training with HCL Technologies, a preparatory phase that, in her account, is further strengthening her fundamentals ahead of the formal joining date. Her five-year plan treats HCL as the starting point for one to two years of specialised AI DevOps skill development, followed by targeted pursuit of more advanced roles at organisations operating in that specific technical area. The complete career arc context is in the hub article on her overall placement story.

Read More: From a Confused First Year to HCL and IBM Offers.

When Chandrika ultimately chose HCL Technologies over IBM, the decision was structurally rational rather than driven by prestige or compensation. The HCL Autonomics Engineer role was defined upfront. The skill set required for the role was known. The engineering domain was identified. The candidate knew, before signing the offer, what she would be working on at the start of her career.

The skills I have for HCL: I know them. IBM is an Associate Software Engineer, but we are not sure until we get into the company. Until we get in, we don’t know where we will be working or what technology we will work on. But for HCL it was already known: the role was defined. That is why.

Naga Chandrika Eluru, on the HCL versus IBM decision

The IBM Associate Software Engineer role, by contrast, assigns the specific technology stack and team after joining. For some candidates, this is acceptable or even attractive: the variety of possible assignments represents broader optionality. For Chandrika, role definition before joining was the decision-controlling factor. She wanted to know what skills she would be exercising on day one, and what skill development trajectory she would be building on top of. The HCL role gave her that clarity. The IBM role asked her to commit before knowing.

Chandrika is currently undergoing pre-joining training with HCL Technologies, a preparatory phase that, in her account, is further strengthening her fundamentals ahead of the formal joining date. Her five-year plan treats HCL as the starting point for one to two years of specialised AI DevOps skill development, followed by targeted pursuit of more advanced roles at organisations operating in that specific technical area. The complete career arc context is in the hub article on her overall placement story.

Read More: From a Confused First Year to HCL and IBM Offers.

One detail that distinguishes a placement-ready candidate from a credential-only candidate is the ability to reference real production experience in interview answers. Chandrika‘s four-month internship at Keyanna Technology Pvt Ltd from January to April 2026 provided exactly that.

My work was focused on the destination microservice, which gave me exposure to how data flows across systems and how backend services are designed in real environments.

Naga Chandrika Eluru, on her internship at Keyanna Technology

The most operationally useful learning from the internship was the gap between local development and server deployment. Code that ran perfectly on her local machine produced multiple server-side errors when pushed to production. The errors were not in her business logic. They were in the surrounding ecosystem: Docker container configuration, server-side dependencies, and the operational layer that production software actually runs on.

The code I had was working perfectly on my local. But when I pushed it to the server, it was not working. The same code base: exactly the same, not a single change. I was pushing to the server but still getting huge errors. When I went to solve those errors, the first one was a server-side error. After solving that too, there were other errors. It was totally on the DevOps side: not only working on the code base, we need to know the basics of other technologies, like Docker, so we can understand where exactly the error is coming from.

Naga Chandrika Eluru, on the production deployment gap

This kind of practical learning, encountered during a real industry internship rather than imagined in a classroom, is precisely what HCL Technologies’ Autonomics Engineer role expects in a fresher candidate. The interview answers built on real production debugging experience carried weight that classroom-only answers cannot. The internship was, in operational terms, the placement-bridging asset.