Standard process of recruiter call, tech screen, and onsite. I had a recruiter reach out to me about interviewing here. This isn't really the type of product I wanted to work on, but a conversation never hurts. Usually. This one felt a little awkward. And when I was told at the end that they would need references, I kind of chuckled to myself. When is the last time anyone asked you for references? The tech screen was also awkward. It just seemed like the person I spoke with wasn't that practiced at conducting interviews. I get that sometimes with smaller companies. This definitely wasn't a case where good fundamentals would matter.
It was a simple problem, and if you knew the latest features of React, and the setup they were using for the interview, this would be a breeze. If you're used to using another framework, even if you can implement what they asked for, you're going to get turned away. Definitely not how I like to conduct interviews, but to each their own. My advice to anyone applying would be to familiarize yourself with CodeSandbox, and the latest features of React.
Implement a function to determine if a string is a pangram, with a simple UI.
Display any characters that are missing from the string.
The following metrics were computed from 8 interview experiences for the Iterable Software Engineer role in United States.
Iterable's interview process for their Software Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having good feelings for Iterable's Software Engineer interview process in United States.