AEM Architect, Front-End & Information Architecture

The Role

This is not an authoring role, and it is not the usual Java-and-Sling AEM architect role either. You are a front-end engineer who thinks in information architecture. You decide how a site's content and data are structured, then you engineer the pipelines that keep them that way at scale, so the team ships through automation instead of logging into an authoring UI to hand-edit a thousand pages.

• Architect the information. Design the content model, taxonomy, metadata, and URL structure for large multi-brand sites, so content is findable by people, reusable by components, and legible to machines.
• Engineer the front end. Build fast, accessible, standards-based experiences in modern JavaScript, HTML, and CSS on AEM Edge Delivery Services, holding near-perfect Core Web Vitals as a build requirement rather than a cleanup project.
• Automate the content operations. Build the pipelines that handle structured data and JSON-LD, global updates aligned to components, bulk operations, migrations, and validation, using AI where it genuinely earns its place.
• Make the site legible to machines. Own structured data and semantic markup, and the technical foundation for SEO and generative engine optimization, so the content is retrievable by search engines and by LLMs.
• Set the standard. Define the component contracts, documentation, and authoring model that let non-technical teams publish safely without breaking the system.

Your First 90 Days

The content model you inherit decides how much of the next two years is rework.

• Weeks 1-3. Audit the model. Content types, templates, taxonomy, and URL structure, plus an honest list of what breaks under migration and what depends on systems that are being switched off.
• Weeks 4-8. Build, with the gates on. Ship real pages with Core Web Vitals and WCAG enforced at build time, not queued as a cleanup ticket for later.
• Weeks 9-12. Hand over the keys. Component contracts, authoring documentation, and the automation that lets non-technical teams publish without breaking the system.

Why 5th Revolution

• The Work Other Firms Can't Offer — We challenge the status quo and put data and technology first, so your energy goes into the outcome and the growth it creates, not the org chart.
• Constant challenge from people at your level.
• Actually build, at Fortune 100 scale.
• Go wide, not siloed.
• All technology, none of the politics.
• Driven by results, not headcount or hours.

Compensation & Engagement

• W-2 from day one. Hourly to start, converting to salaried. You are a 5th Revolution employee from your first day, not an agency placement and not a 1099 contractor.
• You start hourly and overtime-eligible on a longer-term engagement, and convert to a salaried role from there. We typically evaluate conversion within the first six to nine months. Conversion depends on mutual fit and on business conditions, so we will not promise a date we cannot control, and we will tell you where you stand rather than leave you guessing.
• Competitive rate; total compensation reflects skill and impact, not just years.
• Annual certification and professional-development budget; conference attendance and speaking opportunities.
• Fully remote, up to ~10% travel. During the hourly phase your schedule is agreed in advance and all hours worked are recorded and paid, including overtime.
• Latest tools, hardware, and AI-enabled development environments.
• A small, senior team. You work directly with the principal architect on Fortune 100 accounts, not through layers of account management.

Pay

During the initial hourly phase, this role pays $85 to $145 per hour. On conversion to a salaried role, the base salary range is $115,000 to $205,000 per year.

Be plain about the arithmetic. The two are not a like-for-like comparison. Hourly, you are non-exempt: you are paid for every hour you work, overtime included, and you carry the variability. Salaried, you are paid whether or not you are on a billable engagement, and overtime no longer applies. One trades stability for upside, the other trades upside for stability, which is exactly the choice conversion represents. These are good-faith ranges. Actual compensation depends on experience, skills, and location.

Benefits

• Paid sick leave
• Annual certification and professional-development budget

At-will. Employment with 5th Revolution is at will. Either you or 5th Revolution may end it at any time, with or without cause or notice. Nothing on this page is an offer, a contract, or a guarantee of employment, of any term of employment, of conversion, or of any specific compensation. Any offer we make will be in writing and will govern.

The Five Points

We hold every hire to the same five points, the five points of the 5th Revolution star. No one point carries a hire on its own, and no one point is a formality. If you are strong on most of them and straight with us about the rest, apply anyway.

• Business Communication & Leadership — You own the room and the outcome. You move fluidly between executive teams and delivery, framing everything in business value, and setting a direction cross-functional teams want to execute. Translate fluidly between executive and technical audiences. Frame every decision in business value. Lead cross-functional delivery teams.
• Technical Breadth & Depth — A front-end engineer first, with genuine information-architecture command and an automation instinct that refuses repetitive manual work. Deep front-end engineering: modern JavaScript, HTML5, CSS3, design systems and component libraries, performance budgets, Core Web Vitals, and WCAG accessibility. Information architecture: content modeling, taxonomy, metadata strategy, structured data and JSON-LD, and multi-brand, multi-locale site and URL structure. AEM across the stack: AEM (on-premise or as a Cloud Service), AEM Edge Delivery Services (document-based and Universal Editor authoring), and Adobe App Builder to automate content operations at scale.
• Strategic Thinking — You get from "we need a CDP" to the real business goals, a sequenced roadmap, and an ROI case that wins executive budget, sequencing for fastest measurable value, not activity. Turn vague asks into goals, roadmap, and an ROI case. Scope, size against product licensing, and set realistic timelines. Protect scope, schedule, and budget when reality pushes back.
• Drive to Learn & Grow, Together — You never accept the status quo. You stay current because you are genuinely curious, and you level up the whole team by learning alongside your peers. Genuinely curious, always current. Level up the whole team, not just yourself. Best approach wins, regardless of title or tenure.
• Relevant Experience — You have owned both the front end and the information architecture of large content sites, and you have automated your way out of repetitive authoring instead of staffing around it. 2+ years hands-on AEM, or 5+ years in closely related front-end engineering and information architecture. Demonstrated ownership of content modeling and site information architecture, not just component builds. Shipped real content automation: migrations, bulk operations, structured-data pipelines, or authoring tooling.