Senior AEM Engineer

Senior Engineer AEM Connector

AI is changing how the world communicates — and LILT is leading that transformation. We're on a mission to make the world's information accessible to everyone, regardless of the language they speak. We use cutting-edge AI, machine translation, and human-in-the-loop expertise to translate content faster, more accurately, and more cost-effectively without compromising on brand, voice, or quality.

LILT's AEM Connector enables enterprise customers to push and pull AEM content — Sites pages, Content Fragments, Assets, and Tags — directly through Lilt's translation platform, supporting both Instant Translate and Verified Translation workflows. Every customer who runs AEM has a unique content topology, and making the connector work reliably across that diversity is a real engineering challenge. You will own the connector end-to-end: architecture, product roadmap, and the hands-on technical advisory work that ensures enterprise deployments succeed in the field.

This is a high-impact, high-visibility role on a product with a growing customer base that includes some of the world's largest global brands.

As the senior engineer on the AEM Connector, you will drive the long-term technical strategy for the connector while working directly with enterprise customers — configuring implementations, diagnosing production issues, and establishing the best practices that define how Lilt and AEM work together. You will partner with Solutions and Account teams, train internal staff, and build the validation and guard logic that prevents customer-specific content structure quirks from becoming production incidents.

You will ship new capabilities, validate, and define the canonical site structures the connector explicitly supports.

• Own the connector architecture and long-term product roadmap for the Lilt AEM Connector
• Define and maintain the canonical AEM site structures the connector explicitly supports — and advise customers on how their specific topology maps to those structures (or where it diverges)
• Guide customers through AEM Translation Integration Framework setup: language masters, language copies, MSM/Live Copy topology, Experience Fragment hierarchies, and cloud configurations relative to Lilt's connector
• Work directly with enterprise customers to capture feature requirements, validate configurations, and establish long-term best practices
• Define and document canonical patterns for translation project creation, Content Fragment localization, DAM asset translation, and auto-archiving workflows
• Partner with Solutions and Account teams for pre-sales technical evaluation, onboarding, and escalation triage
• Train and enable internal teams on connector capabilities, OSGi configuration options, and troubleshooting patterns
• Deliver new connector capabilities through the full cycle: CI (Git Hub Actions), E2E Cypress tests, package deployment via Cloud Manager and RDE

• 5+ years of professional AEM development on AEM Cloud Service (AEMaaCS), with a track record of owning a production AEM implementation end-to-end — architecture, implementation, deployment, and field reliability
• Deep knowledge of AEM content architecture: JCR/Sling resource model, OSGi service components, AEM Sites, DAM, and Content Fragments
• Java/OSGi bundle authoring: services, schedulers, Sling jobs, event listeners, servlets, and Sling Models
• Deep understanding of AEM Translation Integration Framework: language master setup, language copies, Translation Projects, Translation Jobs, and MSM/Live Copy inheritance hierarchies
• Fluency in AEM content topology nuances — including where standard Adobe guidance does not apply (e.g., Experience Fragments outside language master hierarchies, non-page trunk nodes, customer-specific site structures that would never appear in Adobe's sample sites)
• Ability to debug JCR node type conflicts and content tree issues across diverse customer environments
• Customer-facing technical experience: configuring AEM environments, leading implementation workshops, writing best-practices documentation, and guiding enterprise rollouts
• Comfort reasoning about complex multilingual…