Workday does a good job of providing a lot of employee programs (fitness, snack, etc.).
As a Software Application Engineer, you will use Workday's proprietary language called XO. It is horrible.
It is soul-sucking and depressing. XO is not a programming language; it is forms that are filled out in a web browser to cause changes in the Workday application.
You will not learn anything by using XO. There are no transferable skills to help you in your future if you work here as a Software Application Engineer.
Workday knows this and are developing a layer on top of XO called YP. Don't be fooled, YP is not like any common programming language and will not help you in your future either.
All I can say is DO NOT work here because you can do better and you deserve better.
1. Hiring Manager: Give a brief intro about the company and a basic class diagram. 2. Technical Interview: - Asks for a UML diagram for a ridesharing app. - Later, there is a demo about their language.
Had multiple rounds of interviews. The technical interview was based on UMLs. Otherwise, it was mostly focused on behavioral questions. The recruiter was very responsive and kept me informed on all steps of the interview process.
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. These were mostly focused on: * Behavioral questions * UML class diagrams (object-oriente
1. Hiring Manager: Give a brief intro about the company and a basic class diagram. 2. Technical Interview: - Asks for a UML diagram for a ridesharing app. - Later, there is a demo about their language.
Had multiple rounds of interviews. The technical interview was based on UMLs. Otherwise, it was mostly focused on behavioral questions. The recruiter was very responsive and kept me informed on all steps of the interview process.
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. These were mostly focused on: * Behavioral questions * UML class diagrams (object-oriente