Next to Facebook, Workday's IPO is the most exciting in Silicon Valley. Cutting-edge technology. The rate at which Workday can develop product is unbelievable, leaving our competition struggling to keep up. Vacation time was increased this year, and if the company hits its goals. Company meetings are fun; celebrities such as Captain Sully and Steve Young have attended in the past. We poke fun at our competition at the meetings, portraying SAP employees doing the goose step, and there is even artwork of Larry Ellison being flushed down a toilet at the company headquarters. Needless to say, product confidence is very high.
There is a lot of money at stake at Workday. Not only are the investments of our founders on the line, but several million dollars from famous Bay Area Tech funders and CEOs also have their money wrapped up in Workday. As a result, things have tightened up. Salaries haven't been raised in years, and stock is being guarded tightly. As it stands, the amount of work versus resources is stretched thin, and every overhead cost is scrutinized.
Look past 2012. The IPO is a very big milestone; however, building a sustainable company with good morale is of even greater importance. The IPO is going to make several people very happy and wealthy, but is that enough to retain talent and create a company for the future?
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.