Good work-life balance. Spend $ on employee events.
Everyone that I worked with was either related or a former colleague of management. It didn't seem that the most qualified person was hired; the more people you knew at Workday, the more likely you were to get hired/promoted. There is no career path for the few who are hired on as worker bees. The company tries hard to maintain its image as a "great place to work".
The ratio of directors to employees is 3:5. Most employees are reporting to directors. You might want to rethink the hierarchy and not give out titles to friends and family if the person has a 1-year tenure at Workday. You have lost many qualified people who left due to lack of career growth.
Much improvement is needed in the recruiting process. The process is long and tedious. The recruiters don't call back or respond when emailed. This has caused very qualified people to pass on the opportunity at Workday.
Two over-the-phone interviews were conducted. During these interviews, I was asked to create a UML modeling relationship between given objects. The expectations were vague, even after asking clarifying questions.
Overall, it was a comprehensive and positive experience. The interview process included: * A technical interview * A few pseudo-technical interviews * A lot of behavioral interviews The technical interview shouldn't be too difficult if you know how
Have detailed knowledge of Object-Oriented Programming and Class Diagrams. Be ready to explain cardinality, inheritance, and other OOP design methodologies.
Two over-the-phone interviews were conducted. During these interviews, I was asked to create a UML modeling relationship between given objects. The expectations were vague, even after asking clarifying questions.
Overall, it was a comprehensive and positive experience. The interview process included: * A technical interview * A few pseudo-technical interviews * A lot of behavioral interviews The technical interview shouldn't be too difficult if you know how
Have detailed knowledge of Object-Oriented Programming and Class Diagrams. Be ready to explain cardinality, inheritance, and other OOP design methodologies.