I applied online. The process took 2 weeks. I interviewed at The Plum Guide in Aug 2021
Interview
First I had an interview with technical person who described me how PlumGuide works and how teams are organized. Next I got pointless code test to solve – the recommended time was 2 hours, but there was a lot of business logic to implement and besides that, TDD approach was required and a lot of other quality requirements.
I sent the solution and got no feedback from them for a week. I had to ask the recruiter what's the status and they never contacted me again. Finally got answer from recruiter - they just said "no" without reason.
To be honest it's the worst interview I've ever had - not recommend, waste of time.
Interview questions [1]
Question 1
1. What tools from the requirements list you've worked with?
2. The pointless code test to solve
I applied online. The process took 1 week. I interviewed at The Plum Guide (London, England) in July 2019
Interview
Very smooth - had a face to face technical interview, followed by a 'culture' interview. An offer was made quickly which was important as a I was considering another offer at the time. All stages were enjoyable, and were instrumental in myself accepting the offer.
Interview questions [1]
Question 1
How would you approach building the listings home page
I applied through a recruiter. The process took 3 days. I interviewed at The Plum Guide (London, England) in July 2019
Interview
I will list it in the order of steps:
1) A recruiter reached out to me and introduced The Plum Guide.
2) We arranged a face-to-face interview towards the end of the day so that I could attend after finishing work. They were perfectly happy with me coming in jeans and a t-shirt.
3) I went for an interview around 5 pm on a Thursday, where I was greeted at the door and offered a hot drink and a toastie. The Plum Guide have smoothie Tuesday and toastie Thursdays. Also, I was given a quick tour of the office.
4) I sat down in a meeting room together with two developers from the team I would most likely work in. They had a laptop between them and a few blank pieces of paper.
5) The interview itself was unique, as it genuinely felt like a friendly discussion between three developers who are passionate about technology. There were no algorithmic questions, no trick-questions - just questions about various problems and what could be done to solve them. Whenever I didn't have an answer or was missing something, the interviewers would help me out by pitching in and gently pushing me in the right direction. If memory serves me right, after about an hour and a half I was given the option to stop and move onto the next phase, or spend a few more minutes discussing the topics - I chose to speak a bit longer as I was very invested int he conversation.
6) After the technical interview came the cultural interview, where I sat down with another developer from the team and the lead UX designer. They talked to me about the things I liked, what I valued in a company, what I was looking for and other cultural elements.
7) Then the CTO came for a quick chat, and we just had a quick conversation and such. At this point, the CTO was already aware of what everyone else thought of me, so this part was very brief, as it was getting late, and everyone wanted to go home. Also, we discussed a salary during this.
8) The next day, or even the same evening, the messaged me saying that The Plum Guide would love to have me on board and would like to extend me an offer.
9) And that's the whole interview process.
Interview questions [1]
Question 1
They showed me the website and explained how it works, as well as some of the challenges they faced. Most of the questions were around how I would approach these problems.