The Generation Workday program really does do its best to acclimate new grads into the workforce. It's an easy way to meet a lot of really cool people.
Workday also tends to hire really honest, nice people as new hires. The snack program is fantastic.
Make no mistake: Workday is PeopleSoft, PeopleSoft is Oracle, and, no matter how much they try to convince themselves, Workday is Oracle.
There is zero career advancement at Workday, and it's designed that way. The management chain from the bottom-up is almost exclusively ex-Oracle, ex-PeopleSoft folk. Oracle employees are actively recruited for management or high-priority roles. There are very few people (to the point where I don't know any, but I've heard of them) who came into Workday in management positions. If you are not a PeopleSoft alumni, your chances of advancement are very, very slim. Internal transfers are slim-to-none despite the constant talks they give new hires about them occurring after their first 12 months.
That would be fine and all if this is just a stop-gap in a career, but as an engineer, Workday has designed a tech-stack that essentially tries to ensure employment solely at Workday. It's all proprietary non-programming, and resembles nothing even remotely similar to programming. It's entirely useless for any future jobs. Don't buy into the "Well, there's a lot of similar ideas and principles with traditional programming languages" talk they give: it's nothing like programming. It's just clicking, and clicking, and more clicking. It makes things easy for them, and much harder for the worker, as it's extremely easy to become complacent and you forget traditional programming skills.
Working at Workday is a dead end. If you're young and non-PeopleSoft, I cannot stress how important it is to stay far, far away.
At this point, nothing. They've intentionally created this system and don't see anything changing for a long time.
I met them at an info session and spoke with them at my university's career fair. I was asked to schedule an interview for the next school day during the career fair. The on-campus interview was a 30-minute session, mostly covering background and on
I met the recruiter on campus at UCSD and had an on-campus interview the next day. After a week, I was contacted for an on-site interview. The day started with breakfast, followed by a series of interviews and a technical question. Then, the rest of
I was referred by a friend. I had a phone interview with one of the application developers, and then followed up with him with a take-home question. They set up an on-site a week later with 15-20 other candidates (for other positions as well). The
I met them at an info session and spoke with them at my university's career fair. I was asked to schedule an interview for the next school day during the career fair. The on-campus interview was a 30-minute session, mostly covering background and on
I met the recruiter on campus at UCSD and had an on-campus interview the next day. After a week, I was contacted for an on-site interview. The day started with breakfast, followed by a series of interviews and a technical question. Then, the rest of
I was referred by a friend. I had a phone interview with one of the application developers, and then followed up with him with a take-home question. They set up an on-site a week later with 15-20 other candidates (for other positions as well). The