First, there was a basic phone screen. Then a slightly more elaborate, technically-oriented phone screen. Then you're given a "code challenge" with (if I recall correctly) 2 days to do it. It's got some simple requirements, and then an optional, more elaborate extension of those requirements. (Not optional for senior positions.) You can solve it in any language you're proficient in. Advice regarding the code challenge: 1) Do not attempt to "cheat". If you don't have the toolset to solve these problems without leaning heavily on Google, you'll get eaten alive at kCura. Don't waste your time or theirs. 2) Use solid object-oriented principles. 3) Use interfaces and dependency-injection to facilitate unit-tests, and if you have time, INCLUDE UNIT TESTS! (I didn't have unit tests myself, and they asked me why not.) 4) Comment your code, or write it so well (meaningful variable and function names, keep functions and procedures short) that it doesn't need commenting. Do more than is asked for, put serious and sincere effort into it. Don't skimp on it because you have "too much else going on". Lose a little sleep if you have to. A good job on this gets you the interview. But I say again, DO NOT CHEAT, do not use someone else's code, do not use any design patterns that you don't understand well enough to explain them completely. The "main event" interview is a bit exhausting; it's 5 hours total, with either 4 or 5 different interview sessions with different people, who will examine different aspects of your background and capabilities. Realize that the interview is an opportunity to get a feel for the company itself and the people you'll be working with. Make sure to ask them sincere questions about their experience here... they will answer sincerely in return. BE YOURSELF! I can guarantee you the people that are interviewing you will be the person that you'd be working with every day. Show them the person they would be working with every day. If you have a joking personality, tell some jokes. The more transparently you present yourself, the more of that you'll get in return. One thing I truly loved about the interview is that they didn't batter me with ridiculous questions about obscure syntactical specifics, how'd you'd implement this object or that class, none of that. The technical interviews focused on getting you to expose how well you think on your feet and problem-solve. And people's communication styles were much more relaxed than I was used to; very informal and welcoming.