OnShift logo

OnShift Software Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at OnShift.

Showing 3 of 5
OnShift logo
OnShift

Software Developer

Engineering · more than a year ago

Entry Difficult Positive experience Accept offer 2 rounds
Interview process
Phone screen Onsite Offer
Interview formats
Technical Coding

I had an hour long phone interview and then an on-site that lasted about four hours. The people in the interview were very friendly and direct with feedback. The technical interview was done for general competency. The solutions are coded in the candidate's language of choice! Afterwards, the status of my application and eventually the offer were clearly communicated.

Confirmed questions2 questions
  • Could you solve FizzBuzz?
  • Can you reverse a string?
OnShift logo
OnShift

Software Engineer

Engineering

Senior Average Negative experience No offer 1 round
Interview process
Recruiter call Onsite
Interview formats
Behavioral Technical

I was contacted by a recruiter about a local company doing new "greenfield" development and offering good pay. I agreed to an interview, which was scheduled quickly. I went downtown for the interview, which was a bit of an interesting location. I met with 4 people, and there was supposed to be another interview afterwards. They asked a lot of questions, and I asked my own. It turned out not all the work was new development; there was also old script code to maintain. We chatted, and then suddenly the interview ended. The next person was unavailable, and I was dismissed abruptly. It was a very unprofessional experience. I never heard back from them or the recruiter. It seemed like they were focused on phones and laptops, with signals and expressions behind their backs, similar to what someone else reported. Maybe I seemed discouraged when I heard about the actual position, or maybe they realized I was older than a "greenie" despite my experience. It would have been nice to be told if there was an issue. I wasn't too disappointed because the reality of the job didn't match the recruiter's description. It was kind of funny to be dismissed so quickly and unprofessionally. The recruiter sold the company as the next big tech name in Cleveland, which hasn't really happened yet. I think they need to find some real professionals to conduct their interviews.

Confirmed questions1 question
  • What prompted your desire to leave your current job?
OnShift logo
OnShift

Software Developer

Engineering

Mid Average Positive experience No offer 5 rounds
Interview process
Recruiter call Phone screen Onsite Group
Interview formats
Behavioral Technical Group

The hiring process was pretty good, though there were long gaps between communications. I had 2 phone interviews, one with HR and another with a developer, and then 3 group interviews onsite with devs from different teams.

Confirmed questions1 question
  • How would you approach specific challenges?

OnShift Software Engineer Interview Questions

Quoted word for word from OnShift interview reports.

Formats, difficulty and experience

Across all 5 OnShift interview reports.

Interview formats

Behavioral 36.4%
Technical 36.4%
Coding 18.2%
Group 9.1%

Interview difficulty

Easy 0%
Average 80%
Difficult 20%

Candidate experience

Negative 60%
Positive 40%