AEM Cloud Engineer

About The Role Bridgestone GCC is looking for a hands-on Adobe technologist who goes deeper than any single product. You will be the engineer who understands how content, customer data, and journeys connect across the Adobe Experience Cloud — from authoring and assets in AEM, to real-time customer profiles in AEP, to orchestrated communications in Adobe Journey Optimizer (AJO) and Adobe Campaign.

This is not a pure development seat and not a pure marketing-operations seat. You will build and support integrations across the Adobe stack, act as the technical bridge between platform, marketing, and business teams, and help teams across Bridgestone’s business units use these tools to their full potential. You should be equally comfortable debugging an AEM OSGi service, tracing a profile ingestion issue in AEP, and walking a marketing team through why their AJO journey isn’t triggering.

Key Accountabilities

• Design, build, and support integrations between AEM (Sites/Assets, AEMaaCS) and the wider Adobe Experience Cloud — AEP, AJO, Adobe Campaign, Adobe Analytics, Adobe Target — as well as external systems via APIs and event-driven patterns.
• Serve as the technical subject-matter expert for content and journey tooling: evaluate use cases, recommend the right Adobe capability for each business need, and prevent teams from rebuilding what the platform already provides.
• Configure and maintain AEP data collection and profile foundations: XDM schemas, datasets, identity namespaces and merge policies, Web SDK / datastreams, and source and destination connectors.
• Build, test, and troubleshoot journeys and campaigns in AJO and Adobe Campaign, including audience activation from Real-Time CDP, transactional messaging, and content personalization sourced from AEM.
• Enable and coach business unit teams (authors, marketers, analysts) — create documentation, run enablement sessions, and drive adoption of capabilities such as Content Fragments, Dynamic Media, GenStudio, and Adobe’s AI-assisted and agentic features as they mature.
• Partner with onshore stakeholders, product owners, and architects; participate in Scrum ceremonies; and ensure quality, well-documented deliverables in Bridgestone toolsets.
• Monitor, triage, and resolve cross-platform issues — data ingestion failures, identity and profile discrepancies, delivery and deliverability problems, and content sync issues between environments.
• Champion governance: consent and privacy handling (GDPR/CCPA), data hygiene, naming standards, and permission models across the Adobe ecosystem.

Expected Technical Expertise

• Adobe Experience Manager (AEM) — strong hands-on depth required
• 4+ years developing on AEM 6.5 and/or AEM as a Cloud Service: components, templates, Sling Models, OSGi services, HTL, Content Fragments and GraphQL/headless delivery, and Dispatcher fundamentals.
• AEM Assets / DAM: metadata schemas, processing profiles, Dynamic Media, Connected Assets, and asset delivery to downstream channels.
• Working knowledge of Cloud Manager CI/CD pipelines and the AEMaaCS operational model.
• Adobe Experience Platform (AEP) / Real-Time CDP — genuine implementation experience
• XDM schema design, dataset and identity configuration, and profile merge policies.
• Data ingestion via Web SDK (alloy.js), Edge datastreams, and batch/streaming sources; troubleshooting ingestion and identity-stitching issues.
• Segmentation and audience activation to destinations; understanding of governance labels and consent enforcement.
• Adobe Journey Optimizer (AJO)
• Building event-, segment-, and schedule-triggered journeys; channel surfaces and presets; message authoring with personalization from profile attributes and contextual events.
• Decisioning/Offers and experimentation concepts; integrating AEM-managed content and assets into AJO messages.
• Adobe Campaign (Classic or Standard / v8)
• Technical workflows, schema extensions, typologies, and delivery templates.
• SOAP/REST API integrations, data imports and exports, and deliverability troubleshooting.
• HTML, CSS, and JavaScript for email template development.
• Integration & Engineering Foundations
• Strong Java and JavaScript; REST API design and consumption; JSON/XML; OAuth/JWT server-to-server authentication with Adobe I/O.
• Adobe Developer Console: projects, API credentials, Adobe I/O Events, and App Builder (Runtime actions) for custom integrations.
• Git-based workflows, CI/CD concepts, and comfort with automation scripting.
• Good to Have
• Adobe Analytics / Customer Journey Analytics (CJA) and tag management via Adobe Launch (Tags).
• Adobe Target, Marketo, or Workfront / Workfront Fusion exposure.
• Familiarity with Adobe’s AI and agentic roadmap: AEM Sites Optimizer, GenStudio for Performance Marketing, AEP AI Assistant, and Agent Orchestrator.
• Adobe certifications at Professional or Expert level (AEM Sites Developer, AEP / Real-Time CDP, AJO, or Campaign).
• Exposure to cloud platforms (AWS or Azure) and CDN, dispatcher, and web-tier concepts.

Minimum Requirements

• 6+ years of overall IT experience in web or marketing-technology engineering, of which 4+ years are hands-on with AEM and at least 1–2 years with AEP, AJO, and/or Adobe Campaign in real implementations — build, integration, or support ownership, not end-user or admin exposure alone.
• Demonstrated delivery of at least one cross-product integration (for example AEM ↔ AEP/AJO content and data flows, Campaign ↔ CRM synchronization, or Assets ↔ downstream channel delivery).
• Strong communication skills; able to translate between technical teams and marketing or business stakeholders, and to present recommendations up the organization.
• Experience working in global, distributed onshore/offshore teams and in Agile delivery.
• Ability to work independently under limited supervision, own problems end-to-end, and document solutions for reuse.
• Bachelor’s degree in Computer Science, Engineering, or equivalent practical experience.

What Sets You Apart

• You can explain why an integration was designed a certain way, not just that you worked on a project that had one.
• You have debugged production issues across product boundaries — a segment not activating, a profile not stitching, a delivery not rendering — and can walk through the root cause.
• You enjoy teaching. Teams come to you to understand what the platform can do, and you make them self-sufficient rather than dependent.