Senior Adobe Experience Manager Developer, Thaltej, Ahmedabad
A team on SG Highway in Thaltej is hiring a Senior Adobe Experience Manager Developer, full-time and on-site, with a salary up to ₹1,26,500 per month. The role covers the full AEM stack, components, templates, backend Java services, and the content authoring experience that marketing and content teams actually use every day.
Eight years of relevant experience is expected. AEM is a specific enough platform that general Java or CMS experience alone doesn't translate directly, so this figure reflects real depth with the platform itself, not just years spent adjacent to it.
The sites this role supports see meaningful traffic, and content changes go out frequently, sometimes multiple times a day during a campaign push. That pace means changes need to be both fast and safe, which is a different discipline than working on an internal tool where a broken deploy mostly just annoys a handful of colleagues.
What the work involves
- Build and maintain AEM components and templates using HTL, backed by Java logic where the front end needs real data or business rules
- Develop and extend content management workflows that content authors rely on daily
- Check teammates' pull requests for correctness and for patterns that will cause pain later in a large AEM instance
- Troubleshoot issues reported by content authors and end users, tracing problems through the AEM dispatcher, OSGi services, or the content repository as needed
- Sit in on planning conversations with product and QA so new features get built against what content teams actually need, not a guess at it
A recent example of the kind of debugging this role handles: a component that rendered fine in the author's environment but broke silently on the published site due to a caching rule at the dispatcher layer that nobody had touched in over a year. Tracing that kind of issue across the full AEM stack, not just the component code itself, is a real and recurring part of the job.
Not every week looks like that; plenty of the work is steadier: building a new component to spec, extending an existing workflow, cleaning up technical debt in an older part of the codebase before it causes a real problem. The dispatcher-level mysteries show up often enough to keep things interesting without being the entire job.
What the role expects
A bachelor's degree is the baseline requirement, and the hiring team weighs real, demonstrated AEM project work well above the specific degree title. Genuine hands-on depth with the platform, ideally including at least one full implementation from setup through launch, matters far more than years of general Java experience alone.
Naukri Mitra has noted that senior AEM roles remain relatively scarce compared to general full-stack openings, since the platform's learning curve keeps the pool of genuinely experienced developers smaller than demand across Gujarat's growing enterprise software sector.
Core skills
- Strong, hands-on Adobe Experience Manager development experience, components, templates, and workflows
- Solid Java, since most non-trivial AEM logic eventually runs through backend services
- HTL (Sightly) for building the templating layer that content authors and front-end teams both depend on
- Practical content management experience, understanding how authors actually work inside the platform, not just how developers build for it
What strengthens an application
Experience with AEM as a Cloud Service, rather than only on-premises implementations, is increasingly valuable as more companies migrate. Familiarity with Sling models and OSGi services will speed up onboarding considerably, and any exposure to headless AEM implementations is a genuine plus given where the platform's been heading.
None of these extras are treated as hard requirements. A developer with great, proven skill in traditional AEM implementations but limited Cloud Service exposure will still receive real consideration, since platform fundamentals matter more than the specific deployment flavor used in someone's most recent project.
Compensation and what's included
The role pays up to ₹1,26,500 monthly. Along with the salary, the offer includes medical coverage and standard paid leave, plus a bonus tied to individual and team performance rather than a flat annual amount. Since the position is on-site, the employer also runs a subsidized cafeteria and provides support with the daily commute for staff based further out.
For a role at this seniority and pay level, the compensation here is competitive with similar AEM openings in larger metro cities, which the employer has deliberately used to attract experienced developers who might otherwise default to relocating to Bangalore or Pune for a comparable title.
The team and how things run
This role sits within a mid-sized engineering group that supports several client-facing sites built on AEM, rather than one single product. Work is distributed across those sites based on who has the most relevant context, so a developer here ends up working on a genuinely varied set of implementations over time.
Thaltej, along SG Highway, has become one of Ahmedabad's more active commercial and IT corridors, with reasonable access from most parts of the city and enough restaurants and everyday amenities nearby that settling into the area doesn't take long.
Senior developers are expected to weigh in on architectural decisions early, before a feature is built the wrong way and requires costly rework later. That input is taken seriously here, not treated as a formality before decisions that were already made elsewhere.
Disagreement over the technical approach happens openly rather than being smoothed over in meetings and relitigated afterward in side conversations. It's a working style that suits someone comfortable making a direct case for an architectural decision and, just as importantly, comfortable being talked out of one when someone else's reasoning is stronger.
Applying
Send a resume that specifies the AEM version, deployment model, and specific components or workflows you've built, rather than a general summary of CMS experience. The interview includes a hands-on round working directly in an AEM instance, since that reveals real platform fluency far better than conceptual questions alone.
Candidates whose recent AEM work has been on-premise rather than Cloud Service shouldn't count themselves out. The core development skills carry over well, and the team has said they're comfortable bringing someone up to speed on the Cloud Service specifics as long as the underlying AEM instincts are strong.
