Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Barclays (Glasgow, Scozia) nel mese di giu 2022
Colloquio
Joined a call with a "Vice president" developer. Didnt ask any personal or CV questions which i thought was strange as I was told this was the initial non technical interview. The guy interviewing me had his camera off the whole time, was a bit awkward and didnt show any great interest in me as a person. The person interviewing me kind of ambushed me by giving me a random coding problem which i wasnt told to prepare for. Moreover, they asked me to write the solution in notepad without any help from google and asked me to share my screen and keep my camera on so "I wasnt cheating". Albeit I flunked this spot test, and yeah, I had gaps in my knowledge and in hindsight, this company probably wasnt for me. But Its 2022/23, are we really expecting every developer to know every single javascript method from scratch ? Are you really expecting every developer working for your company to never look up how to do certain things? Is googling a random javascript coding problem 5 min before an interview, epecting the interviewee to do it in 10 min, giving 1 sentence answers to my questions, asking no questions about my CV and not even having the respect to show your face on camera when I have taken time out of my day to attend this interview a good way to screen candidates? Really felt like a "gotcha" interview and that i was there to stroke the interviewers ego more than anything.
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Barclays (Londra, Inghilterra) nel mese di nov 2025
Colloquio
My second-stage interview for a UI Developer (JavaScript/React) role was quite different from what I expected. The session focused almost entirely on CSS, with questions that were extremely detailed. Some of the terms were things I heard for the first time, and I’m honestly not sure how reasonable it is to expect candidates to recall such terminology on the spot.
CSS is of course important in frontend development, but the level of detail in the questions felt excessive for an interview. I’m not sure how well this kind of deep theoretical questioning reflects the practical requirements of the actual role.
Additionally, I remember the interviewer mentioning that their background was in a different area; at that moment, due to the stress, I couldn’t hear clearly and felt somewhat disconnected. I’m not sure whether this may have influenced the level or direction of the questions. Overall, the experience was disappointing for me.
I haven’t received any feedback yet, so I’m not sure if I should even be writing this now, but honestly I’m feeling pretty down at the moment. 😟
Let’s say you have a React component that you are currently using in one application. You now want to reuse the same component in another application. How would you structure this so that the component can be shared and used across multiple apps?
This is another interview question that was clearly very clear in the interviewer’s mind, but came out quite vague verbally. However, it’s possible to guess what they were trying to ask.”
Suppose you have a page in React where you render a list of cards. The data comes from an API, and each card has different content, so their heights will naturally vary. Each card is a reusable component. How would you structure this and handle the fact that each card may have a different height?
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Barclays
Colloquio
First I applied online and then profile was shortlisted after 3 months. First round was Technical round through WebEx and they have asked basic questions of Java script, CSS , and, HTML.
Domande di colloquio [1]
Domanda 1
Basic JS /HTML /CSS Questions and Output Questions
