I applied online. The process took 2 weeks. I interviewed at Ferocia (Melbourne) in Sep 2024
Interview
The application process was impressively swift. From submission to receiving feedback, it took less than two weeks. The entire experience was positive, and the staff were incredibly friendly. The interview questions were not overly technical, allowing for a more personal connection. I appreciated the interviewer's empathy in calling to explain why I wasn't selected. It seems like a great company to work for.
Interview questions [1]
Question 1
Why are you applying for this role?
What do you do outside of work?
Tell me a time you made a mistake?
I applied online. The process took 2 weeks. I interviewed at Ferocia in Feb 2024
Interview
The interview stages were "interview screening questions (via email)" then the choice of "code challenge" type (live session or take-home). First, I sent an email to apply for the position, and the process begins from there.
I've only proceeded up to the "code challenge" and received constructive feedback via email, with the decision to not proceed further (thus, there was no code challenge debrief stage).
Note, the (take-home) code challenge was simple and fun, better than most out there. However, the feedback was they want "code comments" and better emphasis on unit testing, in the overall code contributed to the challenge - keep in mind of these points, as they do not read markdown files and provide a code challenge debrief interview.
In conclusion, be sure to ask about the interview process first and questions about the code challenge itself (for example, ask if they'd prefer written code comments). Lastly, the process were all email comms, never met or seen Ferocia staff on video or in-person.
Interview questions [2]
Question 1
Before you send the email, write answers for What am I passionate about, What am I looking for, and What professional achievement I am most proud of
I applied in-person. I interviewed at Ferocia (Melbourne) in Dec 2019
Interview
1. a lunch, chat and in person overview of the office
2. 1.5 hour in person "pairing" interview
I say "pairing" as this was not a collaborative coding session but more of an in person exam
Interview questions [1]
Question 1
A 1-1.5 hour in person coding challenge. Focus was on working software but it was expected you would write some high level tests to demonstrate the working of your solution. The problem was to translate a given input into an output. The requirements were changed over time to see how well your solution would cope with change. The problem had elements of parsing a grammar.