Frontend Developer

This role suits a frontend engineer who wants to build a meaningful healthcare product—developing a Nuxt- and TypeScript-based medication management platform, collaborating closely with product and backend teams, contributing to performance, refactoring, and reliability improvements, and working in a modern, fast-moving environment where clean architecture, testing, teamwork, and user-centric execution directly support safer, more efficient clinical workflows.

1. What is your experience with Nuxt and how do you structure a mid-sized Nuxt application?
   I organize a Nuxt app by clear separation of pages, components, composables, and stores (Pinia), use layouts for shared chrome, plugins for cross-cutting concerns, and rely on Nuxt’s routing and server-side features to keep the structure predictable and scalable.

2. How do you manage state in a Vue/Nuxt application using Pinia?
   I create domain-oriented stores with typed state, getters, and actions, avoid tightly coupling stores to components, and use Pinia’s devtools and plugins for persistence or caching when needed.

3. How do you ensure type safety when using TypeScript in a Vue 3 / Nuxt project?
   I strictly type props, emits, and store state, enable strict mode in TS config, use defineProps/defineEmits helpers with generics, and rely on shared interfaces for API responses to prevent runtime surprises.

4. Can you describe your approach to end-to-end testing with Cypress in a production web app?
   I focus Cypress tests on critical user journeys (login, medication workflows, ordering), stub network calls when appropriate, run tests in CI on every merge, and keep test data deterministic to avoid flaky results.

5. How do you integrate a Nuxt frontend with a RESTful backend API reliably and securely?
   I centralize API calls in service modules or composables, handle auth tokens securely, standardize error handling and response mapping, and use interceptors or Nuxt plugins to attach headers and log issues.

6. How do you optimize performance in a Vue/Nuxt application, especially for users in healthcare environments?
   I use code-splitting and lazy loading for heavy routes, leverage server-side rendering or static generation, minimize unnecessary reactivity, and regularly profile with browser devtools and Lighthouse to catch bottlenecks.

7. Describe your workflow with Git and GitHub when collaborating in a team.
   I work with feature branches, small focused pull requests, meaningful commit messages, code reviews, and protected main branches, and I use GitHub Actions or similar CI to automatically run tests and checks.

8. How would you approach refactoring a legacy component that has grown too large and complex?
   I first add or improve tests around current behavior, then gradually extract smaller presentational and logic components or composables, reducing props and side effects while keeping the API stable for callers.

9. What considerations are important when building UI for medication management and professional caregivers?
   I prioritize clarity and safety: clear hierarchy, unambiguous labels, strong validation and confirmation flows, accessibility, and avoiding risky interactions like accidental deletions or silent data changes.

10. Have you worked with backend technologies like PHP/Laravel and how does that help you as a frontend developer?
    Yes, experience with PHP/Laravel helps me design better API contracts, understand backend constraints and validation, and collaborate more effectively on performance, pagination, and error-handling behavior.

hellomed is hiring a Frontend Developer (Remote in Germany/Spain or onsite in Berlin) to help build and evolve their Nuxt-based web application that powers digital medication management for professional caregivers. You’ll work closely with product and backend teams implementing features in TypeScript, Nuxt/Vue, and Pinia, writing end-to-end tests with Cypress, and integrating with REST APIs while proactively improving performance and code quality. The role calls for 3–5 years of JavaScript/TypeScript experience, solid Git/GitHub collaboration skills, and bonus points for backend knowledge (PHP, Laravel, MySQL, unit tests). You’ll join a mission-driven team aiming to drastically reduce medication errors in care settings, with a full-time permanent contract, fair compensation, flexible choice between Berlin office or home office in Germany/Spain, flat hierarchies, and regular team events at the Berlin HQ.