Anchora – Content Practice  |  AI-First Delivery

We build AEM with AI in the loop - every ticket, every day. This role is for an engineer who already works that way & wants to build real depth across the AEM stack alongside senior engineers & architects. If AI tooling is still something you mean to get around to, this is not the one. If it is already how you work, & you want to get much better at it on real client engagements, keep reading.

Timezone Coverage: Supports Australia & New Zealand (ANZ) business hours

The Non-Negotiable: You Already Work AI-First

This is the part of the role we will not compromise on. Anchora sells AI, Data, MarTech & Content work - we cannot credibly sell AI-accelerated delivery to our clients if our own engineers still build the old way. We are not asking you to be an expert in it. We are asking that it is already how you work, & that you are actively getting better at it.

• AI tooling is part of your normal day - you use Claude, Claude Code, GitHub Copilot, Cursor or an equivalent as a matter of course - not occasionally, & not just for autocomplete.
• You use it beyond code - writing & maintaining tests, understanding unfamiliar codebases, drafting documentation & tickets, & speeding up analysis.
• You review before you commit - everything AI produces is checked, tested & understood before it goes near a pull request. You can explain every line you commit.
• You are getting better at it deliberately - you know what works for you now that did not six months ago, & why.
• You can show us - you will be asked for specific examples in your application, & to work this way in a live exercise.

Senior engineers here will help you sharpen your judgement on where to rely on AI & where not to - but you need to arrive with the habit already formed.

Tech Stack at a Glance

• AI Toolchain: Claude & Claude Code, GitHub Copilot, Cursor or equivalent; project context & rules files, reusable prompts, growing into agentic workflows
• Content Platform: AEM Sites, AEM Assets & DAM
• Backend: Java, Spring, OSGi, Sling, REST APIs
• Frontend: React JS (or equivalent), HTL/Sightly, component-based development
• Platform: AEM as a Cloud Service (AEMaaCS) – exposure, growing into ownership
• Engineering Practice: Git branching & pull requests, code review, Maven builds, CI/CD pipelines & quality gates
• Quality Engineering: Playwright, Cypress, or Selenium
• Ways of Working: Agile, Scrum ceremonies, AI-first delivery end to end

About Anchora

Anchora is a boutique Adobe-specialist & MarTech & AI consultancy, delivering Adobe Experience Manager (AEM), Data, & Digital Experience engagements for clients across financial services, government, tourism, retail, & beverages. Our Content Practice covers AEM Sites, AEM Assets & Content Hub, AEM Forms, & Edge Delivery Services (EDS), & we pride ourselves on senior, hands-on delivery rather than layered bench teams.

Role Overview

We are looking for a full stack engineer who wants to build real depth across the AEM stack - from frontend components through to backend services - while working closely with senior engineers & architects, & using AI to cover ground faster than a traditional learning curve allows. You will take ownership of features within a sprint, contribute to testing & quality, & grow into progressively more independent delivery as your experience builds.

Is This You?

• You've built components & features in AEM & want to go deeper
• You already lean on AI tooling daily, & you want to get sharper about when not to
• You like learning from senior engineers & architects, not just figuring it out alone
• You take feedback well & turn it into better code the next time
• You would rather ask early than quietly get stuck

Key Responsibilities

• Use AI coding tools as your default way of working across code, tests & documentation, with senior engineers helping you sharpen judgement on where to rely on them
• Use AI to get productive quickly on unfamiliar codebases & client domains, & to keep tests & documentation current rather than deferred
• Review, run & test everything AI produces before raising a pull request - you own the code you commit
• Bring what you learn back to the team: prompts, context files & patterns that made a real difference
• Build & maintain AEM Sites components, templates, & Sling Models under the guidance of senior engineers
• Configure & support AEM Assets, including Digital Asset Management (DAM) workflows
• Develop backend services in Java, contributing to integration work with enterprise systems
• Build componentised frontend experiences using React JS or an equivalent framework, applying design system & accessibility (WCAG 2.1 AA) guidance
• Work to the team's Git branching & pull request standards, & take part in code review as both author & reviewer
• Get your work through the CI/CD pipeline - resolve build failures, quality gate issues & failing tests rather than handing them on
• Write & maintain automated tests using Playwright, Cypress, or Selenium
• Support security testing activities & help remediate findings as directed
• Take ownership of features within a sprint, escalating design questions to senior engineers or architects
• Participate fully in Agile ceremonies – sprint planning, daily stand-ups, retrospectives, & showcases

Required Skills & Experience

• AI-First Delivery (the primary filter): Current, hands-on use of AI coding assistants (Claude / Claude Code, GitHub Copilot, Cursor or equivalent) as part of your normal working day, across code, tests & documentation; ability to explain & defend AI-generated code you commit. You will be asked for specific examples in your application & to work this way in a live exercise.

• Experience: 4–6+ years in full stack software engineering, with at least 2 years working on Adobe Experience Manager (AEM)

• AEM Platform Engineering: AEM Sites component & template development; Sling Models, HTL/Sightly, client libraries, & OSGi services

• Assets & DAM: Hands-on experience with AEM Assets, including Digital Asset Management (DAM) workflows & metadata basics

• Backend Development: Strong core Java (Java 8+), Spring, & RESTful API design

• Modern Frontend & Accessibility: React JS or an equivalent modern frontend framework (Angular, Vue); component-driven development; working awareness of WCAG 2.1 AA accessibility standards

• Quality Engineering: Experience with Playwright, Cypress, or Selenium for automated testing

• Delivery & Agile: Experience working in Agile teams, including active participation in Scrum ceremonies – sprint planning, stand-ups, retrospectives, & showcases

• Communication: Good written & verbal communication skills, & comfortable working closely with senior engineers, architects, & cross-functional teams

Nice to Have

• AI Tooling Beyond the Basics: Context & rules files, reusable prompt or skill libraries, MCP servers, custom agents, or automations you have built for yourself or your team
• AEM Headless & Content Discoverability: Content Fragments & GraphQL-based delivery; structured content modelling; awareness of llms.txt & Generative Engine Optimisation (GEO)
• Edge Delivery Services: Exposure to Adobe Edge Delivery Services (EDS) as an alternative authoring & delivery model
• Cloud, Hosting & Infrastructure: Exposure to AEM as a Cloud Service (AEMaaCS), Cloud Manager, Dispatcher, or CDN configuration
• Design Systems & Security: Component-based design systems & governance; exposure to security or penetration (PEN) testing practices
• Backend & CRM Integration: Exposure to integrating AEM with backend CRM platforms such as Salesforce or Dynamics, & with Adobe Analytics
• Adobe Certification: An Adobe Certification (e.g. AEM Sites Developer) is well regarded, though not required to apply
• Consulting Exposure: Prior experience in a client-facing consulting or agency environment
• Node JS & Microservices: Experience with Node.js or exposure to microservices architecture
• Other CMS & MarTech Platforms: Exposure to other content management systems (Sitecore, Drupal, headless CMS), Salesforce Commerce Cloud, Salesforce CRM, Adobe Target, AJO, CJA, Adobe Workfront, or Creative Cloud

How We Use AI - & Where We Draw the Line

Being AI-first is not the same as being uncritical. We hold a high bar on how AI is used, & we expect you to hold it with us.

• AI writes the first draft; you own the last one - you are accountable for everything you ship, regardless of what generated it.
• If you cannot explain it, you cannot commit it - code you cannot defend in review or debug under pressure does not go in.
• Client data & code go only where they are allowed to go - every engagement runs under Anchora's AI Usage Policy & the client's own AI terms, which set the approved tools & conditions for that project. No shortcuts, no personal accounts, no exceptions.
• Throughput at quality, not volume - AI that produces more code & more defects is a net loss. We measure outcomes, not lines.
• The tooling moves monthly - we expect you to keep up, form your own view, & bring what works back to the team.

What Success Looks Like

• AI Leverage: You get through more, & learn faster, because of how you work with AI - & the quality of what you commit does not drop to get there

• Team Collaboration: You pair well with senior engineers & architects, ask for help early, & share what you learn with the team

• Project Delivery: Sprint commitments are met with quality; you flag blockers as soon as they appear rather than at the last minute

• Proactive Communication: Status updates go out before they're asked for; you speak up in stand-up rather than staying quiet when something isn't working

• Attitude: You take feedback well, turn it into better work next time, & bring energy to solving hard problems

• Technical Craft: Your code, tests, & documentation are something the next engineer is glad to inherit

Don't Tick Every Box? Apply Anyway

We would rather hear from someone with the right attitude & a genuine appetite to learn than lose a great engineer over a skills checklist. If you meet most of the Must Have requirements & can show us how you learn & upskill quickly, we want your application. The one requirement we do not flex on is AI-first working - everything else is negotiable.

Culture Fit

Technical skill gets you shortlisted; culture fit gets you hired. We are looking for someone who takes ownership, communicates proactively, & genuinely enjoys working closely with clients & teammates – culture fit is assessed as a core requirement alongside technical capability, not an afterthought.

How to Apply

Please submit your CV along with a cover letter via this portal. Your application must:

• Address the Requirements - we want to see in your cover letter & CV how you meet each of the requirements outlined above. If you don't meet it exactly but think you have transferrable skills, explain what they are.
• Include a Cover Letter - applicants that do not submit a customised cover letter for this role will not be considered. The cover letter should include:
  • How you actually work with AI - be specific. Which tools, on what kind of work, what you have changed about how you use them over the last six months, & one example where AI clearly changed the outcome of a piece of work.
  • Why you are the right fit - including anything that does not come through in a CV - how you learn new technology, examples of teamwork or stakeholder interactions, or moments where your attitude made the difference on a project.

Applications that do not address these points will not progress.

Our Hiring Process

1. If you pass our screening requirements, which include checking the points above & answering the screening questions in the application portal, we will arrange an Initial Interview with the hiring manager.

2. If proceeding to the next stage, you will be sent a Technical Test to do in your own time. This is an AI-assisted technical exercise. You will use your own tooling - we are not interested in whether you can code with the tools switched off.

3. If you pass the Technical Test you will proceed to a Technical Interview with a tech lead on the team to review your your Technical Test, ask you questions about it, and potentially undertake a live debug+fixes exercise.

4. If proceeding to the next stage, you will undertake a Final Interview with other interviewers to check cultural fit & ask any final questions.

5. If proceeding, we will make a Verbal Offer & agree on employment terms.

6. We will then Check your References & complete a background check.

7. A formal employment offer & Contract will be signed by both parties if you pass your reference & background check.