Shell software engineer candidates describe an online assessment or video screen, then technical interviews on C# and .NET, coding or design, and behavioral questions. Reports vary by team, level and year.
$138K
Avg. Base Comp
$160K
Avg. Total Comp
3-4 rounds
Typical Rounds
3-4 weeks
Process Length
Shell software engineer candidates describe a process that mixes technical depth with a lot of behavioral and project discussion. The reports don't follow one fixed sequence, so expect some variation by team and level.
One candidate who accepted an offer reported going straight into technical interviews with no HR round up front. The first round covered C# and .NET fundamentals. The second was harder, with a hands-on coding component. A scenario asked whether a property of a read-only dependency could be modified inside a method, and whether the compiler would complain. It tests the difference between reassigning a reference and mutating the object it points to. That candidate put the whole process at about four weeks.
Another candidate, who did not get an offer, reported an online test with a coding problem. It asked for time and space complexity and test cases. Two panel interviews followed, centered on projects, strengths and fit. One round included designing a logger rate limiter. The candidate said interviewers cared more about approach and communication than about grinding algorithm problems.
A software engineer who received an offer described a technical interview that covered a resume review, coding, system design and behavioral questions, plus a project presentation. That candidate also reported weeks passing without updates. A senior candidate described a two-day virtual on-site with four back-to-back rounds, covering behavioral, system design, cloud architecture and coding. That candidate reported that recruiter communication stopped afterward.
One engineer-titled report and one graduate report describe asynchronous video interviews and a behavioral assessment. Prompts included "tell us about yourself", disagreements with teammates, and motivation for Shell. To prepare, review C# and .NET reference semantics, practice a rate-limiter design with trade-offs, and prepare two or three honest project walkthroughs. Also prepare a conflict story and a specific answer to why Shell.
Synthesized from 6 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Shell process.
I applied online and entered Shell's interview pipeline, which kicked off with an initial screening and then moved into their on-demand video interview format. This was different from a live conversation — I recorded multiple video responses to standard prompts, and I could retake them if I wasn't happy with my first attempt. Questions were broad and behavioral: "Tell us about yourself" and similar open-ended prompts designed to get a sense of your background and motivation.
After the video assessment phase, they sent me an insight — feedback or an update on where I stood in the process. The overall structure felt systematic and standardized, which made sense for a large organization managing many candidates. It wasn't high-pressure, but it also meant there was little room for personality or real-time connection with an interviewer. You were essentially performing for a camera, which takes some getting used to. I made sure to be clear and concise in my responses since there's no back-and-forth to clarify what you meant.
Prep tip from this candidate
Practice concise, compelling "tell me about yourself" answers for asynchronous video format — you won't get follow-up questions to recover, so be specific about your impact and motivation from the first take. Shell uses this ODVI format for initial screening, so treat multiple takes as an advantage and refine your answer each time.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Shell
How would you answer when an Interviewer asks why you applied to their company?
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Size of Joins | |
| Prime to N | |
| Retailer Data Warehouse | |
| Hurdles In Data Projects | |
| Bagging vs Boosting | |
| The Brackets Problem | |
| Real-Time Transaction Streaming | |
| Flatten N-Dimensional Array to 1D Array | |
| Nearest Common Ancestor | |
| Append Frequency | |
| Sort Strings | |
| Total Time in Flight | |
| Find Duplicate Numbers in a List | |
| Success Measurement | |
| Digit Accumulator | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Multi-Reaction | |
| Time Difference | |
| RAG Strict Source Control | |
| Walking Robot | |
| Concurrent LLM Serving | |
| Worker Distribution Dilemma | |
| Log Anomaly Detection Model | |
| Data Pipelines and Aggregation | |
| Legacy System Heartbeat Monitor | |
| Mapping Nicknames |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different openers. One described an online test with a coding problem, complexity analysis and test cases. Others described a behavioral assessment or on-demand video interviews with retakes. Which one you get may depend on the team and level, so prepare for both formats.
One candidate who accepted an offer went straight into technical interviews and reports that the first round focused on explaining C# and .NET fundamentals clearly. The questions were described as fair rather than tricky. Other teams may use different stacks, so confirm the language focus with your recruiter.
Candidates report harder technical rounds with hands-on work. One had a roughly hour-long Teams session on mutability and reference types in C#. Another was asked to design a logger rate limiter. A third described coding plus system design. Expect to explain your reasoning aloud as you work.
Behavioral questions appear across the reports. Candidates mention conflict with teammates, pushing through a difficult challenge, strengths, why Shell, and walking through past projects. One said interviewers could tell when stories were fabricated, so specific and honest examples are likely to serve you best.
One senior candidate reported a two-day virtual on-site with four panel rounds: behavioral, system design, cloud architecture and coding. This is a single report and may not apply to non-senior roles. Two candidates also described slow or absent communication after interviews, so you may want to follow up proactively.
