> Markdown version of [/jobs/ext/3065299-full-stack-engineer](https://www.wearedevelopers.com/jobs/ext/3065299-full-stack-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Full Stack Engineer - **Company:** GlassDollar - **Location:** Berlin, Germany - **Contract:** Permanent contract - **Skills:** JavaScript (Programming Language), Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Relational Databases, Github, PostgreSQL, Node.Js, Prism (Software), Search Technologies, TypeScript, ReactJS, Large Language Models, Technical Debt, Backend, Material UI, Playwright, Sentry, Graphql, Front End Software Development, Terraform - **Published:** September 25, 2026 - **Apply:** https://www.xing.com/jobs/berlin-full-stack-engineer-158079207 ## About the Role You can take a problem further than the ticket. Work often starts with something incomplete, like "customers need a better way to manage X". You'll shape the problem with product, challenge assumptions, and decide what belongs in this iteration. Strong opinions about what we build, not only how, are expected here. You care about product. You want to know who you're building for, why the problem matters, and what success looks like. That context should shape your technical decisions. You have technical judgement. There is rarely one correct architecture. You know when the boring solution beats the ambitious one, when an abstraction helps and when it hides the problem, and when a small feature is about to create six months of technical debt. We expect you to reason about API boundaries, data models, permissions, performance, failure modes, testing, observability, and rollout, and to raise concerns with a clear argument attached., * Substantial production experience with TypeScript, React, and Node.js * Comfortable reasoning about relational databases, not just the ORM * Can independently take a feature from unclear starting point to production * Can read unfamiliar code without immediately proposing a rewrite Nice to have: * Experience with GraphQL, Prisma, or PostgreSQL at scale * Exposure to LLM APIs, embeddings, or vector search * Experience owning systems, not just features ## Description * Frontend: TypeScript, React, Material UI, Apollo Client, Playwright * Backend: Node.js, GraphQL, Prisma, PostgreSQL, Jest * Infrastructure: AWS, Terraform, GitHub Actions, Sentry * Increasingly: LLM APIs, embeddings, vector search, MCP, AI-assisted engineering workflows You don't need experience with every item. Reasoning about systems matters more to us than having memorised our exact stack., We're a small engineering team, so there are fewer places for responsibility to disappear and no chain of five people between you and a decision. We prefer written context over meetings the calendar invented, and working software over elaborate process. Quickly doesn't mean carelessly. Sometimes the fastest route is the simple version today, sometimes it's another day on a foundation twenty future features will sit on. Knowing which situation you're in is part of the job. Expect to ship to production very early. How we hire No seven-stage endurance test. No algorithm trivia disconnected from the work. 1. Intro. You, us, and whether this is the environment you're actually looking for. 2. Technical conversation. We go deep on something difficult you've built: the decisions, the alternatives, what you'd do differently now. 3. Technical assessment. Usually live coding on a realistic problem, sometimes a small proof of concept instead. We care how you think, not whether your solution matches ours. 4. Offer. If there's strong mutual conviction, we move. One last thing Job descriptions have a habit of producing candidates who optimise themselves against bullet points. Please don't. If you're reading this thinking "I can do most of this, but I haven't worked with MCP", apply. Strong fundamentals, meaningful software shipped, and a bias toward ownership are what we're looking for. The rest is learnable. ## Related Videos - [Build and Deploy a Fullstack App with Open Source Tooling](https://www.wearedevelopers.com/videos/775-build-and-deploy-a-fullstack-app-with-open-source-tooling) - [Putting the Graph In GraphQL With The Neo4j GraphQL Library](https://www.wearedevelopers.com/videos/257-putting-the-graph-in-graphql-with-the-neo4j-graphql-library) - [Innovating Developer Tools with AI: Insights from GitHub Next](https://www.wearedevelopers.com/videos/1268-innovating-developer-tools-with-ai-insights-from-github-next) - [From Doubt to Confidence: How Sentry Uses Verdaccio to Bulletproof SDK Releases](https://www.wearedevelopers.com/videos/739-from-doubt-to-confidence-how-sentry-uses-verdaccio-to-bulletproof-sdk-releases) - [GraphQL + Apollo + Next.js: A Lovely Trio](https://www.wearedevelopers.com/videos/311-graphql-apollo-next-js-a-lovely-trio) - [Bringing AI Model Testing and Prompt Management to Your Codebase with GitHub Models](https://www.wearedevelopers.com/videos/1536-bringing-ai-model-testing-and-prompt-management-to-your-codebase-with-github-models) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Fullstack developer salary in Germany [2023]](https://www.wearedevelopers.com/magazine/197-fullstack-developer-salary-in-germany-2023) - [Dev Digest 109 -Egg-citing things…](https://www.wearedevelopers.com/magazine/408-dev-digest-109-egg-citing-things) - [Dev Digest 131 - AI'm not sure about OSS](https://www.wearedevelopers.com/magazine/472-dev-digest-131-ai-m-not-sure-about-oss) - [Dev Digest 119 - ❤️ === ❤️](https://www.wearedevelopers.com/magazine/454-dev-digest-119)