Senior, Software Engineering (AEM + Workfront/Fusion)

DEPT®•New York, NY

2d•$108,600 - $170,000•Remote

About The Position

We are looking for a Software Engineer (P2), AEM Backend to own backend workstreams on AEM website and platform projects. You will build the services, content structures, workflows, and integrations behind experiences used by real people, taking semi-defined problems through clarification, implementation, testing, and release. This role reports into our Software Engineering practice in the US. You will support a Tech Lead/Principal Software Engineer, CMS (AEM) Architect, frontend engineers, QA, DevOps, content specialists, and client stakeholders. Some days that means creating a Touch UI, Universal Editor Content model, Sling Model, Servlet, App Builder apps or an OSGi service. Other days it means turning an incomplete requirement into a plan, tracing a slow request, improving a workflow, integrating an external API, or explaining to the team why a tempting shortcut will make the next release harder. You do not need to know every corner of Adobe before you start. You do need solid engineering habits, curiosity about how AEM works, and the willingness to learn from the people around you.

Requirements

3+ years of backend or full-stack software development experience, or equivalent practical experience building and supporting production systems.
Professional experience with Java and object-oriented software development.
Hands-on experience with AEM backend development and production AEM projects, including configuring Edge Delivery Services, working with the Universal Editor, and developing or integrating with Adobe App Builder.
Experience delivering end-to-end CMS (AEM) websites and participating in CMS (AEM) migration or re-platforming projects is required.
Working knowledge of Sling, OSGi, JCR/Oak, Sling Models, servlets, HTL integration points, workflows, and Maven.
Experience with REST APIs, JSON, authentication, input validation, and integrating with external services.
Familiarity with Git, pull requests, automated builds, and testing practices.
The ability to take an ambiguous problem, research independently, read logs, and debug across application, repository, dispatcher, and integration layers.
Care for performance, security, accessibility, and maintainability, even when the immediate ticket seems small.
A collaborative approach. You can take direction, offer a different view respectfully, and communicate when you are blocked.
Proven experience utilizing AEM Assets (DAM), configuring asset search facets, and managing creative workflows across Creative Cloud for Enterprise and Adobe Express.
Proven experience with Workfront Fusion for integration and transaction orchestration, alongside a solid understanding of the broader Adobe content supply chain and marketing ecosystem (e.g., Workfront Planning, Frame.io, Marketo, Target, AJO, AEP).

Nice To Haves

Experience with AEM Cloud Manager, Dispatcher, or headless delivery.
Experience with Adobe Commerce, App Builder, API Mesh, analytics, or marketing platform integrations.
Familiarity with GraphQL, event-driven integrations, Docker, CI/CD, or observability tools.
Adobe certification, a computer science background, or a portfolio of relevant work.
Hands-on experience leveraging GenAI productivity tools (such as Gemini CLI, Claude Code, or Codex) within your development workflow, alongside the drive to push their boundaries to accelerate team delivery.
A practical understanding of core LLM concepts and the judgment to identify where AI solutions create real value.

Responsibilities

Own backend workstreams: Take semi-defined problems, resolve open questions, create a plan and estimate, and drive the work through implementation, testing, and release.
Develop AEM features: Build authoring interfaces (Touch UI dialogs, Universal Editor etc.), Components, Blocks, Java services, Sling Models, servlets, schedulers, workflows, event handlers, and APIs that support real author and customer experiences.
Model content well: Implement content structures, Universal Editor content models, templates, blocks/components, permissions, and workflows that are understandable to authors and maintainable by engineers.
Build integrations: Connect AEM to APIs and other enterprise systems and datasources using REST or GraphQL, App Builder Apps, with appropriate authentication, validation, retries, timeouts, logging, and failure handling.
Write code that can be changed: Follow established patterns for OSGi configuration, dependency injection, separation of concerns, error handling, and secure development.
Test your work: Create unit and integration tests, contribute to automated test coverage, and investigate failures rather than working around them.
Work through the full lifecycle: Participate in refinement, implementation, code review, UAT support, release preparation, launch, and hypercare.
Diagnose real problems: Use logs, metrics, traces, repository inspection, and local reproduction to find the cause of defects and performance issues.
Collaborate openly: Ask for help early, explain your thinking, review teammates' code thoughtfully, help in backend and frontend integration, help/guide frontend engineers (if needed), communicate directly with working-level client stakeholders, and keep documentation current when a decision will matter later.
Support cloud delivery: Work with Cloud Manager, CI/CD pipelines, Dispatcher configuration, environment variables, secrets, and deployment diagnostics under the guidance of the Tech Lead and DevOps.
Learn the Adobe platform: Build practical fluency in AEM as a Cloud Service, AEM Sites and Assets, Edge Delivery Services configurations and the Adobe tools relevant to the engagement.