A campus hire at a global consulting and technology services company often joins a team that is building something new for a client, where the first weeks are spent understanding what the business really wants. Prepare to explain your college projects to someone who is not technical, to show how you ask questions when a requirement is unclear, and to link your fundamentals to a client's business process. What to show here: clear explanations and curiosity about the client's business. Each question below has what the interviewer is checking, an answer frame and a sample spoken answer to adapt.
How Accenture hires, in its own words, and its questions for every job →
“For our final year project we built a small app for the college canteen, and I had to explain to the canteen manager why we needed his menu in a fixed format. He did not care about databases. I compared it to his own order book: if every waiter wrote orders in a different way, the kitchen would make mistakes. He understood at once. I then asked him to tell me in his words what we needed, to be sure. He gave us the menu in a sheet the same week. Since then I look for an example from the listener's own work.”
Weak answers repeat the technical explanation more slowly or blame the listener for not following.
“Our guide asked us to build an attendance system, and that was the whole brief. Before coding, I wrote down questions: who marks attendance, the teacher or the student? What happens if a class is cancelled? Who sees the reports? I took them to two teachers and the office clerk. It turned out the real pain was the monthly report for the office, not the marking itself. So we built the report first and kept marking simple. The teachers used it for a full term. I learned that the first request is rarely the full need.”
Weak answers start coding from their own assumptions and find out at the demo that it was not what was wanted.
“When the customer presses submit, the browser first checks simple things, such as an empty date. Then it sends the form data to the server as a request. The server never trusts the browser, so it checks everything again and applies business rules, for example that the slot is still free. If all is fine, it saves the booking in the database inside a transaction, so two people cannot take the same slot. It then sends a response with a booking reference, and the page shows a confirmation. If something fails, the customer sees a clear message and keeps what they typed.”
Weak answers skip server-side checks or cannot say what happens when two customers pick the same slot.
“An API is an agreed way for one program to ask another to do something, with a fixed format for the request and the reply. Here I would write a small program that reads the file row by row. For each row it checks the fields, builds a request in the format the new system expects and sends it. It then reads the response code. A success is logged. A failure, such as a missing phone number, is written to an error file with the reason, so someone can correct it and send only those rows again. It would also wait and retry if the new system is busy.”
Weak answers define an API from a textbook and have no plan for rows that fail.
“With version control each of us works on our own branch, and the tool keeps the full history of who changed what and why. When we both edit the same lines, the tool cannot choose and reports a conflict. I would not just keep my own version. I read both changes to see what each was meant to do, and if it is unclear I ask my teammate so we decide together. Then I edit the file to keep both intentions, run the tests and commit the merge. Pulling the latest code often and making small commits keeps conflicts rare.”
Weak answers overwrite the teammate's change or have only ever used version control alone.
“I would first sit with the person who does it and write down each step, including how they handle odd emails. Then I would count how long it takes and how many emails follow the usual format. If most are regular, a program can read them, pick out the figures and fill the sheet. The unusual ones should go to a person with a note, not be guessed. Before anyone depends on it, I would run the program on last month's emails and compare with the sheet they made by hand. I would also ask the staff what they want checked.”
Weak answers start writing a script at once without watching the task or planning for emails that do not fit.
“In the room I would stay calm and say simply that this part is not working as expected and that I will come back on it today. I would not try to debug live while people wait. I would continue with the rest of the demo, or explain the feature with the design, so their time is not wasted. Afterward I find the cause, which is often a difference between my machine and the demo environment. I send a short note with the cause and a time for a new demo. From then on I rehearse in the real demo environment.”
Weak answers make excuses, blame the environment in front of the client or spend the meeting debugging.
“What I enjoyed most in college was not the coding alone but finding out what people actually needed and then building it. Accenture provides consulting and technology services to client companies around the world, so that is the daily work: understand a business, then build for it. As a new graduate I would see how a bank, a shop or a hospital runs, which I could never learn from books. I know I will need to listen well and explain clearly. I hope to grow into someone who can sit with a client and turn their problem into a working system.”
Weak answers mention only the company's size or name and show no interest in clients or their businesses.
No figures on this page: pay depends on the level, the city and the offer in front of you. When the offer comes, the free salary negotiation script helps with that part.
ClapAssist is an AI interview assistant for Mac and Windows. It listens to the interview on your computer and shows you what to say, in short lines you can read while you talk. Your live interview audio and screen are never stored. Your resume and notes are saved to your account so the app fills them in on any computer. It is hidden from screen share on every plan, including Free; only you can see it.