HCLTech is a global technology company, home to 219,000+ people across 54 countries, delivering industry-leading capabilities centered on digital, engineering and cloud, powered by a broad portfolio of technology services and products. We work with clients across all major verticals, providing industry solutions for Financial Services, Manufacturing, Life Sciences and Healthcare, Technology and Services, Telecom and Media, Retail and CPG, and Public Services. Consolidated revenues as of $13+ billion.

For more information on how we process your personal data, please refer to HCLTech’ s Candidate Data Privacy Notice.

Assignment

We are looking for a colleague to contribute to the Achmea Multi-brand Design System team, responsible for the Kotlin Multiplatform / Compose Multiplatform component library serving multiple Achmea brands (Centraal Beheer, Interpolis, FBTO, Avero). The team works in a cross-platform monorepo alongside web (React, Angular) and iOS (SwiftUI) colleagues.

Responsibilities include:

• Building and maintaining reusable Compose Multiplatform UI components for Android, iOS and Desktop
• Maintaining the multi-brand theming architecture — one codebase, multiple brand skins
• Maintaining the design token pipeline — transforming Figma tokens into Kotlin via Style Dictionary and custom MJS scripts
• Developing custom Gradle build infrastructure (convention plugins, code generation tasks)
• UI test automation using Appium/Selenium on BrowserStack for cross-platform visual and functional testing
• Publishing the library to Azure Artifacts (Maven)
• Life Cycle Management — keeping up with Kotlin, Compose and platform releases
• Collaborating cross-platform on shared component APIs, token structures and design decisions

Soft skills

• Communication: Articulate ideas clearly across platform boundaries (web, iOS, Android). Give and receive constructive feedback. Speak up and share opinions
• Problem-Solving: Think critically about complex multi-platform, multi-brand issues
• Adaptability: Comfortable working outside your primary domain (e.g. MJS scripting, iOS debugging)
• Teamwork: Collaborate closely, including pair programming. Contribute positively to team dynamics
• Attention to Detail: Pixel-perfect implementation of design specs; understand semantic vs. primitive tokens
• Cross-platform thinking: Reason about API decisions that affect web, iOS and Android simultaneously
• Ownership: Drive features end-to-end, from token generation through implementation to publishing
• Continuous Learning: Stay current with the rapidly evolving KMP and Compose Multiplatform ecosystem

Must haves

• Kotlin (advanced)
• Kotlin Multiplatform (KMP) — shared code targeting Android, iOS and JVM Desktop
• Compose Multiplatform (JetBrains) — multi-target UI components
• Material 3 — theming, color schemes, typography, component customization
• Gradle (Kotlin DSL) — multi-module project configuration
• GIT
• Clean architecture — designing maintainable, modular library APIs
• Attention to UX/design detail

Nice to haves

• Gradle convention plugins / custom plugin development — the project heavily relies on custom plugins for brand config, code quality, publication and code generation
• Design tokens / Style Dictionary — understanding token hierarchies (primitives → semantic → component) and the Style Dictionary tool that transforms them into platform code
• Node.js / MJS scripting — the token build pipeline uses custom ES module scripts (.mjs) running via Gradle to configure Style Dictionary transforms and generate Kotlin code from Figma JSON tokens. Requires comfort reading and modifying JavaScript
• AI Agentic coding
• Firebase App Distribution
• UI test automation — Appium and Selenium on BrowserStack for cross-platform visual/functional testing
• Multi-brand / white-label architecture — supporting 5+ brands from a single codebase
• CI/CD with Azure DevOps (GH in future)
• iOS basics (Xcode, SwiftUI) — for debugging KMP iOS targets
• SAFe / Agile / Scrum