My General Mills Interview Experience

Hello Juniors! My name is Vinayak Mohanty. I'm a Computer Engineering student at Thadomal Shahani Engineering College (2027 batch). Whenever I was preparing for placements, I found interview experience blogs incredibly helpful, so I wanted to share my own General Mills interview experience in the hope that it helps someone preparing for a similar opportunity.

Disclaimer: Interview processes evolve over time, so your experience may differ slightly. This was the process followed for my batch, and I'm sharing it simply to give you an idea of what to expect.

The Timeline

Here's how the process unfolded:

25 July – Campus hiring announcement.
28 July – Pre-Placement Talk (PPT).
30 July – Online Assessment (OA).
4 August – On-campus interviews.

Around 280 students registered for the process. After the Online Assessment, 18 students were shortlisted for the interview rounds, and eventually, 3 students were selected.

Pre-Placement Talk (28 July)

The Pre-Placement Talk served as an introduction to General Mills and the opportunities they were offering through campus placements.

The session covered:

An overview of the company, its history, and its global presence.
The values and culture at General Mills.
The different roles they were hiring for.
What those roles involved and the kind of work candidates could expect.
The overall hiring process and what the upcoming stages would look like.

It was held in two modes: online and offline. The top students (based on CGPA) from each branch were invited to attend the offline session. Unfortunately, I wasn't one of them :p

One piece of advice I'd give here is to spend some time researching the company beyond just the PPT. Understand what General Mills does, its products, its values, and how its technology teams contribute to the business. It helps you answer HR questions more confidently and also shows genuine interest in the company.

Online Assessment (30 July)

The Online Assessment was conducted on HirePro.

One thing worth noting is that, unlike previous years where the assessment was conducted on campus, our batch was allowed to take the OA from home.

The OA consisted of two sections, both carrying equal weightage:

Technical Section
Non-Technical Section

I found the OA to be of medium difficulty. More than accuracy alone, it tested how quickly you could work through the questions. Time management played an important role, and making educated guesses when you weren't completely sure was sometimes necessary to maximize your score.

Technical Section

The technical portion primarily focused on Core Computer Science fundamentals. The topics included:

Object-Oriented Programming (OOP)
SQL
Computer Networks (CN)
Database Management Systems (DBMS)
Operating Systems (OS)

If you've consistently revised these subjects, the questions should feel familiar. It wasn't designed to test obscure knowledge but rather your understanding of concepts that form the foundation of Computer Science.

Non-Technical Section

The non-technical section included questions based on:

English grammar
Reading comprehension
Logical reasoning
General aptitude

While preparing, several seniors had suggested practicing these types of questions from IndiaBix. This isn't mandatory, but if you're looking for practice material, IndiaBix is a good resource for aptitude and reasoning questions. Solving a decent number of questions there can help you become comfortable with the pattern and improve your speed during the assessment.

Interview Day (4 August)

The interview process consisted of two rounds:

Technical Interview
HR Interview

Technical Interview (35–40 minutes)

The technical round was, for the most part, completely resume-driven.

One thing I noticed immediately was that the interviewers were very experienced. They knew exactly where to probe deeper and often built follow-up questions based on previous answers. Because of this, I would strongly advise against bluffing. If you don't know something, it's perfectly fine to admit it and explain how you would approach the problem. Trying to fake your way through an answer is something experienced interviewers can spot almost immediately.

It began with a simple introduction. I gave a brief overview of myself, primarily focusing on my internship experience and the work I had done there.

The interviewers then asked follow-up questions about it, including:

The background of the company I had interned at.
Where the company was based.
The nature of my responsibilities and contributions.

Resume Experience Discussion

A significant portion of the interview revolved around my resume experiences, including both my internship work and projects.

I was asked to explain one of the projects I had worked on and:

Draw a high-level design of it.
Explain the major components involved.
Walk through the complete flow of the system.
Describe how the different parts interacted with one another.
Clarify my specific contributions and responsibilities in the implementation.

One thing worth mentioning is that this wasn't a formal System Design round.

You are not expected to separately prepare for HLD or LLD interviews. However, you should know your internship work and projects thoroughly.

If something is on your resume, be prepared to explain:

Why you built it that way.
How it works internally.
How data flows through the system.
The decisions you made while building it.

The interviewer had also prepared questions tailored specifically to my resume. I don't remember the exact wording, but one of the discussions revolved around how geofencing was implemented in one of my projects.

An important lesson:

If it's on your resume, assume you'll be asked about it.

Core CS Questions

After discussing my projects, the interviewer asked which Core CS subjects I was comfortable with. I mentioned that I was fine with any of them.

The questions included topics such as:

Operating Systems: Scheduling algorithms.
Databases: Deadlocks.
SQL: Queries involving joins.

The questions were straightforward and focused on conceptual clarity rather than memorized definitions.

Scenario-Based Questions

The technical round also included a few scenario-based questions.

For example, I was asked:

What would you do if you were assigned to a team that wasn't your preferred field of work?

These questions seemed to assess adaptability, mindset, and how you approach situations that may not go exactly as planned. Make sure you are prepared for questions like this.

DSA Questions

The final part of the technical interview focused on Data Structures and Algorithms.

I was asked to solve two fairly simple questions:

A simple palindrome check.
A question that involed implementing Breadth-First Search (BFS).

I was expected to write the code on paper.

Once I finished, the interviewer asked additional follow-up questions, including:

The time complexities of the algorithms.
The differences between BFS and DFS.
Use cases for each algorithm.

The DSA portion wasn't designed to be extremely difficult. Instead, it tested whether you could implement fundamental algorithms correctly and explain your reasoning.

Overall, the technical round focused on three things:

Whether you truly understood your resume.
Whether your Core CS fundamentals were clear.
Whether you could communicate your thought process effectively.

HR Interview (15–20 minutes)

Compared to the technical round, the HR interview was much more relaxed.

There was a single panel consisting of two panelists, and the atmosphere felt more like a friendly conversation than an evaluation.

I was again asked to introduce myself.

The discussion then shifted toward understanding me as a person.

Some of the topics included:

My background.
Where I live.
My family, including my parents and siblings.
My aspirations and future goals.

I was also asked questions such as:

"Where do you see yourself in five years?"
"How do your values align with those of General Mills?"

Towards the end of the discussion, the interviewers asked, "Do you have any questions for us?"

I asked them:

How does General Mills adapt to modern technologies and keep up with the rapidly evolving tech landscape?

I found the discussion that followed quite insightful and appreciated the openness with which they answered my questions.

Overall, the HR round felt less like an interview and more like a conversation to determine whether I would be a good cultural fit for the organization.

The Final Result

After all the interviews had concluded, the waiting began.

About one and a half hours later, all the students were asked to gather in the seminar hall.

There was a mix of nervousness and excitement in the room. After progressing through multiple stages of the process, everything had come down to this moment.

The names of the selected candidates were then announced one by one.

Out of the 280 students who had registered, 18 had made it to the interview stage, and finally, 3 students were selected.

I was fortunate enough to hear my name among them.

As a small gesture, General Mills also presented a gift hamper to each of the three selected interns.

It was a simple moment, but one that felt incredibly rewarding.

All the preparation, interviews, and anxious waiting had finally paid off.

Final Thoughts

You don't need to know everything under the sun. But if you've built something, understand how it works. If you've listed a skill, be prepared to discuss it. And if you don't know an answer, be honest and explain how you would approach the problem.

I hope this gives future candidates a better idea of what to expect from the General Mills interview process.

If you need any further advice regarding the interview, placements in general, or just want to discuss preparation strategies, feel free to reach out to me on LinkedIn! :)

LinkedIn: https://www.linkedin.com/in/vinayak9769

If you're preparing for placements right now, trust the effort you're putting in and keep going. I hope this blog makes the journey a little easier for you! ❤️