CobbleWeb interview questions

Thank you for the feedback. However, the role you interviewed for was Senior Software Engineer, which requires a certain level of product thinking - developing products that solve real user problems and achieve business goals. This is clearly indicated in both the job ad and our breakdown of the CobbleWeb recruitment process: https://www.cobbleweb.co.uk/team/cracking-the-code-inside-cobblewebs-recruitment-process/ Our team blog also consistently emphasises the requirements for close collaboration and product thinking in our engineering teams: https://www.cobbleweb.co.uk/team/ Here's one salient excerpt: "Unlike many software development agencies that focus solely on technical performance, we encourage our engineers to explore the broader business implications of their work. This product-led mindset has proven to be a powerful catalyst for innovation, successful project outcomes, and job satisfaction" It's important to understand that we are not a code factory that don't care about our clients' success. As such we expect everyone to consider the big picture: how their work affects the end results.

Thank you for your feedback. Good or bad, it helps us refine our recruitment processes to the benefit of all. First and foremost, we have to apologise for the perceived lack of attention in your final interview. The CTO suddenly had to deal with an urgent matter, but that should not be your problem. It is important to us that every candidate is treated with kindness and respect. Now let's dig into the nitty-gritty of your dissatisfaction, because there seems to be confusion on a few points. CobbleWeb is a product development company, not a code factory, which is why candidates should have a firm grasp of the product development process. Our job ads specifically mention that you need (1) to understand how your work impacts end users and business goals and (2) a strong ability to collaborate within cross-functional teams. In particular, that means having a solid grasp of the discovery, functional requirements, and technical specifications steps. By taking offence at being quizzed on this critical skill set, you are basically asking us to put our company and our clients' projects at extreme risk. Could it be that the interview felt "uncomfortable and confrontational" because you felt out of your depth? Unfortunately this sometimes happens, but nonetheless we cannot dilute the rigour of our product interviews. Our company simply cannot take that risk. It is unfortunate that you felt that the atmosphere was "cold and disconnected", but you do come across a tad oversensitive. For the record, your take contradicts our team members' and the vast majority of candidates' feedback. According to the product interview team, you were given ample opportunity to ask questions at the end of the interview. You could also have emailed us any lingering questions. Frankly, it would be contrary to our recruitment priorities not to welcome questions, since they tend to indicate a real interest in our work. Finally, we apologise that you feel that you didn't get sufficient feedback at the end of the interview process. You are welcome to pop us an email for further clarification.