Backend Engineer applicants have rated the interview process at Autify with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 14.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Backend Engineer roles take an average of 14 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Autify overall takes an average of 18 days.
Common stages of the interview process at Autify as a Backend Engineer according to 2 Glassdoor interviews include:
Phone interview: 33%
Background check: 33%
Skills test: 33%
Here are the most commonly searched roles for interview reports -
1. HR Interview
- Relatively easy process, as they explain about the company and want to understand your motivations for joining their company.
2. Programming Assignment
- They ask me to design a website fetcher script that runs on command-line, without using any built-in tools like wget or curl etc...
- I designed it using JavaScript, the script downloads the html, css, jpg, icon assets of the webpage in order to be able to load offline.
- There was small request to add the --metadata option, which when present, it would allow to print the metadata information to the url site you are checking.
- They requested to make a github repository and submit the link to them
3. Technical Interview
- 2 Engineers performed my interview.
- Initially they asked me questions related to my skills, which I explained without any issues
- Then a whiteboard system design questioning was performed by another engineer, which I designed a reasonably good system based on the contraints provided.
- I did not appreciate the 2nd engineer constantly pretending like he doesn't understand what I'm saying, I don't know if he's english was the problem or just was in a bad mood.
Interview questions [1]
Question 1
Overview
We want to build a web application where users can type in a web address, and store the current value offline. Think about web archive as an example. For example: I would type in https://www.google.com and hit "Save". Your application would scrape the website and sabe it so the user could then download the files, and access it on their local machine.
Please use the whiteboard to draw & explain your answers
Setup
- Draw an infrastructure diagram of what you would want the production infrastructure setup to look like
- How would a user's request travel through your system?
Questions
- How would you save costs & scale the system if the usage changed throughout the day?
- If you were to scale up to 10000 users a day where would the performance & scalability bottlenecks be?
- What would you do to fix this?
- How about 1 mil users?
- What do you see as the disadvantages and advantages of your proposed architecture?
- What would you put in place for disaster recovery?
I applied through a recruiter. The process took 2 weeks. I interviewed at Autify (Tokyo) in Feb 2023
Interview
I stopped at 2nd stage. Overall here is the Interview Process: 1. Coding test using Hackerrank with 60 minutes time contains 3 questions. 2. Take home assignment building app in 1 week.
Interview questions [1]
Question 1
1. Coding test 3 questions in 60 minutes. 2. Take home assignment in 1 week.