I applied through a recruiter. The process took 1 week. I interviewed at Parkopedia
Interview
A series of very specific questions about particular tech areas, including some red flags (what do you do if unit tests are taking 40 minutes) which perhaps give a clue as to the internal workings. No real questions about experience or interaction with answers except the usual "what was your biggest work challenge" at the end. Despite not getting the job it also feels like something of a lucky escape if all the hiring is done this way, as this kind of approach inevitably ends up with people who can explain what every acronym stands for while not actually being able to write decent code. Good luck!
Interview questions [1]
Question 1
What do you do if you need to run all tests during a CI/CD pipeline but they take 40 minutes to run?
A series of general software engineering questions focusing on OOP an data structures. Mainly knowledge based. Followed by a series of problem solving tasks on a whiteboard, time complexity and structuring of code. Friendly and enjoyable experience
Interview questions [1]
Question 1
- local private modifiers
- encapsulation
- polymorphism
- testing
- Writing a function to check if a series of lines form one continuous single branching polyline.