Getting an Interview
Getting an Interview
Interviews for Top Jobs at Accenture
- Associate Software Engineer (548)
- Analyst (240)
- Consultant (196)
- Software Engineer (191)
- Senior Software Engineer (140)
- Business Analyst (124)
- Systems Integration Consultant (116)
- Manager (85)
- Intern (84)
- Technology Consulting Analyst (60)
- Systems Integration Analyst (59)
- Management Consultant (56)
- Senior Manager (44)
- Team Lead (41)
- Senior Consultant (40)
- Management Consulting Analyst (39)
- Consulting Analyst (35)
- Technology Analyst (34)
- Systems Analyst (32)
- Software Developer (30)
- Project Manager (30)
- ASE (30)
- Technology Consultant (29)
- SAP Consultant (29)
- Systems Integration Consulting Analyst (27)
- Financial Analyst (25)
- Programmer (25)
- Senior Programmer (23)
- Client Financial Management Analyst (21)
- Data Analyst (19)
Java Software Engineer Interview
I applied online – interviewed at Accenture (Chicago, IL) in April 2013.
Interviewer hadn't reviewed my resume before calling. Had applied for an entry level position but the interviewer said the position was for currently working individuals with 5-7 years of experience. Interviewer abruptly ended the interview.
Other Interview Reviews for Accenture
Java Software Engineer InterviewNo OfferNegative ExperienceAverage Interview
I applied through an employee referral. The process took 2 weeks – interviewed at Accenture (Seattle, WA) in April 2012.
I had two interviews with Accenture.
The first, an initial phone interview with a gentleman from their recruitment team for about a half hour which was pleasant enough. Talked about my background and he provided me with some basic knowledge about the company. After this we set up a second technical interview.
The second (technical) interview, also by phone, was something of a quiz on acronyms and word definitions. Terms like POJO, MVC, JDBC, Singleton, Inheritance, Encapsulation, Polymorphism, DAO, ORM, SOAP, JNDI, and AOP. Some were easy enough, granted. Their checklist of terms was all they were about. They didn't seem interested in me speaking about technical details of my past projects (which would have been good for them to know). That worked against me in particular because much of the development work I had done (circa 2000) was using many of the concepts they were referring to but but not the terminology . So I didn't do well according to their system. That's fine, I should have been up to speed on the current terminology, simply put. However, they didn't even bother to communicate with me following the interview. Even after I followed up a few days later offering to clarify their view of me, they didn't bother to message back. Even a 'thanks but no thanks' would have been nice! I guess I had been tossed into the gutter, in their mind. Basic professionalism is still expected even if you take a pass on a candidate, in my opinion.
- What is AOP? 1 Answer