One of the onsite interview sessions lasted for 90 minutes, much longer than a typical technical session. I was asked to implement a fully functional app in React from scratch of a basic game with basic rules. This caught me by surprise, as I'd never seen an interview that actually asks you to build a running application within the timespan of a single session before this or since.
I have experience in React but was not prepared to make a fully functional application. By the end of the session, I had it mostly up and running but wasn't quite able to resolve some UI update issues. For this reason, I didn't receive an offer.
There are good reasons why this isn't an industry standard for interviewing. Running code in an interview isn't a reliable way of gauging a candidate's experience. Had we discussed my strategy via pseudocode and high level design, I would have passed this with ease, as the problem itself wasn't complex, but the requirement to execute the app caused delays in setting up npm tooling, creating the package from scratch or via create-react-app, clearing out the default contents, running a development server, etc.
You need to create a functioning React app from scratch and demo it via a development server.
The following metrics were computed from 4 interview experiences for the Imprint Software Engineer role in United States.
Imprint's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very negative feelings for Imprint's Software Engineer interview process in United States.