> Markdown version of [/jobs/ext/4024881-adobe-multi-solution-architect](https://www.wearedevelopers.com/jobs/ext/4024881-adobe-multi-solution-architect). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Adobe Multi-Solution Architect - **Company:** Net2Source - **Location:** Houston, TX, United States (Remote available) - **Experience:** Expert - **Salary:** $177,944.0 - $188,344.0 - **Contract:** Permanent contract - **Skills:** Adobe Analytics, Adobe Creative Cloud, Adobe Experience Manager, Adobe Marketing Cloud, Application Programming Interfaces (APIs), Data Analysis, Audit Trail, Software Bug Management, Cloud Computing, Code Review, Information Systems, Continuous Integration, Data Validation, Data Governance, Data Retention, Global System for Mobile Communications, Key Management, Metadata, Cloud Services, Next.js, Requirements Management, Data Streaming, Strategies of Testing, Performance Testing, Postman, Adobe Campaign, ReactJS, Adobe Target, Build Management, Adobe, Data Lakes, Information Technology, Low Latency, Adobe Workfront, Marketo, Enterprise Integration, Graphql, Front End Software Development, Osgi, Api Design, Software Coding, Restful APIs - **Published:** October 30, 2026 - **Apply:** https://www.careerbuilder.com/job-details/adobe-multi-solution-architect-houston-tx--88ef224e-85a6-4af2-b1ff-eb9d8e549803 ## About the Role Adobe Product Family, Adobe Product Family, Technical Leadership, Data Analysis, Requirements Management, Cloud Computing, Enterprise Architecture, Content Delivery/Distribution, Data Collection, EDGE (Enhanced Data for GSM Evolution), · Bachelor's degree in Computer Science, Engineering, Information Systems, or equivalent practical experience. · 12+ years of overall technology experience, including 7+ years delivering Adobe Experience Cloud solutions in architect, lead engineer, or senior technical lead roles. · Demonstrated hands-on depth in AEM Sites and/or Assets plus strong architecture and implementation experience with AEP." ## Description ?The Adobe Multi-Solution Architect / Technical Lead is a senior, hands-on architecture leader responsible for designing and delivering enterprise-scale digital experience solutions across Adobe Experience Manager (AEM) and Adobe Experience Platform (AEP). The role translates business, content, data, analytics, and personalization requirements into secure, scalable, supportable architectures. It provides technical direction from discovery and solution design through build, release, stabilization, and ongoing optimization. This leader works across client stakeholders, product owners, enterprise architects, data teams, creative and content teams, and distributed engineering teams. The role may operate as the overall solution architect, AEM/AEP technical lead, or architecture lead within a broader Adobe Experience Cloud program. **Key Technologies** **Core:** AEM as a Cloud Service, AEM Sites, AEM Assets / DAM, Adobe Experience Platform, Real-Time CDP, Customer Journey Analytics, Adobe Journey Optimizer, Adobe Analytics, Adobe Experience Platform Data Collection, Tags, Web SDK, Edge Network **Supporting:** AEM 6.x, Edge Delivery Services, Adobe Target, Dynamic Media, Workfront, Adobe Campaign, Marketo Engage, GraphQL, REST APIs, event-driven integration, cloud services, CI/CD, identity, consent, security, observability **Key Responsibilities** · **Architecture and roadmap:** Define target-state and transition architectures spanning web experience, content and assets, data collection, customer profiles, analytics, personalization, journey orchestration, and downstream activation. · **AEM solution leadership:** Own AEM architecture for Sites and Assets, including component and template strategy, content models, authoring patterns, localization, multisite management, DAM governance, headless delivery, caching, performance, and upgrade or cloud migration approach. · **AEP solution leadership:** Lead AEP architecture for XDM schemas, datasets, identities and namespaces, sources, ingestion, Real-Time Customer Profile, audiences, destinations, data governance, consent, and activation. · **AEM-AEP integration:** Design how AEM experiences and content interact with AEP-powered data, audiences, analytics, decisioning, and activation using Data Collection, Web SDK, datastreams, Edge Network, APIs, and approved integration patterns. · **Technical design authority:** Produce and govern solution diagrams, integration designs, data flows, sequence diagrams, interface contracts, technical standards, NFRs, architecture decisions, and implementation guardrails. · **Hands-on technical leadership:** Guide engineers through design and build; review code and configuration; troubleshoot complex platform, integration, performance, and production issues; and lead technical spikes or proof-of-concepts. · **Delivery governance:** Establish development standards, branching and release strategy, quality gates, environment promotion, dependency management, defect triage, and technical risk management across onshore, nearshore, and offshore teams. · **Security and compliance:** Embed privacy, consent, least-privilege access, secure API patterns, secrets management, auditability, data retention, and enterprise security requirements into the solution. · **Discovery and stakeholder leadership:** Facilitate workshops, clarify use cases and success measures, challenge ambiguous requirements, explain trade-offs, and present recommendations to technical and executive audiences. · **Pre-sales and capability support:** Contribute to estimates, staffing models, solution shaping, proposals, architecture presentations, and reusable accelerators for Adobe Experience Cloud opportunities. **AEM Technical Expertise** · Architecture and delivery experience with AEM as a Cloud Service and working knowledge of AEM 6.x modernization or migration patterns. · AEM Sites: Sling, OSGi, JCR, HTL, editable templates, Core Components, Content Fragments, Experience Fragments, workflows, metadata, localization, and Multi Site Manager. · AEM Assets / DAM: asset taxonomy and metadata, ingestion, renditions, workflows, permissions, Dynamic Media, asset delivery, and integration with authoring and downstream channels. · Cloud Manager pipelines, environment strategy, deployment governance, automated quality gates, and cloud-ready development practices. · Dispatcher, CDN and caching strategy; security hardening; performance testing; capacity considerations; monitoring; and production troubleshooting. · Headless and hybrid architecture using Content Fragments, GraphQL, REST APIs, and front-end frameworks such as React or Next.js. · Experience with Edge Delivery Services is desirable for programs evaluating high-performance, document-based or composable delivery patterns. · Ability to define reusable component architecture, coding standards, test strategy, and authoring governance that balance speed, reuse, and maintainability. **AEP Technical Expertise** · XDM schema and data model design, datasets, data types, field groups, identity namespaces, merge policies, and profile enablement. · Batch, streaming, edge, and API-based ingestion patterns; source connectors; error handling; data validation; and reconciliation. · Adobe Experience Platform Data Collection, Tags, Web SDK, Mobile SDK concepts, datastreams, Edge Network, event forwarding, and migration from legacy client-side collection patterns. · Real-Time Customer Profile, audience definition and evaluation, segmentation approaches, destinations, activation, and audience lifecycle governance. · Real-Time CDP, Adobe Journey Optimizer, Customer Journey Analytics, and Adobe Analytics integration patterns and solution boundaries. · Consent and preference data, data usage labels and policies, governance controls, sandbox strategy, role-based access, monitoring, and operational support. · CJA data views, connections, calculated metrics, dimensions, identity considerations, and event-based cross-channel analysis. · AEP APIs, authentication patterns, Postman or equivalent API tooling, and automation for repeatable configuration and deployment where appropriate. **Cross-Solution Architecture Expectations** · Define the end-to-end experience flow from content creation and asset management through digital delivery, behavioral data collection, profile and audience creation, measurement, decisioning, and activation. · Clarify system-of-record ownership and platform boundaries across AEM, AEP, CRM, commerce, consent management, data lake or warehouse, identity providers, campaign platforms, and enterprise integration services. · Design for resiliency, latency, scalability, accessibility, SEO, observability, operability, cost awareness, and maintainable ownership after go-live. · Identify solution trade-offs such as edge versus server-side processing, batch versus streaming, native capability versus customization, and tightly coupled versus composable integration. · Ensure implementation designs are aligned to enterprise architecture standards and are traceable to business capabilities, use cases, functional requirements, and NFRs.