Slice logo

Slice Software Engineer Interview Questions
& Process

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

Based on 7 interview experiences · FREE TO READ

3.7 Rounds average
Average Typical difficulty
57.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Slice.

Showing 3 of 7
Slice logo
Slice

Senior Software Engineer

Engineering · more than a year ago

Senior Easy Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Background check
Interview formats
Coding System Design Behavioral

Recruiter called me first, then I had a coding round, followed by LLD and HLD rounds, and then a final HR round to check cultural fit. The HR person was super responsive throughout the whole thing.

Confirmed questions2 questions
  • Standard leetcode questions were asked
  • System design questions were asked
Slice logo
Slice

Software Engineer

Engineering

Entry Average Negative experience No offer 6 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Technical screen Phone screen
Interview formats
Behavioral Technical Coding

I went through 6 stages over the space of a month, the last stage being a call with the CTO which seemed like a pretty good sign. After all that, I was told the company had changed their hiring plan and that they would not be making an offer. The following is a direct quote from the rejection email: "I want to strongly highlight that our decision was not based on your performance at the interviews." Felt like a massive waste of time and energy. This is in no way targeted at the interviewers themselves who were all very nice.

Confirmed questions6 questions
  • Informal meeting
  • Call with senior engineer
  • Take home test
Slice logo
Slice

Software Engineer

Engineering

Mid Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Technical Coding Behavioral

First, I had a chat with the CTO about the company and its engineering teams and goals. Then, I got a take-home coding assignment. The actual interviews were separate, lasting about 4 hours. I spoke with various engineers and managers. The first interview involved reviewing the take-home exam and expanding on it. The remaining part of the interview was mostly behavioral.

Confirmed questions1 question
  • Could you add a REST API layer to the module you developed in the take-home exam?

Slice Software Engineer Interview Questions

Quoted word for word from Slice interview reports.

Could you add a REST API layer to the module you developed in the take-home exam?

Read reports

Regarding introducing new technologies and frameworks into the team's technical stack, what would be your evaluation and introduction process?

Read reports

What makes you the best choice for this role compared to others?

Read reports

Formats, difficulty and experience

Across all 7 Slice interview reports.

Interview formats

Behavioral 33.3%
Technical 28.6%
Coding 28.6%
Case 4.8%
System Design 4.8%

Interview difficulty

Easy 14.3%
Average 71.4%
Difficult 14.3%

Candidate experience

Positive 57.1%
Negative 28.6%
Neutral 14.3%