Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      CobbleWeb

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur CobbleWeb | Offres d’emploi chez CobbleWeb | Salaires chez CobbleWeb | Avantages sociaux chez CobbleWeb
      Entretiens chez CobbleWebEntretiens d’embauche pour Senior Full Stack Engineer chez CobbleWebEntretien chez CobbleWeb


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Senior Full Stack Engineer

      5 juil. 2024
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez CobbleWeb en juin 2024

      Entretien

      I must express my disappointment with how CobbleWeb handled my application process. Over the span of three weeks, I went through six stages of interviews, dedicating significant time and effort, only to be informed at the end that the company is undergoing internal restructuring and requires a more senior developer. This is not only unprofessional but also highly disrespectful to candidates who invest their time and resources into the application process. To provide a detailed overview: 1. Initial Interview with HR: Discussed my previous experience (~45 mins). 2. Take-Home Task: Completed a task involving building a login/registration system with AWS services integration (~13 hrs). 3. Project Demo: Presented my project (~45 mins). 4. Technical and Non-Technical Interview: Spoke with the CTO and a Senior Engineer (~2 hrs). 5. Cultural Fit Interview: Discussed with the CEO (~1 hr). 6. Final Interview: Met with the CEO and a Senior Engineer to discuss previous experiences and provide optimization suggestions for a design (~1 hr). After these successful interviews, I waited for two days for an offer, only to receive an email stating, "We are going through some internal restructuring, splitting existing teams in a different way, and they believe we need a more senior developer for this specific role." This experience has been one of the most disappointing I’ve had as an applicant for a B2B contract. Furthermore, the compensation offered was not competitive, with a base salary of 45k GBP for a Senior B2B contract and a potential 10% increase contingent on interview performance. Regrettably, this experience has led me to decide against any future opportunities with CobbleWeb. I cannot recommend this company to other professionals, but if you have a lot of free time, feel free to proceed.

      Questions d'entretien [1]

      Question 1

      - JS beginner to advanced questions - CI/CD, github, AWS CDK - React, testing libraries
      Répondre à cette question
      5
      avatar
      Réponse de CobbleWeb
      1y
      Thanks for the feedback. We regret that you had a less-than-enjoyable experience during your recent interview process at CobbleWeb. However, after carefully examining your complaints, we have to clarify a number of inaccuracies and/or misunderstandings. First, and most important, the engineering position was clearly advertised as a senior role. This was reiterated during the interview process, since this role carries a high level of responsibility for project outcomes. Yes, we do have a rigorous recruitment process, which has proven to be the best way to establish if there is a good fit between CobbleWeb and a particular candidate. This is obviously to both parties' advantage. Nobody wants to start a new job only to discover it was not what they initially made it out to be. And we don’t want to set anyone up for failure by putting them in a role they are not equipped for. You provided a detailed breakdown of the interview steps and their apparent duration in your case. It is worth mentioning that candidates progress through these steps at different speeds. It may take longer, especially if a candidate excels in some aspects, but there are still question marks over other critical areas of experience and/or expertise. This is true in your case, as there were concerns whether you could make the jump from your mid-level engineering experience (which offers good technical skills) to a more senior role, which requires a high-level product focus and deeper understanding of business logic. We do concede that the technical take-home exercise was a bit time-consuming for some candidates. We have therefore replaced it with a shorter live technical interview. With regards to " internal restructuring" and "requiring a more senior developer": This was mentioned to you in the regret email to (1) explain that due to rapid growth there may be a future, more suitable, role for you with CobbleWeb, and (2) to reiterate the seniority requirement for the advertised role. You seem to have misinterpreted our message, but we do apologise if it was not clear enough. Finally, we pride ourselves on respecting candidates' time and effort by always keeping them in the loop. You admit as such when you refer to the detailed regret message you received. It is therefore disappointing that you decided to vent your frustration on Glassdoor, instead of accepting our offer of a meeting to discuss your concerns and clarify future opportunities with CobbleWeb. While we wish you well in your future endeavours, we are a bit sad that this issue was not dealt with in a more amicable, constructive (and dare we say, mature) manner. Hopefully some lessons have been learnt all around.

      Autres retours d’entretien d’embauche pour un poste comme Senior Full Stack Engineer chez CobbleWeb

      Entretien pour Senior Full Stack Engineer

      27 juin 2025
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez CobbleWeb

      Entretien

      From the very beginning, the interview felt completely off. The recruiter didn’t start with any kind of introduction — no explanation of their role, no overview of the company, and no effort to build rapport. Instead, they jumped straight into reviewing my resume and firing off questions like it was an interrogation. For a first call, this felt abrupt, cold, and unwelcoming. The lack of a proper introduction set a negative tone and made the interaction feel transactional rather than conversational. To make matters worse, the recruiter unexpectedly dove into technical questions — something that is typically reserved for later rounds with engineers. This was not communicated in advance, and it felt out of place for what should have been an initial screening focused on background, experience, and mutual fit. The 30-minute call was almost entirely one-sided. The recruiter asked questions for 28 minutes, leaving just two minutes at the end for me to ask anything — barely enough time for a meaningful exchange. As the first point of contact, a recruiter shapes the candidate’s perception of the company, and in this case, the experience was so poor that I decided to withdraw from the process altogether. I hope the company reconsiders how they approach initial interviews — especially if they care about candidate experience and attracting strong talent.

      Questions d'entretien [1]

      Question 1

      What are design patterns used for
      Répondre à cette question
      avatar
      Réponse de CobbleWeb
      11mo
      We regret that you did not enjoy your screening interview, but it does seem that you are trying to dictate how a company conducts its interviews? Just because a certain format worked for other companies, doesn't mean it will work for ours. Firstly, it is perfectly acceptable to ask some technical questions in the screening interview. They are a very necessary filter to gauge if a candidate qualifies for the more in-depth technical interview. In fact, if you took the time, you would have noticed that this is explicitly indicated in our recruitment FAQs: https://www.cobbleweb.co.uk/team/frequently-asked-questions-working-at-cobbleweb/#recruitment-process As for not being introduced properly, all our interviews follow the same structure and are recorded for quality purposes. They include a brief introduction to CobbleWeb and the opportunity to ask questions at the end of the interview. We don't book back-to-back meetings for this very reason, so that candidates have sufficient time to ask questions. In addition, our interview invite contains detailed information about the company: Company Focus | Clients | Tech Stack | Our Software Development Approach | Job roles You can also visit our dedicated Team portal to learn more about worklife at CobbleWeb. Aspects covered include: our product discovery process, your influence on technical decisions, and our recruitment steps. Candidates are of course welcome to email through queries, before or after the interview. In fact, we really appreciate those who do. Did you do so? It also needs to be noted that the purpose of our screening interview is to verify if a candidate ticks the minimum requirements boxes. That’s why we generally keep them short and sweet (30 minutes) so that no one's time gets wasted. Subsequent interviews (product and technical) are more appropriate for deep dives into specific aspects of the role and the company. We always welcome constructive feedback, but after careful review of the facts we do feel that this negative review has its roots in an unsuccessful candidate who is unwilling to accept their unsuitability for the role in question.