I had a short discussion with someone from the recruiting team.

There were two interviews with a couple of small, general software development questions, followed by algorithm problems similar to those found on LeetCode. After a first solution, the problems could be modified to adapt to new requirements.

One interview was of the "system design" type, where I talked about a system and described the necessary components and possible solutions.

There was also one interview with a manager, which was more of a chance to learn more about the Bolt team.

I interviewed with people from Romania and Estonia (I am based in Romania).

The programming language was the choice of the interviewee.

The process was enjoyable, and I had interesting discussions with the Bolt employees. The process was streamlined, and despite there being five calls, it didn't take more than three to four weeks to complete. I really liked the scheduler they have; it allowed the candidate to enter a calendar app and select their preferred slot directly. I hope this becomes the standard.

Overall, I invested a sufficient number of hours in the interview process, but in the end, there was no response. This was certainly disappointing and is the least amount of respect I would expect for a candidate who was interested in your company.

Yes, I can accept a rejection, and I probably wasn't that surprised, considering my background didn't match well with their technology stack. However, no explanation came after a couple of months.

What types of testing processes are used in process development?