Started with a very polished chat with HR, then the interview starts with a take home coding challenge. I was verbally told it wasn't a big deal, and to just spend a couple hours on it as it would be used as a discussion point in a later interview round.
That was a lie; they actually expect candidates to spend 12+ hours on it, it's massive, and it's graded VERY strictly. (It's also very poorly defined, as a nice bonus, without clear test cases provided.)
I could have trivially passed it if they'd made it clear what they wanted, but they didn't, so I failed, and didn't make it to the subsequent interview round.
Did it leave a sour taste in my mouth? Yes.
Interview questions [1]
Question 1
As above; it starts with a massive take home coding challenge. Basically you're given a very vague problem statement and a small amount of example data (carefully chosen to NOT cover any interesting edge cases), and must come up with an entire solution (design, implementation, API, test cases, code coverage, documentation, everything), all finished to the level you'd expect in production code (ie, full test coverage, edge cases thought about, errors handled, consistent method names, use a logging framework, everything).
Don't be surprised if you fail due to something like "we told you we wanted logs, but we didn't tell you what would be consuming the logs, and you guessed wrong, so the formatting of the log messages isn't quite what we expected". Yes, it's THAT nit picky. And no, you can't ask questions during the process.