Job is Still Open - CLICK HERE for Job Details
👉 HOW TO GET A JOB IN A MONTH - GET HERE
Role: Web Developer Associate
Company: Accenture
Location: Mumbai
Interview Slot Time: July 25, 2025 – 11:00 AM IST
Interview Mode: Online (Microsoft Teams)
Interview Level: Entry-Level (0–2 years)
Candidate Name: Anonymous
Complete Interview Experience (30+ Questions)
🧪 TECHNICAL ROUND (Q1–Q10)
Q1. What is Adobe Experience Manager and why is it used in enterprise projects?
Candidate Answer:
"Adobe Experience Manager, or AEM, is a comprehensive content management solution for building websites, mobile apps, and forms. It helps enterprises deliver consistent digital experiences across channels. It allows marketing teams to easily create, manage, and deliver content, while developers can build reusable components."
Feedback: Good overall understanding. Could add use cases like personalization and digital asset management.
Skill Assessed: AEM knowledge
Mistakes to Avoid: Avoid generic CMS definitions – focus on enterprise-grade use
Q2. How would you create a custom component in AEM?
Candidate Answer:
"I'd use HTL (HTML Template Language), define the component in CRXDE Lite, and link it with a Sling model in Java. The component would live under /apps/project/components and be referenced from a template."
Feedback: Accurate flow. Could improve by mentioning clientlibs and dialog.xml.
Skill Assessed: AEM development basics
Mistakes to Avoid: Don't ignore structure (JCR paths, sling models)
Q3. Difference between HTL and JSP in AEM?
Candidate Answer:
"HTL (formerly Sightly) is a secure templating language, unlike JSP. HTL separates logic from markup and prevents XSS attacks by default. JSP is Java-heavy and outdated in AEM."
Feedback: Spot on. Strong answer.
Skill Assessed: AEM templating
Mistakes to Avoid: Don't say “HTL is just HTML.”
Q4. Write a sample responsive web layout using HTML and CSS.
Candidate Answer:
“<header>, <main>, <footer> with media queries using flexbox for mobile responsiveness.”
Feedback: Okay, but too shallow. Should've shown code.
Skill Assessed: HTML/CSS layouting
Mistakes to Avoid: Don’t describe when you can demonstrate
Q5. What are client libraries in AEM and how do you use them?
Candidate Answer:
“They’re used to manage CSS and JS. You define them with categories in clientlibs, and include them via data-sly-use.”
Feedback: Could improve with details about dependencies and embed property.
Skill Assessed: Frontend integration in AEM
Mistakes to Avoid: Avoid being vague; give directory paths and syntax
Q6. How do you debug layout issues in AEM pages?
Candidate Answer:
"Use Chrome DevTools to inspect DOM and applied CSS. If it’s AEM-specific, I’d check CRXDE paths and clientlibs loading."
Feedback: Good approach. Mentioning logs or dispatcher cache could make it stronger.
Skill Assessed: Debugging
Mistakes to Avoid: Don’t skip cross-browser/device testing
Q7. How do you handle performance issues in AEM?
Candidate Answer:
"Minify JS/CSS, use proper caching, optimize images, and avoid unnecessary server calls."
Feedback: Correct, but could mention dispatcher caching or lazy loading.
Skill Assessed: Web optimization
Mistakes to Avoid: Don’t generalize – give AEM-specific answers
Q8. How is CSS specificity calculated?
Candidate Answer:
“Inline > ID > Class > Tag. Inline styles are most specific. More selectors = more specificity.”
Feedback: Decent. Should’ve included calculation: Inline (1000), ID (100), class (10), element (1).
Skill Assessed: CSS deep knowledge
Mistakes to Avoid: Avoid vague “more selectors = more power” talk
Q9. How does version control work in AEM project structure?
Candidate Answer:
“We use Git for managing code. Content is pushed via Maven builds to AEM.”
Feedback: Accurate. Could mention how JCR content isn’t in Git unless packaged.
Skill Assessed: DevOps basics in AEM
Mistakes to Avoid: Don’t assume AEM content is auto-versioned
Q10. What is a dispatcher in AEM and how does it improve performance?
Candidate Answer:
“Dispatcher acts as a caching and load balancing tool. It caches pages and filters requests, which reduces load on publish servers.”
Feedback: Strong, full points.
Skill Assessed: AEM Architecture
Mistakes to Avoid: Don't forget: Dispatcher configs are Apache-based
🧠 BEHAVIORAL ROUND (Q11–Q17)
Q11. Tell me about a time you adapted quickly to a new tool or technology.
Candidate Answer:
"In college, I had to use Figma for a UI project overnight. I learned it via YouTube and delivered a prototype in 2 days."
Feedback: Shows agility. Great fit for ‘quick learning’ culture.
Skill Assessed: Agility & learning speed
Mistakes to Avoid: Don’t overplay – stay believable
Q12. Describe a situation where attention to detail saved your project.
Candidate Answer:
"While designing a form in HTML, I noticed a wrong input type. Fixing it saved user validation issues later."
Feedback: Good example but could use a bigger impact scenario.
Skill Assessed: Detail orientation
Mistakes to Avoid: Don’t go too “micro”
Q13. How do you handle feedback from supervisors or peers?
Candidate Answer:
"I always thank them, take notes, and apply it fast. I see feedback as fuel."
Feedback: Great attitude. Company culture match.
Skill Assessed: Coachability
Mistakes to Avoid: Avoid sounding defensive or perfectionist
Q14. Ever worked on a project where you had to rely on another teammate’s code?
Candidate Answer:
"Yes, I had to debug a teammate’s CSS. I asked them to walk me through the logic before tweaking it."
Feedback: Collaborative mindset—this is a plus in team-oriented Accenture culture.
Skill Assessed: Collaboration
Mistakes to Avoid: Never bash teammate code
Q15. Tell me about a stressful deadline you handled.
Candidate Answer:
"In a college hackathon, we had 24 hours. I coded UI nonstop and helped with backend setup too."
Feedback: High-pressure performance – solid.
Skill Assessed: Pressure handling
Mistakes to Avoid: Don’t exaggerate work hours
Q16. Describe a time you solved a tough problem using a creative approach.
Candidate Answer:
"I couldn’t use JS animations, so I used only CSS transitions and keyframes for an interactive quiz."
Feedback: Shows innovation. Great answer.
Skill Assessed: Problem solving
Mistakes to Avoid: Avoid cliché ‘we Googled it’
Q17. What motivates you in a team environment?
Candidate Answer:
"Shared goals and learning from others. I like when everyone brings their strengths to the table."
Feedback: Matches Accenture’s collaborative ops culture
Skill Assessed: Team dynamics
Mistakes to Avoid: Don’t say “I prefer working alone.”
🧩 SITUATIONAL ROUND (Q18–Q24)
Q18. You’re given an urgent AEM page bug in live environment. What do you do first?
Candidate Answer:
“Reproduce the issue in staging, check logs, test rollback options. Then deploy a hotfix after QA approval.”
Feedback: Sharp troubleshooting. Good structure.
Skill Assessed: Incident response
Mistakes to Avoid: Never say “I’d fix it directly in production”
Q19. Your client wants a pixel-perfect UI, but you’re tight on deadline. What’s your move?
Candidate Answer:
"Prioritize functional UI, share tradeoffs with client, and give a roadmap for design perfection post-MVP."
Feedback: Balanced – technical + communication
Skill Assessed: Scope management
Mistakes to Avoid: Don’t promise “everything fast”
Q20. A teammate left mid-project. How do you manage deliverables?
Candidate Answer:
"I’d assess their modules, delegate tasks within team, and update the project manager immediately."
Feedback: Strong ownership
Skill Assessed: Crisis handling
Mistakes to Avoid: Don’t wait for someone to assign the work
Q21. You’re asked to use a tool you’ve never used before (e.g., AEM). What’s your learning strategy?
Candidate Answer:
"Go through official docs, quick YouTube crash courses, and hands-on sandbox builds."
Feedback: Smart – Accenture loves fast learners
Skill Assessed: Self-learning
Mistakes to Avoid: Avoid saying “I’d wait for training”
Q22. You notice broken clientlibs across several pages after deployment. What next?
Candidate Answer:
“Rollback clientlib changes, check categories & embed orders, and redeploy after fix.”
Feedback: Spot on
Skill Assessed: CSS/JS handling in AEM
Mistakes to Avoid: Don’t reload blindly
Q23. You’re assigned rotational night shifts. How do you plan your day for productivity?
Candidate Answer:
“I’ll adjust my sleep schedule, block distraction hours, and use light workouts to stay sharp.”
Feedback: Shows maturity
Skill Assessed: Shift adaptability
Mistakes to Avoid: Don’t say “I’ll just wing it”
Q24. APM asks for hourly progress updates. How do you handle frequent check-ins while working?
Candidate Answer:
“I’d log my tasks in chunks and share via Slack/email. I’d balance updates with delivery.”
Feedback: Good balance of accountability and productivity
Skill Assessed: Communication in real-time ops
Mistakes to Avoid: Don’t whine about micromanagement
🧾 HR ROUND (Q25–Q30)
Q25. Why do you want to join Accenture?
Candidate Answer:
"Accenture blends tech with creativity, especially in marketing ops. I want to be part of that change engine."
Feedback: Tailored. Good job.
Skill Assessed: Role interest
Mistakes to Avoid: Don’t say “Because it’s a big brand.”
Q26. Are you comfortable working in rotational shifts and weekends if needed?
Candidate Answer:
“Yes, I understand project timelines and client delivery requirements may demand it.”
Feedback: Shows readiness
Skill Assessed: Availability & flexibility
Mistakes to Avoid: Don’t say “Only if needed”
Q27. What’s your expected salary?
Candidate Answer:
“I’m open to market standards for a fresher with 0–2 years of experience.”
Feedback: Smart – opens room for offer
Skill Assessed: Salary negotiation
Mistakes to Avoid: Avoid underselling or over-quoting
Q28. What’s your notice period?
Candidate Answer:
“I’m available to join immediately.”
Feedback: Big plus for fresher hiring
Skill Assessed: Availability
Mistakes to Avoid: Don’t say “after a long vacation”
Q29. Are you okay relocating to Mumbai and working from office?
Candidate Answer:
“Yes, I’m excited to work at HQ and collaborate onsite.”
Feedback: Positive, culture fit
Skill Assessed: Relocation readiness
Mistakes to Avoid: Don’t sound hesitant
Q30. Do you have any questions for us?
Candidate Answer:
“Yes – What kind of AEM projects do you typically handle in this team?”
Feedback: Curious and role-aligned. Good closer.
Skill Assessed: Engagement
Mistakes to Avoid: Don’t ask “When’s lunch?”
🔚 INTERVIEWER SUMMARY
Technical Performance: 8.5/10
Communication Skills: 9/10
Confidence Level: Medium–High
Recommendation: ✅ Shortlist for Final Round
What the Candidate Missed:
-
Could go deeper into AEM architecture and clientlibs
-
Lacked real-world deployment pipeline or testing flow knowledge
-
HTML/CSS answers needed better demonstration, not just explanation