J'ai passé un entretien chez Workday (Dublin, Dublin)
Entretien
Phone call
OOP Interview
Onsite 4 rounds
i passed the all technical interviews with very good feedback specially in the architect interview but Overall i didn’t pass to the offer stage as they see me overqualified and looking for leading position however i was asked directly about the seniority level and i answered clearly that i prefer not to lead team.
I think this is not the right reason for rejection as i stated that to the recruiter in the feedback call and she said she will definitely help me to get another position as i am overqualified but unfortunately she didn’t answer my emails after that.
I can rate the experience as awful and waste of time as i see the company leaving good candidates because a problem in their interviews and the recruiting team.
Questions d'entretien [1]
Question 1
All Technical Questions are related to OOP modeling and database modeling concepts otherwise is behavioral
J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Workday (Atlanta, GA)
Entretien
1)Hiring Manager: Give a brief intro about company and a basic class diagram 2)Technical Interview: Asks for UML diagram, I am asked ridesharing app. Later there is a demo about their language
Questions d'entretien [1]
Question 1
1)Hiring Manager: Give a brief intro about company and a basic class diagram 2)Technical Interview: Asks for UML diagram, I am asked ridesharing app. Later there is a demo about their language
J'ai postulé en ligne. J'ai passé un entretien chez Workday
Entretien
Had multiple rounds of interviews. Technical was based on UMLs. Otherwise was mostly focused on behavioral. Recruiter was very responsive and kept informed on all steps of the interview process.
J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Workday en févr. 2023
Entretien
I first had a phone call with the recruiter, which was mostly about the company, the position, and my qualifications. Later, I had almost five interviews, which were mostly focused on behavioral questions, UML class diagrams (object-oriented programming, classes, attributes, and relationships), and improving the model (such as how to simplify existing relationships, minimize methods and attributes, and determine cardinality).