I was first contacted by the engineer to whom I had sent my CV. After that, I had a phone interview with a lead software engineer, which was mostly about my experience.

Then, I had a technical interview with another software engineer. This was followed by a coding challenge that I could complete over several days via email.

I was then flown into London, where I was asked to spend a whole day with them.

They will evaluate you as if you were already a software engineer, expecting the same experience and knowledge. They do not view an internship as a place where you are there to learn. So, if you do not have experience working in a regular company, do not apply.

It took a really long time. I spent so many hours preparing, doing the coding challenge, etc., only to be rejected after the on-site interview.

I believe that if you do not fit the 'agile is everything to me' culture, you will not be selected (they even named the role 'AGILE Software Engineer').

Tech interview: Java basics, OO design, Clean Code, Agile, XP.

Coding challenge: Develop the Rock Paper Scissors game (just Google Rock Paper Scissors eBay and you'll find examples). They provided a user story with some acceptance criteria.

On-site interview: I was asked to write some user stories based on input from a 'product owner,' then code it working in pair programming. The problem was that the pair was an engineer there who was not pairing with me but accessing me. I did everything by myself. When I asked for opinions, there was not much feedback. It was what Kent Beck recommends it not to be.

Then you have to present what you did to the product owner.

After this, there's an interview with lead software developers about Agile experience, Scrum, etc. What would you do in this situation? And this one?

What do you do when you have a doubt? Do you Google? Check Stack Overflow for suggestions? (Answer is no! You need to have people you aspire to, and you'll check what they did - name a few ones).

By the way, the challenge will be to do a Sudoku game with a CLI. Think about software patterns, Clean Code, TDD (most important!).

They will offer you flights, accommodation, lunch, a t-shirt, and a teacup.