Imprint logo

Imprint Interview Questions
& Process

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

Based on 14 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
21.4% Positive experience

Which role are you interviewing for?

8 roles · 14 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Imprint.

Showing 4 of 14
Imprint logo
Imprint

Team Lead

Engineering · a year ago

Lead Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Behavioral Technical

I interviewed for this Team Lead role in Winter 2024 and again the following fall. The first interview seemed to go well, but I got an automated rejection with no feedback. The second time, they seemed really impressed and almost offered me the job after the final interview, saying I'd hear back that day. Three weeks went by, and I heard nothing even after reaching out. Finally, I was told they had restructuring and weren't filling the role, possibly any roles soon. It would have been nice to know instead of being ghosted for 3 weeks; the company seems disorganized. The interviewers from the first time weren't even there anymore, and they had no record of my prior interview for the same role.

Confirmed questions1 question
  • How do you manage difficult customer situations?
Imprint logo
Imprint

Software Engineer

Engineering · a year ago

Mid Average Negative experience No offer 1 round
Interview process
Onsite Offer
Interview formats
Coding Technical

So, one of the onsite interview sessions was actually 90 minutes long, way longer than a typical technical session. They asked me to build a complete, working React app for a basic game from the ground up. I was pretty surprised because I'd never had an interview where they expected you to actually build a running application in one session. I mean, I know React, but I wasn't ready to create a fully functional app on the spot. I got most of it working by the end, but couldn't quite fix some UI update issues, which is why I didn't get an offer. Honestly, it's a weird way to interview and not a reliable way to judge someone's skills. If we had just talked about my strategy using pseudocode or high-level design, I would've aced it because the actual problem wasn't that hard. But having to set up npm, create the project, delete default stuff, and run the server all took up time.

Confirmed questions1 question
  • Could you create a functional React application from scratch and demonstrate it using a development server?
Imprint logo
Imprint

Staff Software Engineer

Engineering

Staff Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Presentation
Interview formats
Technical Coding System Design Presentation

The interview process was pretty standard: Recruiter Screen, Technical Screen, Virtual On-Site with Code/System Design/Product Design sessions, and finally an Interview with the CEO. For me, the whole thing was super smooth and wrapped up in just two weeks. I really liked the lead recruiter, and the process overall went really well. Everyone was on time, knew their stuff, asked good questions, and set them up nicely. Some of the tech questions were tough, but that's what I expected for this role. I appreciated that they looked at the whole picture; weaker areas were balanced out by stronger ones. However, doing well on the coding parts is still a big deal.

Confirmed questions4 questions
  • Can you diagram and explain a real-time transaction processing system?
  • How would transactions be brought into the system?
  • What components would be used for ledgering or risk assessments of transactions?
Imprint logo
Imprint

UX Designer

Design

Senior Difficult Negative experience No offer 6 rounds
Interview process
Recruiter call Technical screen Onsite Panel Group Presentation
Interview formats
Technical Behavioral Presentation

This company's interview process was really weird. I had 6 interviews in total, but I never once spoke to another designer. All my interviewers were from engineering and new to the company. One interviewer was actually looking up answers online while we talked. They also asked about 25+ project management questions in every single interview. It felt like they had already chosen someone and were just interviewing me to waste my time. Super strange and honestly pretty dumb.

Confirmed questions1 question
  • What methodology do you use to ensure your designs are user-centric?

Imprint Interview Questions

Quoted word for word from Imprint interview reports.

Could you rewrite this poorly written code in vanilla JS and HTML?

Read reports

Could you build a basic React component that displays a list of books?

Read reports

What components would be used for ledgering or risk assessments of transactions?

Read reports

Can you diagram and explain a real-time transaction processing system?

Read report

Build an interactive game in React, and expect to be interrupted every 20 minutes.

Read report

Could you create a functional React application from scratch and demonstrate it using a development server?

Read report

How would you approach scaling and ensuring resilience for this system?

Read report

Formats, difficulty and experience

Across all 14 Imprint interview reports.

Interview formats

Behavioral 27.3%
Technical 27.3%
Coding 18.2%
System Design 15.2%
Presentation 12.1%

Interview difficulty

Easy 7.1%
Average 71.4%
Difficult 21.4%

Candidate experience

Negative 64.3%
Neutral 14.3%
Positive 21.4%

Reports by job function

Engineering 8
Other 2
Design 2
Product 1
Marketing 1