The process was absolutely brutal.

Here's how it goes:

1. Interview with Ceridian recruiter (who sounded extremely rushed). The conversation lasted maybe 10 minutes and she was not friendly, and sounded very rushed
2. Technical Interview - Some random developer somewhere in the world will ask you extremely in depth questions about tech. You're not allowed to Google anything.

Based on how you perform on the technical interview, they consider you for a role. Eg. If you fail all the web stuff, but do great on the desktop stuff, you'll be an SD. If you do great on web, bad on OOP stuff, you'll do web.

But it is not a personable interview. No questions were asked pertaining to my projects or what I actually worked on.

I did not pass the 2nd interview. It was honestly quite brutal in that it was almost 2 HOURS LONG!!!! This was by far the worst technical interview I have ever done.

They ask extremely in depth about technical concepts that normally, you would just google on the job. If you bring up a term, they ask you to explain it, which is fair.

But then they ask you more in depth questions on it like how it actually works in memory. What happens with memory, what happens compared to another operation. How does this language handle it vs this language. How does it relate to this other concept. Some of these are fair, some of them I had to do a double take if I was interviewing for a Senior role by accident.

While I think it's fair to ask someone to explain a concept, I don't think it's fair to expect people with less than 3 years of experience have the same knowledge of a Senior Dev, or ask things so specifically that normally on a job you would Google anyways.

99% of the answers you need to lookup the documentation and I don't think would be related to the real job. I don't think the interview properly assesses a developers skills.

I was absolutely drained 30 minutes in after explaining a simple concept, then continuously asked to explain it on deeper and deeper levels each time.

Luckily had an offer from somewhere else come through, but man I would never interview with them again. I almost prefer a coding assignment compared to this.

Have you heard of "X" concept? Explain it. Now what happens on a deeper level. What's the difference between "X" concept and "Y". How would this best be used? You mention using "Z" concept just now, explain it. "How does it work in relation to X concept". "What about in memory" "What about in this situation, or that" "How would it behave in this situation"

Be careful what you bring up. If you bring it up, you will be asked about it. If you explain a concept without bringing up the term, they'll ask you what the name of that concept is.

Read other reviews on here, the technical concepts are very similar almost 1 to 1. But again, anything you bring up will be asked