Shell Technology Centre Bangalore Interview Experience (On-Campus for Software Engineer)
Interview Experience
Shell Technology Centre Bangalore visited our college for recruiting Software Engineer. They conducted only two rounds:
Online round and Personal Interview.Total 60 studen...
Full Details
Shell Technology Centre Bangalore visited our college for recruiting Software Engineer. They conducted only two rounds:
Online round and Personal Interview. Total 60 students sit for the Online round from CS and IT only. First Round(Online) There were 3 sections in the online test namely verbal, logical and CS fundamental technical questions on AMCAT (Aspiring Minds). Logical was quite easy and good practice on GeeksforGeeks for verbal and technical question will help a lot. Technical questions were mainly on DBMS,OS and a few question on networking and OOPs.
Online round was adaptive, that is you cannot come back to a question again. There was no negative marking so better to attend all questions. Time limit was good around 1 minute per question so practice is needed a lot to complete all questions. Scoring more was key to selection. They selected top 20 candidates from the online round. Second Round(PI) This round was done on Skype. It was 45 minutes interview round that tests your technical cum managerial skills. They have 2 sections in the interview: 1 technical and another behavioral. They have a standard age old set of questions which they will not change. Besides the profile being a technical one but they judge you mostly on managerial skills. Technical knowledge weighs a little in the interview. They ask few technical definitions about 2 or 3 to each candidate and a 15 minutes discussion on your project. A project is a must so try to have a good project on your CV (Android Application Development, Machine Learning, Web Development, etc). Also an internship will help a lot. Second section was mostly HR round with all situation based questions- here your story-telling ability will help a lot. Prepare some stories related to your leadership, problem-solving, situation-handling skills, achievements and situation were you worked against your morals and all this kind of stuff (including event management, social-responsibility activities, etc)- the stories can be imaginary too but you need a lot of confidence and self-belief while answering. Try to communicate well, don't bother asking them a good number of questions but don't ask question regarding job profile and all(they don't like questions much regarding this) and express yourself well and also show eagerness towards the job and company. Try to be innovative and at the same time, enough communicative to let them understand your points. Shell have clear rules in recruiting people. Prepare to demonstrate yourself on the CART model. Capacity : via academic (GPA/test scores) and professional credentials (internships) Achievement : projects executed Relationships : team work,leadership,ethics Technical know how : related to the specific role you are applying Overall a good one but don't expect too much subject questions in interview process, its all about managerial skills. The results were announced 2 days later and 7 of 20 candidates were offered the job.
About This Question
This is a candidate experience report from a shell interview for a eng manager role (intern level) during the oa round reported in 2017.
It covers the following topics: Ml, Sql .
Difficulty rating: Easy
More Shell Interview Questions
About Shell Interview Reports
This question was reported by a candidate who interviewed at Shell. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Shell are the higher-signal extractions to take from this report.
For broader preparation context, the Shell interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Shell reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Shell Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Shell reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.