I applied for a software engineering position and received an interview invitation about five days later. The first round was a 30-minute technical screening.
One slightly unusual thing was that the interview was scheduled for 2:05 PM instead of a typical interview time, and the interviewer joined about five minutes late. We started with a brief introduction, followed by several API focused questions. I was asked what APIs I would design for a system and discussed common operations such as GET, POST, PATCH, and update-related APIs. I was also asked about database indexing, how indexes can improve database performance, and the pros and cons of using indexes.
The interview itself was fairly straightforward, and I felt comfortable with my answers. Afterward, I asked a few questions about the role and team. I received a rejection email the following Monday.
Overall, the experience felt a little unusual because the technical portion seemed to go well, but I was not moved to the next round and got a rejection email the next day. It is possible I didn't demonstrate enough enthusiasm during the conversation, as I was somewhat tired that day and probably could have been more engaged. Still, I would have appreciated more feedback about the decision.
The following metrics were computed from 3 interview experiences for the Mintlify Software Engineer role in United States.
Mintlify'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 very good feelings for Mintlify's Software Engineer interview process in United States.