Accenture · Primly Community

Accenture frontend engineer interview: React, system design-lite, and the behavioral curveball

backend_bekah · 4 replies

came through Accenture's frontend engineer interview in April 2026 for a mid-senior position on a client-facing product team. this was a custom software delivery team rather than the traditional consulting track, so the process leaned more technical than what you'd see for pure analyst roles.

three technical rounds plus a behavioral.

round 1 - coding (60 min): live coding in a shared editor. first problem was a relatively clean React component build: they asked me to implement a filterable list with client-side search and keyboard navigation. no library restrictions, I used vanilla React hooks. second problem was a JavaScript async question, fetching data from two endpoints in parallel and merging the results, handling errors from either one gracefully. Promise.all with try/catch. it wasn't tricky but you need to know the async model solidly. no TypeScript required but I used it and they seemed fine with that.

round 2 - system design for frontend (60 min): I was not fully prepared for how real this was. they asked me to design a client-facing dashboard that ingests real-time data (think: a logistics tracking UI that updates every few seconds). I had to cover: component architecture, data fetching strategy (polling vs. SSE vs. WebSockets and why), caching, performance at scale (what if there are 50 widgets each making API calls), accessibility basics. this was more like a scaled-down FAANG-style frontend system design. I'd recommend actually studying this if you're applying. a lot of frontend candidates skip it.

round 3 - code review (45 min): they showed me a real (de-identified) piece of frontend code and asked me to review it. the code had a few issues: a useEffect with a missing dependency array causing a bug, an overly deep component tree creating prop-drilling hell, and a performance issue where an expensive computation wasn't memoized. I had to narrate the review as if I was talking to a colleague. this format was new to me and I liked it. it tests whether you can give feedback constructively, not just find bugs.

behavioral (45 min): STAR format, consulting-flavored. "describe a time you pushed back on a client's technical decision" was the one that surprised me. for a frontend role I expected maybe culture-fit softballs. they care about delivery judgment at Accenture even for IC engineers.

offer came in at $118k base for the mid-senior level in a secondary market. not big-tech comp but the project rotation and client exposure is genuinely interesting if you like variety over depth.

4 replies

frontend_fran

the code review round sounds kind of great actually. so much more realistic than "implement a trie." did they give you the code ahead of time or was it shown live?

backend_bekah

shown live at the start of the round, maybe 3-4 minutes to read before we started talking through it. not a ton of time so read fast and start mentally categorizing what you see: bugs, design problems, style issues. then talk through it in roughly that order.

laidoff_lena

the frontend system design gap is real. most frontend interview prep focuses on component trivia and JavaScript quirks, not actual architecture. good reminder to work on that if you're targeting consulting-adjacent product work.

market_realist

the $118k base in a secondary market feels light for mid-senior but I know Accenture has a more compressed band than big tech. did they offer any signing bonus or equity? asking because that comp is the part that usually needs to be negotiated.