Want to know if this job is worth applying to?
Berlin, Deutschland
Onsite
Not Available
Langdock is the AI platform used by more than 10,000 companies to give employees secure access to the leading AI models, to build and share agents and to automate repetitive workflows. We have grown past $40M ARR while remaining a small team, and we care deeply about operating efficiently across the entire company.
For many enterprises, Langdock is becoming the place where most of the net-new work is produced. As people and agents create more documents, analyses, decisions, and automations inside AI interfaces, the context and data behind that work accumulate within Langdock. This gives us the opportunity to earn a larger role in their technology stack by building a platform they choose to rely on.
Our ambition is to build that platform for European enterprises while preserving their control over data, model providers, and deployment environments. We have made meaningful progress at the application layer, but much of the foundation beneath it still needs to be built.
You can watch the Meet the engineering team video to get a feeling for how we work.
Design Engineers own the experience and visual language of Langdock, then turn that design into working software. You take an ambiguous product problem from the user's workflow through information architecture, interaction design, visual execution, and production code.
The source of truth is the product, not a handoff. Figma is useful for exploration, but the decisive design work happens in React, where real data, latency, permissions, edge cases, and responsive behavior are visible. You are responsible for whether the final interaction is clear, coherent, and technically sound.
This role spans individual product surfaces and the systems behind them. You will shape major workflows yourself, build the component library and design system that raise the quality of work across the company, and help other engineers make better interface decisions.
Human-agent collaboration. Design how people give agents context, steer work in progress, approve actions, inspect tool calls, recover from failure, and review complex outputs. The challenge is to make powerful multi-step systems understandable without reducing the experience to another chat interface.
Dense enterprise workflows. Make permissions, governance, configuration, evaluations, and workspace administration understandable to occasional users without slowing down experts. Find the hierarchy and interaction model that preserve necessary complexity without making the product feel heavy.
Creating work with agents. Define the interfaces where people and agents produce and revise documents, analyses, spreadsheets, applications, and other structured work together. Show progress, changes, sources, and control clearly enough that users can understand and trust the result.
The design system. Build and evolve reusable components, interaction patterns, typography, motion, and layout principles that keep a growing product coherent. Make the high-quality choice the fastest choice for engineers working across the product.
Prototypes and production interfaces. Turn uncertain ideas into realistic software quickly enough to expose difficult interaction and technical questions before the team commits to an approach. Then implement responsive, accessible product surfaces in React and Tailwind CSS, going into the backend when a strong end-to-end result requires it.
Product storytelling. Apply the same visual standard to launches, product pages, demos, and other materials that explain what Langdock does. Work in code where appropriate and make sure the way we present the product matches the quality of the product itself.
TypeScript, React, Next.js, and Tailwind CSS in one Bazel monorepo
Node.js, PostgreSQL, and Prisma when work crosses into the backend
Figma for exploration
Linear for planning and GitHub for code review
You should be strong in the frontend stack and comfortable learning enough of the surrounding system to finish work end to end.
We operate with high trust and autonomy in squads of 3 to 4 engineers. A squad owns its roadmap, prioritization, technical decisions, and operation in production. Engineers are expected to find the context they need, ask for input when it improves the outcome, and move work forward without waiting for every next step to be assigned.
We align asynchronously before scheduling a meeting. Product requirement documents (PRDs) define the user problem, intended outcome, and constraints. Design documents make architectural boundaries, tradeoffs, failure modes, migrations, and rollouts explicit. People read and challenge the thinking asynchronously; once the context is shared, a short in-office discussion or whiteboard session usually resolves the remaining questions quickly.
We optimize for leverage. Engineers choose the AI tools that work for them, supported by clear ticket context, focused branches, automated tests, and AI review before human review. We also invest in observability, migration tooling, automated recovery, and runbooks so recurring product maintenance does not depend on someone remembering a manual step.
The engineer who ships a change owns it in production. If something breaks, you lead the fix.
You have designed and shipped production interfaces in React, Next.js, and Tailwind CSS.
You use Figma when useful, but prefer testing important design decisions in working software.
You can take an ambiguous problem through user flows, information architecture, interaction design, visual execution, and production code.
You have enough full-stack familiarity to handle backend work when the experience requires it.
You understand complex business-to-business software, either through professional experience or strong related portfolio work.
You have a strong, considered point of view on visual design and can explain your decisions.
You care about interaction details, including transitions, hover states, loading behavior, responsiveness, accessibility, and empty states.
You give direct, constructive feedback and help other engineers improve the quality of their interfaces.
You care about the people around you and contribute to a thoughtful working environment.
We want to see what you have built and designed. Please include at least one of the following with your application:
A Dribbble profile or screenshots or videos of interfaces you have designed and implemented.
A brief screen recording (2–5 minutes) that walks through a project you took from problem to shipped product, ideally a complete website or application. Explain your design decisions and the code behind them.
If you have not worked in business-to-business software as a service (B2B SaaS) before but have related experience, strong portfolio work is how you can make the case.
This is an in-office role at Greifswalder Strasse 212 in Berlin. We work together in person because it helps us build trust, develop shared context, and make decisions quickly.
Most engineers start around 8:30. We usually eat lunch together, and dinner is available for people who stay later. Running and gym are part of the routine for many of us.
You need an existing right to work in Germany. We do not currently sponsor visas.
The salary range for this role is €135,00–€200,000 gross per year. All roles include equity.
We will figure out the right level together based on your experience and scope. Levels are about the work you own, not your title or years of experience. Salaries are tied to levels, not negotiation.