Snacks 401k matching (with after-tax 401k contributions allowed)
I don’t think it’s possible to deny that Workday has some positive attributes. I’m sure some people can go through their career there without a hitch. But I think I can safely say that if you want a great software engineering career, you need to do much better than working in the apps org at Workday. I think joining the Apps was the biggest mistake in my entire life, setting me back years in my professional development.
And it’s not just working in XpressO. At the end of my tenure, I came to appreciate the things it did well. It’s more the lack of insight into any part of the technical stack and the subpar technical leadership in Apps. Almost every manager I had during my tenure were Peoplesoft->Oracle->Workday, so several years away from the technical cutting edge. The lack of almost any technical know-how forces nonsense metrics to be the measure of an engineer's ability, such as the number of commits in a month or how many comments were posted on a code review. Issues with my manager disappeared when I started committing near blank code to keep my number up and started telling my peers to give me comments on my code reviews directly, instead of on the code review tool. And I know for a fact it’s not just me who dealt with this.
Workday appears to hire three types of people in apps: college students who don’t know any better, older folk who don’t care anymore about being on the bleeding edge and just want a stable 9-5, and managers who worked at Peoplesoft at some point. Not exactly the ideal combination for what should be a high-performance team.
Invest in your employees. Untangling XO from Workday is probably near impossible, but I think Tools team rotations should be mandatory.
Hire technical managers who have some sort of interest in programming. I don’t need a Manager Who Codes, but I do need a manager who understands basic system design principles and can point me in the direction I want my career to grow.
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