I was contacted by a recruiter through LinkedIn.
A brief phone call with the recruiter was followed by a 45-minute phone interview with the hiring manager. The interview was mostly behavioral, focusing on past experience, with a few questions on Object-Oriented Design (OOD) basics.
I was invited for an in-person interview a couple of weeks later.
There were 3-4 managers, one demo of their IDE, and one technical interview with two members from the development team.
Their OOD is centered around the object model they use in Espresso, which I realized is not entirely industry standard.
Their application stores data as objects, not in a client/server model where data is stored in RDBMS or NoSQL database platforms.
They seem to pull data on demand based on object relationships, whereas a traditional model fetches data from the RDBMS. I felt this makes the object model a bit different.
Their Espresso IDE demo will make this more clear.
Design Amazon billing invoice.
Lots of behavioral questions, TDD, and Agile process questions.
The following metrics were computed from 4 interview experiences for the Workday Senior Applications Developer role in Pleasanton, California.
Workday's interview process for their Senior Applications Developer roles in Pleasanton, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Workday's Senior Applications Developer interview process in Pleasanton, California.