The A4A process, which is Access for Awesome, involved two rounds of telephonic interviews.

One was with a senior technical individual, and the other was with a manager from another team (who also asked technical questions).

Following the telephonic rounds, I was invited onsite for the interview. At Intuit, the A4A process is quite well-structured.

You begin by presenting a PowerPoint introduction to all panel members. They will then primarily address all questions, excluding technical ones, during your presentation.

After this, you'll be presented with a problem statement. You will need to provide a working solution by coding it directly. You'll have approximately 45-60 minutes (sometimes up to 90), depending on the complexity of the problem statement.

Once you complete the coding, the subsequent questions will focus on your solution, primarily revolving around the 'what, how, and why?' aspects.

(Telephonic) Asked about the project that I'm currently working on.

(Telephonic) More questions around the choice of technology for the application.

(Telephonic) Any problems encountered during development? How were they solved?

(Telephonic) More questions on caching and caching mechanisms.

(Telephonic) LRU implementation.

(Face to face) Develop a servlet to pull data from a database. Pretty straightforward problem statement.