A few months ago, I went through Accenture’s Go for Gold selection process. I cleared multiple assessment stages and eventually reached the virtual interview.

Since several months have passed, I don’t remember the exact sequence of every assessment or the exact wording of every question. So, rather than filling in the gaps with things I’m not sure about, I’m sharing the parts of my own experience that I genuinely remember.

I hope this helps someone going through a similar process. :)

🧠 Cognitive and Gamified Assessment

One of the assessments I remember was quite different from a normal aptitude test.

Arithmetic Ordering Task

In one section, I was shown a few mathematical expressions at a time. They involved basic calculations such as squares, multiplication, addition, and subtraction.

The task was to mentally calculate their values and arrange or select them in increasing order. As far as I remember, there were around 20 questions, and the time given for each set was very short—roughly 15 seconds.

The calculations themselves were not particularly difficult. The actual challenge was doing them quickly without making careless mistakes under time pressure.

If you're preparing for something similar, I would recommend practising quick mental calculations rather than only traditional quantitative aptitude questions.

🧩 Pathfinding Puzzle

There was also a puzzle-based game.

I had to find or create a valid path from a starting point to a destination. I don't remember the exact interface now, but the idea was to logically work out how to reach the end.

I actually found this part interesting because it felt more like playing a logic game than taking a traditional test.

💻 Technical and Coding Assessment

I also went through a technical assessment that included coding and questions from other technical areas.

Coding Question

The coding question I received was a basic string-processing problem related to vowels.

I believe the task involved either counting or removing vowels from a given string. I don't remember the exact wording confidently enough to state the precise question, but it involved basic string traversal, loops, and conditions.

This reminded me of something simple but important: don't ignore the fundamentals while preparing for harder DSA problems.

It's easy to spend all your time on difficult topics and forget that assessments can still test your ability to write a clean solution for a straightforward string or array problem.

SQL and HTML

I also remember getting a question involving SQL and another task related to HTML.

I no longer remember the exact questions, so I won't try to recreate them from memory. My general suggestion would be to revise SQL fundamentals and basic HTML before the assessment rather than focusing exclusively on coding.

🎙️ Communication Assessment

The communication assessment involved different listening and speaking activities.

I remember tasks such as:

Reading text aloud
Listening to sentences and repeating them
Other speaking and listening exercises

For this round, I think clarity and careful listening matter much more than trying to use complicated vocabulary.

My advice would be to sit somewhere quiet, use a good microphone or earphones, listen carefully before answering, and speak naturally.

👩‍💻 The Virtual Interview

After clearing the previous stages, I eventually reached the virtual interview.

There are two moments from that interview that I still remember very clearly.

🎤 Yes, I Was Asked to Sing

During the conversation, I mentioned that reading and singing were among my hobbies.

So the interviewer asked me to sing something.

And yes... I actually sang. 😭

At that moment I definitely wasn't expecting my interview preparation to require a live singing performance, but looking back, it is one of the funniest and most memorable parts of the entire process.

To be fair, I had mentioned singing as a hobby, so the question didn't exactly come from nowhere. 😅

🤔 One Hard Problem or Ten Easy Problems?

Another part of the interview has stayed with me for a completely different reason.

The interviewer told me that the question he was about to ask would not be considered as part of my evaluation. He then asked me something along the lines of:

Would you choose to solve one hard problem or ten easy problems?

He gave me some time to think about it.

I chose the one hard problem.

My reasoning was that I didn't want to back down simply because something was difficult. I felt that if I always chose the easier option, I might end up avoiding challenges rather than learning how to face them.

The interviewer then gave me another perspective, speaking more like a mentor.

He explained that choosing the harder task is not automatically the better decision.

If someone simply tells us that a problem is hard, we don't necessarily know how hard it is. We don't know how much time it will require, what resources it might need, or whether we can realistically solve it in the situation we're in.

With the ten easy problems, on the other hand, we have more certainty. We understand their approximate difficulty, and completing all ten may sometimes create more value than spending all our effort on one uncertain challenge.

That conversation made me think.

My answer came from a place of not wanting to run away from difficulty. But his perspective showed me that there is a difference between being willing to face challenges and choosing difficulty simply because it is difficult.

Sometimes taking on the hardest problem is the right decision.

Sometimes completing ten achievable problems is the smarter one.

I still remember that conversation months later, which is probably why I consider it one of the most valuable moments of the entire process.

📌 The Result and What I Learned

I ultimately wasn't selected.

Naturally, it was disappointing to reach the interview after going through multiple assessment stages and not make the final selection.

But the experience taught me that internship and placement preparation is much broader than simply solving increasingly difficult coding problems.

During one selection process, I encountered mental calculations under time pressure, logic games, coding, technical fundamentals, communication assessments, and finally an interview that went from discussing my background to singing a song and thinking about whether I would choose one hard problem or ten easy ones. 😭

My biggest takeaway was this:

Preparation isn't only about knowing more. It's also about thinking clearly under pressure, communicating your reasoning, having strong fundamentals, and learning to make better decisions when there isn't one obviously correct answer.

I didn't get the outcome I wanted from this process, but I did come away with experience and a conversation that I still remember.

If you're preparing for a similar process, I hope sharing my experience helps in some small way.

All the best! :)