Design Engineer - m/f/d
Langdock
| Company | Langdock |
| Category | Engineering |
| Location | Berlin |
| Remote | On-site (inferred) |
| Employment | Not stated |
| Level | Not stated |
| Salary | EUR 90k–140k |
| Posted | 20 Apr 2026 |
| Last verified | 7 Aug 2026 |
| Source | Employer ATS (ashby) |
Description
HELP US CHANGE THE WAY THE WORLD WORKS
BUILD SOMETHING THAT MATTERS.
Langdock exists to change the way the world works, bridging the gap between what technology can do and what people actually do with it. We bring all leading AI models into one secure, model-agnostic platform and make them usable across entire organizations. Over 10,000 companies use our platform every day, from fast-growing startups to some of Europe's largest enterprises. Their employees open Langdock to draft strategies, analyze documents, or automate workflows. Helping them to work smarter, think more creatively, and reach their full potential.
ABOUT THE ROLE
Most companies separate design from engineering. Designers hand off Figma files, engineers implement them, and something gets lost in translation every time.
We do it differently. Our source of truth is not Figma. It is the code. It is how the product actually looks and feels in the browser. And the person who owns that is the Design Engineer.
You will hear about a problem from a product, develop the solution visually and technically, open a branch, build the full front end, pixel-perfect and production-ready, and either hand it off to a product engineer or take it all the way yourself. You are the person who makes sure Langdock looks and feels as sharp as it actually is.
This is not a role for someone who designs in isolation or codes without taste. It is for someone who does both and cares deeply about the result.
WHAT YOU WILL DO
- Own the UI end-to-end. When a new feature or page needs to exist, you build it. You take a problem, develop the visual and interaction solution, implement it in code, and ship something that looks exactly right.
- Set the visual bar. You have strong opinions about spacing, typography, motion, and hierarchy. You push back when something looks off, and you fix it when it does. Clean, minimal, and a little bit vibey. That is the aesthetic you default to and defend.
- Build in code, not in mockups. You work primarily in Next.js and React, using Tailwind to implement designs directly in the codebase. Figma is a tool for exploration, not the final word. The final word is the screen.
- Prototype fast. When the team needs to see an idea working, you build it. Fast and convincing enough to make a real decision.
- You are comfortable going full-stack when needed and ship end-to-end. You are comfortable enough with the back-end to wire up what your front end needs - whether that is writing Prisma queries, or building / modifying API routes. You do not need a backend engineer to finish your work. You will be seen as a full member of our engineering team.
- Collaborate closely with product and engineering. You sit at the intersection of both. You translate product thinking into interfaces and engineering constraints into design decisions.
WHAT MAKES THIS DIFFERENT
Langdock is a product that tens of thousands of people open every day to do their most important work. The quality of the interface is not a detail. It is part of the value.
You will work on a product where design quality is taken seriously, on a team small enough that your taste shapes what the product becomes. Every screen you ship is seen by real customers immediately.
We went from €1M to €15M+ ARR in one year. You will join early enough to shape how things work, with enough traction, customers, and product love already there.
YOU MIGHT BE A FIT IF…
- You have 1–2+ years of hands-on experience with React and Next.js and are completely comfortable building production UI and business logic in it.
- You design and prototype UI with Tailwind CSS and do not need a designer to tell you how something should look.
- You are proficient in Figma, but do not depend on it. You optionally use it to think or scribble; actual prototypes get built in code.
- You have full-stack familiarity - Supabase, Firebase, Postgres, Prisma, or similar experiences. You can handle back-end work