Hey everyone!
I recently attended the Spaulding Ridge hiring process for the Consulting Intern position at Bangalore, and I wanted to share my experience in detail for anyone who might be applying through on-campus or off-campus opportunities in the future.
I am sharing this because I genuinely liked the company's people and overall work environment, but I also felt that certain aspects of the recruitment process could have been better structured.
This is my personal experience and feedback, not an attempt to discourage anyone from applying.
1. Company Presentation and Overall Environment
The process started with a company presentation where they introduced Spaulding Ridge, its business, work culture and opportunities.
Honestly, this was one of the best parts of the experience. The HR team, employees and other staff members were welcoming, professional and approachable. The overall office environment gave me a very positive impression.
I could genuinely imagine myself working in an environment like that. The people I interacted with were good, and I have no major complaints about the company's overall atmosphere.
However, the recruitment process itself left me with mixed feelings.
2. Recruitment Process – Communication Could Have Been Better
One thing that I felt was not communicated clearly was whether the hiring drive was being conducted as an on-campus or off-campus recruitment process.
There were approximately 100–120 candidates participating in the hiring process, and I believe the recruitment stages, selection criteria and job details should have been communicated more clearly beforehand.
This becomes especially important for candidates travelling from other states.
Before travelling, candidates should ideally have clear information about:
- Whether the opportunity is on-campus or off-campus.
- Complete selection rounds and elimination criteria.
- Job location and work arrangement.
- Working days and expected responsibilities.
- Stipend and other relevant employment details.
As communicated during the process, the internship involved five working days per week and an approximate stipend of ₹20,000 per month.
My suggestion to future applicants is to clarify these details with the recruitment team before making travel arrangements.
3. Group Discussion – My Biggest Concern
The GD round was the part I felt could have been designed better for a Consulting Intern position.
The topics given to our group included:
- Are electric vehicles good or bad?
- Nuclear energy.
- Do deadlines affect creativity?
These are interesting general discussion topics, and they certainly allow candidates to express opinions, demonstrate confidence and communicate with others.
However, my question is: How closely does a general discussion on these topics evaluate someone's suitability for a business and technology consulting role?
I understand that communication is extremely important in consulting. Candidates need to communicate with clients, explain solutions, participate in discussions and work with teams.
But if the main objective of the GD is to evaluate communication skills, why not conduct a business-oriented discussion or a practical case-based activity?
For example:
- A company wants to automate its manual business operations. How would you approach it?
- A client is facing problems with inaccurate business data. What would you recommend?
- Should a company invest in AI or traditional automation?
- How can a business use data analytics to improve decision-making?
- A company wants to migrate its operations to the cloud. What factors should it consider?
These topics would still evaluate communication, confidence, teamwork and the ability to express opinions, but they would also help assess business understanding and problem-solving abilities.
The elimination ratio
Another concern was the elimination ratio during the GD.
From what I observed, groups consisted of approximately five candidates, and around three candidates were eliminated from each group.
That means a significant number of candidates were filtered out through a single group discussion.
I understand that companies need to shortlist candidates, particularly when there are 100–120 participants. However, when such a large proportion is eliminated in one round, the evaluation criteria should be transparent and closely connected to the job requirements.
I also feel that the evaluation should not depend only on how frequently someone speaks or how confidently they present an opinion.
Listening skills, logical reasoning, the relevance of arguments, teamwork, respectful disagreement and the quality of contributions are equally important.
A candidate might have strong technical skills, good academic projects and relevant experience but may not necessarily dominate a general discussion. That should also be considered.
4. One GD Topic in Detail – Do Deadlines Affect Creativity?
Our group had different opinions on this topic.
Three members argued that deadlines do not necessarily affect creativity. Their perspective was that deadlines are simply limitations that encourage discipline, prioritisation, time management and faster execution. They also suggested that working under pressure can sometimes encourage people to think differently and develop innovative solutions.
However, another candidate and I had a different perspective.
We argued that unrealistic deadlines can affect creativity because innovation requires time for research, experimentation, testing and exploring alternatives.
For example, when developing a new product, a team might identify a unique feature that could become its USP (Unique Selling Proposition). However, if the deadline is too restrictive, the team might skip additional research, testing or improvements just to deliver the product on time.
This could affect the originality, quality and competitive advantage of the final product.
My conclusion was that deadlines are not necessarily bad. Realistic deadlines and proper planning can improve productivity. However, excessive time pressure can limit creative exploration and affect the quality of the final outcome.
I found this discussion interesting because both sides had valid arguments.
5. Technical Evaluation
The technical evaluation focused mainly on three areas:
SQL
- SQL queries and database fundamentals.
- Joins and subqueries.
- Aggregate functions.
- Primary keys and foreign keys.
- Database concepts.
PL/SQL
- Difference between SQL and PL/SQL.
- Procedures and functions.
- Cursors and triggers.
- Exception handling.
- Basic PL/SQL programming concepts.
Object-Oriented Programming
- Classes and objects.
- Constructors.
- Inheritance.
- Polymorphism.
- Encapsulation.
- Abstraction.
For anyone preparing for the technical round, I would recommend revising SQL, PL/SQL and OOP thoroughly, particularly their practical applications and examples.
6. My Suggestions to Spaulding Ridge
I genuinely believe the recruitment process could become much better with a few improvements:
- Clearly communicate whether the opportunity is on-campus or off-campus.
- Share the complete selection process and elimination criteria in advance.
- Consider candidates' resumes, academic projects and relevant technical backgrounds.
- If conducting a GD, make it more business-oriented and relevant to consulting.
- Evaluate communication through practical business scenarios, teamwork and problem-solving rather than relying heavily on general topics.
- Clearly communicate stipend, working days, location and role expectations before candidates travel.
A combination of resume-based evaluation, technical assessments, business case discussions and communication assessments could provide a more complete picture of a candidate.
7. Final Thoughts
Despite my concerns about the hiring process, I genuinely liked Spaulding Ridge as an organisation.
The HR team, employees and staff members were welcoming, and the company environment made a very good impression on me.
I am not saying that the company is bad or that the hiring team had bad intentions. My feedback is specifically about the recruitment experience and how it could better reflect the actual requirements of a Consulting Intern position.
For future applicants, my advice is simple: prepare SQL, PL/SQL and OOP concepts, practise communication and business-oriented discussions, and clarify all job-related details before travelling.
Company impression: Positive. Recruitment experience: Room for improvement.
I hope this feedback helps future applicants and encourages a more structured and transparent hiring experience.
Would also like to hear from anyone who has previously attended Spaulding Ridge interviews. Was your GD experience similar, or did you have a different selection process?