ISEE logo

ISEE 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

3.4 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at ISEE.

Showing 3 of 5
ISEE logo
ISEE

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding

It was about 5-6 rounds with the team members. You get to chat with them and they ask you questions. It was pretty standard, and everyone was really nice. I guess they probably get together afterwards to figure out if you're a good fit for what they need.

Confirmed questions2 questions
  • Questions about coding, and some low level system questions.
  • Questions on synchronization primitives and system functions.
ISEE logo
ISEE

Software Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Technical Behavioral

I applied for a robotics infrastructure role that needed C++/C and Python experience. Later, I got an email for a video interview, which I scheduled. During the video interview, the interviewer started asking frontend questions, and it turned out the role was actually for a frontend developer, not the robotics role I applied for. I had to ask what the position was near the end because they hadn't described it, and I was surprised. I mentioned I applied for a robotics role and this wasn't it. The interviewer was understanding and explained that the recruiting team often considers candidates for roles they didn't apply for based on their resumes, even if it's not a strong match. While I don't mind being considered for other roles, I do have an issue with the recruiting team not mentioning it was a frontend role in advance. I only found out when I asked the interviewer. The interviewer said they'd talk to the recruiting team about possibly considering me for the role I actually wanted. Two business days later, I received an email stating I wouldn't be moving forward. Such a waste of time.

Confirmed questions1 question
  • Can you share your experience with React?
ISEE logo
ISEE

Software Engineer

Engineering

Mid Average Positive experience Decline offer 4 rounds
Interview process
Phone screen Onsite Presentation Technical screen Group
Interview formats
Technical Coding Behavioral Other

It started with a phone call, and then I went onsite. At the onsite, I had a chat with the CEO, a technical round with an engineer from the planning team, and a coding interview. There were also some puzzle questions.

Confirmed questions2 questions
  • Tell me about building a planner for one of their use cases.
  • Can you solve some puzzle type questions?

ISEE Software Engineer Interview Questions

Quoted word for word from ISEE interview reports.

Questions on synchronization primitives and system functions.

Read reports

Questions about coding, and some low level system questions.

Read reports

Tell me about building a planner for one of their use cases.

Read report

Formats, difficulty and experience

Across all 5 ISEE interview reports.

Interview formats

Coding 38.5%
Technical 30.8%
Behavioral 15.4%
Other 15.4%

Interview difficulty

Easy 0%
Average 100%
Difficult 0%

Candidate experience

Positive 40%
Negative 60%