Accenture Frontend Developer Interview Questions

“We were designing a claims portal, and I built a clickable prototype for a workshop with a few of the client's customers. I expected comments on colours. Instead, people got stuck on the first step because we asked for a policy number, and most did not have it at hand. One person said she would give up there. We changed the start so people could identify themselves with their phone number and birth date. It took me a day to change the prototype, and the next group went through without help. The result was your result.”

“We had three weeks left for a client's new booking site, and the design included custom animated date pickers and a map. I sized each part and showed the designer that those two items took a third of the remaining time. I did not just say no. I built a quick version with a standard date picker styled in the client's colours, and we looked at it together. She agreed it kept the feel. The map moved to a later release. We wrote that down for the client. The site launched on the day, and your result.”

“I would begin with design tokens, the named values for colours, spacing and type, so that a brand change is made in one place. Then I would build a small core of components that every team needs, such as buttons, inputs and dialogs, each tested for keyboard use and screen readers. The library is published as a package with version numbers, so teams upgrade when they are ready and breaking changes are announced. A documentation site shows each component with examples. Most important is the process: teams need a simple way to ask for changes, or they will build their own copies.”

“No text would live in the code. Every string goes in message files with a key, and translators get context for each one. For layout, I use logical properties such as start and end instead of left and right, so the whole page flips when the direction changes. Dates, numbers and plurals are formatted with the browser's built-in tools, because rules differ more than people expect. I would also leave room for longer words, since a short English label can double in length. One right-to-left language goes into testing from the first sprint, not the last.”

“I would agree a budget for page weight at the start and test on a cheap phone with the network slowed down, not on my laptop. The first screen should arrive as ready content from the server, with only the script that screen needs. Other code loads when the user goes there. Images are sent in sizes that fit the screen and load only as they come into view. I would keep third-party scripts to a minimum, since each one costs the user. If the connection drops during a form, the entries are kept and sent when it returns.”

“I would agree at the start which standard the site must meet, and put it in the definition of done for every story. In the code that means real headings, buttons and form labels, not styled boxes, plus good colour contrast and full keyboard use with a visible focus. Automated checks run in the pipeline, but they catch only part of the problems. So each journey is also tested with a screen reader and with zoomed text. Before launch I would ask for sessions with people who use assistive tools every day, since they find what we miss.”

“I would go through each item with the agreed designs and stories next to me. If the screen does not do what was agreed, it is a defect and I fix it fast. If it does what was agreed but the tester wants something else, I note it as a new request with a rough size and the reason they want it. I avoid the word wrong. Then my lead and I take the list to the client's product owner, who decides what must be in before launch and what can follow. Testers who feel heard stay on our side.”

“I enjoy the early part of a project most, when an idea becomes a prototype and real users react to it. Accenture provides consulting and technology services to clients in many industries, so I could help shape a portal for a bank one year and a public service site the next. Each has different users and different rules, which keeps me learning. On my last project, a workshop with users changed our first screen completely, and the product was better for it. I want to grow in leading that kind of session and in building shared libraries for client teams.”