Imprint Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Imprint.
Imprint
Software Engineer
Entry Average Negative experience No offer 2 rounds
Interview process
Technical screen Phone screen
Interview formats
Technical Behavioral
I went through 2 rounds, one technical and one behavioral. I thought I did pretty well, but they rejected me the next day. I tried to get some feedback from the recruiter, but they ghosted me. The behavioral interviewer seemed inexperienced, like they were just reading from a document and weren't really interested.
Confirmed questions2 questions
- Code a weather app.
- Answered typical behavioral questions.
Imprint
Software Engineer
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
Software Engineer
Senior Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding System Design Presentation
Went through the usual interview cycle: Recruiter Screen, Tech Screen, and then an Onsite Panel. Honestly, the interviewers weren't great overall. The designer was the only one I enjoyed talking to. The technical interviews felt very impersonal and cold. The first tech screen involved rewriting some JS without much guidance, and the engineer seemed bored and uninterested in discussing solutions or requirements. The onsite panel was much of the same. They did try to make it less pressure by having me build an app alone for 90 minutes, but it felt more like a take-home assignment. The app was likely simple for experienced people, but I don't think that 90-minute window really shows if you can do the job. System design was similar. The design interview was the only one that felt normal.
Confirmed questions2 questions
- Could you rewrite this poorly written code in vanilla JS and HTML?
- Build an interactive game in React, and expect to be interrupted every 20 minutes.
Imprint Software Engineer 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 →“Build an interactive game in React, and expect to be interrupted every 20 minutes.”
Read reports →“Can you design a feature flag service or system?”
Read reports →“Could you create a functional React application from scratch and demonstrate it using a development server?”
Read report →Formats, difficulty and experience
Across all 6 Imprint interview reports.