I applied online. The process took 2 weeks. I interviewed at AUTO1 Group (München, Bavaria) in Dec 2021
Interview
Amateur HR interview that I have ever experienced.
My first interview was with a HR specialist and he was asking technical questions and it was really funny, because he couldn't write technical expressions and I had to write them and sent by text message :-))))
Don't waste your time with this company, I got any thing of them after the first HR interview.
Dear applicant,
Thank you for your feedback!
If you are open to discussing this further, please contact us at hrfeedback@auto1.com.
Best wishes,
Your HR Team
Other Senior Frontend Developer Interview Reviews for AUTO1 Group
I applied online. The process took 4 weeks. I interviewed at AUTO1 Group in Feb 2019
Interview
This company recruiting team are the worst (don't waste your time):
I have passed all the steps (2 interviews) and then the code assessment (task) that I need to finish before the weekend:
1- They sent me the assessment using Dropbox as if there is no Git or Docker out there.
2- In the assessment, he asked me to submit my code to an (EMAIL), The email mentioned in the assessment was not reachable for almost 3 days which give me huge stress and I had to SEARCH for his personal email in the web so he can get my code.
3- He told me they got my code and the will reply ASAP, My application was pending for 10 DAYS until I remind him about it and then they reply with rejected.
4- In the rejection reasons they said:
- No unit test cases
* Uniting testing was the only point that makes sense but the app was so simple that I forgot to write any unit test (i literally wrote thousands of lines of test code using jest and mocha before)
- No new React 16 features
*I have used some React 16 new features although using ALL new React 16 features is not necessary and was not required, even the React 16 documentations clearly mentioned that no need to migrate from now to all React 16 new features like hooks because it has no impact on the code, it only makes your code looks cleaner only when you have too much logic within your components lifecycle methods .
- Unclear folder structure
* First I am 100% sure there is no standard for folder structure in redux or react and I am very sure they didn't read the README where I have explained every single file and folder purpose.
A lot of developers think that the folder structure they see (while watching react tutorials or read the getting started) is a standard for react or redux, and it is so sad they can just have another session with me where I can explain why I have built it this way and also it's not a big deal i can follow their company guideline.
- Unnecessary use of class component where function component will suffice.
*I have used MANY functions as components but also I always keep some components as classes in purpose. (e.g routes)
Note: In StackOverflow, I am a moderator with 20k points and top 2% (OVERALL) most of my points comes from JAVASCRIPT, I have babel, react-native and react modules with thousands of downloads and I have a contribution in many latest frontend technologies like (styled-components) and when I was searching for the email of the guy who rejected me I found it in GitHub his profile was a disaster and I would literally not even interviewing him with that profile if it was the opposite.
Interview questions [1]
Question 1
Create a single page application using React JS and Redux.