Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en MWR InfoSecurity (Londres, Inglaterra) en abr 2019
Entrevista
30 minute phone call, just to get to know me. Then they scheduled a phone call for a technical challenge. They called me on the phone and asked me to go to a shared URL for a coding challenge. So far during both interviews I have been asked really basic technical questions, such as why I like to use Go or Python. Nothing to determine my experience.
During the code challenge I was asked to write an algorithm to determine how many permutations of coins can go into £2. That's it. That is the only question. Not how I've written scalable software, CI/CD pipelines. Nothing about my several years experience. Just that. Then their feedback was I'm not experiened enough and I'm not a fit currently.
They determined who they hire entirely on if I knew this 1 algorithm. What was beautiful is that I was to write it in Python, and the interviewer did NOT know the answer, he had to copy and paste an answer that someone had created for him in C#.
Bit irritated at the state of the interview really. I read a lot of bad ones about this place that I now understand.
Preguntas de entrevista [1]
Pregunta 1
Print every coin less than £2 that can be added together to create £2. Thats it. That is the only technical question I got.
Envié una solicitud electrónica. El proceso duró 1 día. Acudí a una entrevista en MWR InfoSecurity (Londres, Inglaterra) en dic 2016
Entrevista
Questions typically concerned information security. I had already answered a few questions on InfoSec in an email and was asked to expand on some of these in the phone interview. There were no questions about algorithms, just parts of InfoSec I found interesting. The feedback given was that I should have shown more of an interest in InfoSec by understanding how some of the things I talked about worked in detail.
Preguntas de entrevista [1]
Pregunta 1
How might someone get ahold of a company's set of user data?
Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en MWR InfoSecurity (Basingstoke, England) en may 2016
Entrevista
I applied for a role in the Basingstoke office via a recruitment company a month or so ago.
The first round interview was completed via telephone which the recruitment company detailed would last around 30 minutes. The person called 10 minutes late and asked a host of questions regarding my technical ability; sort of on-the-spot technical questions. This I expected given the technical role applied for and I was given a quick outline of the job role.
A week later I was informed by the recruiter that I had progressed to the next stage - a technical test. This involved a fairly straightforward technical exercise which I completed within the time given and matched exactly the specification they gave. This I sent off and within a couple of days was invited by the recruiter to a face-to-face interview. I was surprised at this stage to have not received any feedback on the technical test, but thought I'd at least give the interview a go.
The recruiter explained that the face to face interview would last a couple of hours and would involve learning more about the role, the company and the people I would be working with - standard interview stuff. This was absolutely NOT what happened.
Upon arrival I was given an IQ test, followed by an hour long technical test. Then, I was grilled about the technical test I had just sat plus the technical test I had completed prior to the interview. I was bombarded with question after question sat in a small hot meeting room for the entire time. Just for added encouragement in the adjoining room a manager was shouting loudly at a team for their work.
The process lasted just shy of 3 hours and at no point was any explanation given about what the job entails, the company history, what the organisation structure is or anything that might help me understand whether the job was right for me. Neither did they ask about my history, experience or skills that I could bring to the role. This, with the combination of the IQ test and technical test, led me to the conclusion they're after robots to write their code
After this I was shown around the office and invited to "meet the team" hunched over desks in small bench desk setups. This seemed odd - I had literally no idea what they did there. Finally, just as I was about to leave I was asked if I had any questions. To be honest by this point I'd already decided that they appeared to not place any value on their staff and this was not the place for me to work.
Once I'd left the office I gave the recruiter a call and informed them I wasn't interested in the job regardless of a job offer from them. In hindsight I wish I'd read the other review on Glassdoor from April as it is wholly accurate and I would have saved myself wasting a morning.