Senior, Software Engineering (AEM + Workfront/Fusion)

Back to jobs Senior, Software Engineering (AEM + Workfront/Fusion) NY, US, CA, US, IL, US - Remote Apply WHY DEPT? We are a Growth Invention company built to help the world’s most ambitious brands grow faster. Operating at the intersection of technology and marketing, we create what is next by pioneering ideas, acting fast, and moving further because standing still just is not in our DNA. We are drawn to people who stay curious, move with intent, and never stop inventing. Our culture runs on three values: better together, relentlessly curious, and get sh*t done. It is how we work, how we grow, and how we make things that matter. At DEPT®, you will find the freedom to explore, the space to collaborate, and the trust to make a real impact for our clients, for each other, and for the world we are helping to build. THE ROLE 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. WHAT YOU"LL DO - 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.