Full Stack Developer

Role Description

We're looking for a Full Stack Developer (AEM) who cares about how they work as much as the work itself. You'll help build web projects for luxury hotel brands on AEM as a Cloud Service. Beyond writing clean code, you'll act as a true extension of both our team and our clients' teams, where craftsmanship, clear communication, and ownership are central to the job.

The technical requirements are significant, and we cover them in detail below. But because we work so closely with our clients, the way you communicate, collaborate, and take ownership has a direct impact on the experience we deliver. For this reason, we prioritize those qualities first.

Qualifications

• A clear, proactive communicator.
• Collaborative by nature.
• You take ownership.
• Detail-oriented and quality-focused.
• Curious and a strong problem-solver.
• Client-minded.
• Self-directed and accountable in a hybrid setup.
• Culturally aware.

Requirements

• Must have:
• OOP principles (SOLID, KISS)
• Git, Maven, Unit Testing, TDD, JUnit, Clean Code, Code Quality, SonarQube
• AEM core:
• AEM Cloud vs. AEM on-premise: comparison, pros and cons
• AEM MVC Model: OSGi Service → Sling Model → HTL/Sightly
• Core AEM principles: Sling, JCR, OSGi
• REST Services
• Resource Resolving in AEM (override, overlay, extending)
• Touch UI (dialogs, inheritance, validations, dynamic dialogs, custom dialog components)
• Client Libraries (what they are, why and how they work in AEM, including embedding, dependencies, and debugging)
• Sling Servlets (how they work, AEM "global" servlet examples)
• AEM Events & Handling (listeners, observers, JCR events, Sling Jobs, AEM Workflows)
• AEM queries & indexes (pros, cons, best practices, what to avoid and why)
• AEM system console: bundles, components, Sling configuration, logging
• AEM Runmodes (what and why; how to configure an OSGi service for a specific runmode)
• AEM ACLs, User Management
• Sling API vs. JCR API
• AEM Templates (structure, policies, initial content)
• AEM Dispatcher (what it is, why to use it, set-up, configuration, caching)
• AEM Troubleshooting
• AEM Assets processing (Dynamic Media and Scene7)
• AEM Replication and Content distribution
• AEM MSM: live copy & language copy
• Nice to have:
• JavaScript ES6+ (TypeScript and a modular approach are a plus)
• HTML, CSS, SCSS
• Bootstrap 5+
• Working with REST API, JSON, AJAX
• Sling HTL
• Understanding of webpack or parcel principles
• Working with npm scripts
• UI component libraries
• Ability to work with third-party libraries (e.g. Swiper)
• Fancybox dynamic library
• Git

Benefits

• Fully remote work format
• Strong, professional, friendly team
• Professional development