Dwelo Interview Questions
& Process

It kicked off with a recruiter chat, covering my previous work, systems I've used (they're on Salesforce), and my reasons for wanting a change. Then there was a second chat with the Head of the team. She seemed to be looking for ways to make the most of the interview time after asking her initial questions. But honestly, both the recruiter and the team lead were pretty chill.

I had an initial chat with a recruiter which was pretty standard, asking about my work history. Then I had a second interview with someone from the department, but it wasn't the hiring manager, which I thought was kinda weird. He seemed really uncomfortable and just read from a script the whole time. He went through my resume, asking the same questions for each past job: 'What were you hired to do?', 'What are you most proud of?', 'What was the hardest part?', 'What would your boss say was your greatest strength?', 'What would they say was your greatest weakness?', and 'Why did you leave?'. We spent way too much time on jobs from over 10 years ago, and I barely got to talk about my current relevant experience. The next day, I got a rejection email from the recruiter. I asked for feedback but never heard back. The interview felt poorly done, and since the interviewer seemed inexperienced, I don't think I got a fair shot.

I was referred to Dwelo by a friend and had two separate interviews for this position. I was ghosted and didn't get responses to my follow ups. Months later, they reached out again and asked if I was still interested. I interviewed again and was ghosted, with no responses to my follow ups. Recruiters, please get back to people with a rejection. That is your job.

My interview process might have been a bit different from usual. I initially connected with someone who worked there, and they and their manager approached me over lunch to discuss my fit with the team and current challenges. After that, I chatted with an HR representative about benefits and insurance. This was followed by a 3 to 3.5 hour in-person interview, which included a technical interview with some basic whiteboarding. Later, I had an online meeting with their CTO. They then took me out to lunch, and concluded with a meeting with one of the developers. Many of the questions focused on general competence and cultural alignment. The SET1 title is considered their junior-level position, which felt appropriate. They were very communicative throughout the entire process, even reaching out before the role was officially posted, and there was a waiting period.