Scandit logo

Scandit Interview Questions
& Process

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

Based on 62 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
58.1% Positive experience

Which role are you interviewing for?

30 roles · 62 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Scandit.

Showing 4 of 62
Scandit logo
Scandit

Product Marketing

Marketing · nearly a year ago

Senior Average Positive experience No offer 5 rounds
Interview process
Recruiter call Background check Take home Presentation
Interview formats
Behavioral Presentation Case

Started with an HR interview, then met with the hiring manager who is a senior product marketing leader, then talked to the head of product. After that, I had a take-home case study assignment. The final step was an interview to present the assignment, so they could check out my thinking and ability, and I could ask questions about the assignment.

Confirmed questions1 question
  • Can you tell me if you've created a feature requirement proposal previously?
Scandit logo
Scandit

Computer Vision Engineer

Engineering · a year ago

Mid Average Positive experience No offer 5 rounds
Interview process
Recruiter call Technical screen Panel Background check Offer
Interview formats
Technical Behavioral Coding System Design

Had an initial screening call that was a mix of technical and behavioral questions, mostly about my projects and motivation. Then there were 4 Panel interviews covering Python DSA coding, ML system design (more like applied ML), Backend system design, and a Hiring manager round. The recruiter managed it well and the interviewers were very friendly. Overall, it was a good experience.

Confirmed questions4 questions
  • Technical and Behavioural Qs on your CV, projects and motivation.
  • End-to-end system design.
  • DB schema.
Scandit logo
Scandit

Project Manager/Business Analyst

Product · more than a year ago

Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Recruiter call Offer
Interview formats
Behavioral

Scandit got in touch a few days after I applied and set up a call. I joined the call, but the recruiter wasn't there. After waiting about 7-8 minutes, I contacted HR. Around the 12-minute mark, the recruiter joined, stayed for a minute, and said the interview wasn't on his calendar, possibly due to a technical glitch. He asked to reschedule as he had another call. We rescheduled for the next day. I joined again and felt from the beginning that it was a forced call, especially since it took 8 minutes out of the scheduled 30. It felt rushed. We talked about my background (basically repeating my CV) and a bit about the role, but nothing in depth. I was told I'd get feedback the following Monday. I received a rejection Saturday morning, less than 12 hours after the second interview. My advice: if you don't think an applicant is a good fit, don't waste their time with a fake interview; just say no. If you mistakenly invited the wrong person, admit it, apologize, and cancel. These courtesy calls are just sad and disrespectful, especially to the applicant.

Confirmed questions4 questions
  • Hi, can you tell me about yourself?
  • Tell me about the background of the role.
  • What is your resume?
Scandit logo
Scandit

IOS Engineer

Engineering · more than a year ago

Entry Easy Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding Behavioral

HR reached out and after some back and forth via email, we set up a zoom call. The first interview was pretty chill, they went over the company's structure and vibe, plus gave an overview of the product, the job, and the tech stack. Then came the second interview, the first technical one, lasting about an hour. I totally bombed it, got too nervous and flustered, my mind just went blank. Seriously, try not to do that. It wasn't super tough, just some thinking about code for a hypothetical pull request, standard UIKit/Swift/iOS stuff. No crazy LeetCode problems or weird questions, just a realistic scenario and a couple of straightforward questions. The interviewer was cool and not uptight. A few days later, I got the rejection email, just as expected. It was generic, the typical 'we found someone else, don't take it personally, etc.' Honestly, I wasn't a fan of that. It felt disingenuous. Plus, I'm pretty sure they're still looking, so just be upfront, I can handle it. I mean, I wouldn't have hired me either, judging by that interview.

Confirmed questions3 questions
  • Can you review this Swift/UIKit pull request?
  • How do you handle multithreading with GCD?
  • Tell me about memory management in iOS.

Scandit Interview Questions

Quoted word for word from Scandit interview reports.

How can you count the number of set bits (1s) in the binary representation of an integer?

Read reports

Given a string, can you create a table showing cities and their populations?

Read reports

What would console.log(this) output in a browser environment?

Read reports

Can you explain the reasons behind Google's decision to develop Chrome?

Read reports

Consider an app where cells download images. How would you refactor it to move the image downloading logic out of the cell itself?

Read report

Considering the significant limitations of Swift, would you still opt for it if starting a new iOS project?

Read report

Could you explain the workings of a barcode scanning mobile application?

Read report

Formats, difficulty and experience

Across all 62 Scandit interview reports.

Interview formats

Behavioral 40.1%
Technical 23.4%
Presentation 18.2%
Coding 7.3%
Other 4.4%

Interview difficulty

Easy 11.3%
Average 66.1%
Difficult 22.6%

Candidate experience

Positive 58.1%
Neutral 14.5%
Negative 27.4%

Reports by job function

Sales 19
Engineering 18
Marketing 9
HR 9
Product 6
Legal 1