Shell Recharge Solutions logo

Shell Recharge Solutions Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 36 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
50% Positive experience

Which role are you interviewing for?

23 roles · 36 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Shell Recharge Solutions.

Showing 4 of 36
Shell Recharge Solutions logo
Shell Recharge Solutions

QA Lead

Engineering · nearly a year ago

Lead Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Behavioral Technical Coding

the first round was virtual, the interviewers and HRs were really polite. I was eager to join this company because it's my dream company, mainly because of its brand name and the bi-weekly Friday off.

Confirmed questions7 questions
  • What are your thoughts on test planning?
  • Can you tell me about challenges you've faced during automation?
  • How did you overcome those challenges?
Shell Recharge Solutions logo
Shell Recharge Solutions

Senior Software Engineer

Engineering · a year ago

Senior Average Positive experience No offer 5 rounds
Interview process
Take home Technical screen Technical screen Onsite Onsite
Interview formats
Coding Technical System Design Behavioral

The interview process started with a HackerRank Test focusing on REST API using Java. Then there were two technical rounds. The first technical round covered basic questions on Java Spring Boot. The second technical round, with the manager, involved discussions about the project, system design, event-driven architecture, and technologies like Kafka. Following that, a behavioral round assessed company fit through scenario-based questions. The final round was with the Director and included one system design question about an inventory service.

Confirmed questions1 question
  • Asked basic questions on Java spring boot
Shell Recharge Solutions logo
Shell Recharge Solutions

SRE Engineer

Engineering · a year ago

Mid Difficult Positive experience Decline offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Technical Coding System Design

The interview process kicked off with an HR contact, and they took about 3 to 4 days to set up my first interview with the hiring manager. After that interview, another 3 to 4 days passed before they scheduled my first round of interviews with two people on an interviewing panel. They hit me with SRT questions about design architecture and debugging monitoring. They also threw in a Java question which I'll share below.

Confirmed questions1 question
  • We have a class called Bar which takes an object of type Foo as a dependency. This dependency is declared within the Bar class as read-only or final. Q3: If I write a method called "DoSomething" and its job is to replace the value of a property of Foo. Will I get a compiler exception, am I even able to do this? Provide visual of code below as part of the question public class Bar ( private read-only Foo foo; public Bar(Foo foo) { this.foo = foo; } public void DoSomething € foo sample = "new value"; } !.. var bar = new Bar(new Foo0); bar.DoSomethingO;
Shell Recharge Solutions logo
Shell Recharge Solutions

Director of Sales

Sales · more than a year ago

Director Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Case

Started off with a really energetic and great chat. The recruiter laid out the whole plan, including target dates, saying it would be about a 3-week process. The second interview was set for about a week and a half later. That one seemed to go well, and I got told I was moving on. Then, a week passed before the next interview. That one also went fine, and again, I was told I was advancing. So, at this point, 3 weeks had gone by, which was the total time they originally said the process would take. I followed up twice a week for the next two weeks about what was next and kept hearing they were still working on it. After another week (so, 3 weeks after the third interview, and 6 and a half weeks total), I sent an email to pull out of the running. I decided to do this, not because I got another offer, but because if this is how they handle their time during the interview process (when they're supposed to be making a good impression), I can't even imagine how they treat their actual customers.

Confirmed questions5 questions
  • Can you share an example of a challenging customer interaction and how you resolved it?
  • Describe a time you had to close a sale quickly under pressure. What was your approach?
  • What's your strategy for entering and developing a new market segment for our product?

Shell Recharge Solutions Interview Questions

Quoted word for word from Shell Recharge Solutions interview reports.

How would you write code to remove duplicates from an array in Java?

Read reports

We have a class called Bar which takes an object of type Foo as a dependency. This dependency is declared within the Bar class as read-only or final. Q3: If I write a method called "DoSomething" and its job is to replace the value of a property of Foo. Will I get a compiler exception, am I even able to do this? Provide visual of code below as part of the question public class Bar ( private read-only Foo foo; public Bar(Foo foo) { this.foo = foo; } public void DoSomething € foo sample = "new value"; } !.. var bar = new Bar(new Foo0); bar.DoSomethingO;

Read reports

Can you write code to load Google and fetch search results?

Read report

Given that I'll be moving after Covid, can my offer reflect a remote full-time role?

Read report

Formats, difficulty and experience

Across all 36 Shell Recharge Solutions interview reports.

Interview formats

Behavioral 38.6%
Technical 34.3%
Coding 12.9%
System Design 4.3%
Other 4.3%

Interview difficulty

Easy 16.7%
Average 72.2%
Difficult 11.1%

Candidate experience

Positive 50%
Neutral 8.3%
Negative 41.7%

Reports by job function

Engineering 17
Operations 6
Analytics 2
Product 2
Marketing 2
Sales 2