La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Canonical
Colloquio
Too long, didn't read: a long interview process ending in an automated email from a no-reply address rejecting my application.
----
Step by step breakdown:
1) Application:
As you'd expect, a CV and cover letter
2) Email questions:
4 reasonably basic questions emailed to you that you have to answer.
3) Interview 1:
An introductory interview with a member of the web dev team. Just to talk about the next steps and stages.
4) Tests:
A personality and intelligence assessment. The intelligence assessment isn't like a typical IQ test or an 11+ that you would expect in the UK. The personality assessment is a Likert scale questionnaire asking how you would respond in certain situations.
5) Coding assessment:
A basic exercise to implement a UI element using their Vanilla framework. This included fetching some data from a JSON file they linked to.
6) Interview 2:
A technical interview with a panel of 3 people. I was asked questions that related to the job description, and some about activities stated in my CV.
7) Rejection:
An automated email from greenhouse.io stating that my application will not be processed further.
----
All in all, a process that should not be this long. From the second interview, I have found out that this is a new way of interviewing for multiple positions at once. Personally, I don't think this works as well as intended, as the initial job description has to be quite vague to cater to many different jobs. Especially if you only make a decision after step 6, which for me personally has been a month of back and forth emails/exercises.
Domande di colloquio [4]
Domanda 1
In your high school years or university, what have you achieved that you consider exceptional?
The recruitment process is excessively long and completely lacks human contact. Moving through numerous anonymous stages without a proper interview makes it impossible to evaluate the opportunity effectively. The company needs to introduce real interaction much earlier in their hiring pipeline.
Domande di colloquio [1]
Domanda 1
A high volume of basic school and college-level academic questions during the initial stage.
Written interview including high school performance. After that, I took an online assessment (coding) and a personality test. The recruiter sent me an email about arranging the first person-to-person interview. But after an hour, I received a rejection email.
Domande di colloquio [1]
Domanda 1
High school performance, working style, project experience
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Canonical
Colloquio
As we all know, the interview process can feel long from the moment you get that first email. I completed the text interview, the coding tests, and the problem-solving assessments 🤔. Interesting or not — you decide. The interviews with the team were pleasant; I guess it depends, but mine were 3/3 positive experiences. I didn’t get an offer, but I’m thinking of applying again in six months..
Domande di colloquio [1]
Domanda 1
To be honest, I thought it would be more like an architectural interview where I’d be drawing app structures on a whiteboard. But instead, it was more along the lines of: Tell me about your projects, your achievements, your goals. What would you do in this situation? Why do you use this instead of that? What would you do differently now?
