Our Tech Stack: Typescript, React, Vite, Cypress, GraphQL, Node.
Why do we need this role?
Candis is growing and so is our Frontend ambition. We are investing in more Engineering power across our product teams, and this role is part of that. More Frontend capacity means more features shipped, more domains covered and more room for our Engineers to drive the Frontend chapter forward. We are looking for someone who can come in, contribute, and grow with us.
What makes this role exciting?
You will join team Achilles, one of the most active product teams at Candis right now, working predominantly on brand new features. The tech stack is modern and deliberately kept that way. If you spot something ageing out, you can raise it, propose the upgrade and lead it yourself with no one blocking you because of a preference for stability over progress. Candis genuinely believes in engineer agency: if you see a repeated problem across the codebase, bring it to the Frontend Chapter and propose a fix, with no one telling you, no.
Growth also makes this role exciting. We are not a company where career progression happens by waiting in a queue. Your team lead will run structured, regular one-on-ones focused on your competency growth and what it takes to reach the next level.
What are the biggest challenges?
Things can change at Candis, and they can change fast. The way a component looks or works can be revised multiple times in a single quarter as product and design sharpen the vision, so you need to be the kind of person who finds that energising rather than exhausting. There is also a level of cross-team coordination that takes active effort: multiple squads often work on closely related domains simultaneously, and the responsibility for syncing sits partly with you. Spotting that another team is touching shared ground and proactively reaching out to align is expected, not exceptional. On the technical side, some legacy test infrastructure has accumulated tech debt and will need to be reworked as part of ongoing modernisation, meaning you will occasionally need to navigate imperfect foundations on your way to shipping clean work.
What would be achieved over 6 months? haben?
In the first 30 days: Complete company onboarding, merge your first pull requests, and start building familiarity with the Achilles codebase and domain.
By 60 days: Attend Frontend Chapter meetings regularly, have shipped at least one meaningful feature, and be able to work across two full delivery cycles.
By 90 days: Operate with little to no supervision on most tasks, use AI tooling to offload repetitive work such as routine bug fixes, and be a recognisable cross-team collaborator.
By month six: Have been the driving force behind at least one shipped feature, contribute actively to Frontend Chapter discussions and be on a clear trajectory toward a senior competency level.
