GlassdollarPosted 3h ago
Full Stack Engineer (m/f/d)
Berlin
Primary technologies, domain competencies, and required qualifications
Verified specifications, primary responsibilities, and qualifications
Join GlassDollar and help build the system some of Europe's largest companies use to find, test, and adopt startup technology.We're looking for an engineer who wants considerably more responsibility than "implement what's in the ticket". You'll take an ambiguous problem, shape it together with product, make the important technical decisions, ship it, and stay close enough to see whether it worked.We expect you to have opinions. We also expect you to be good enough to change them.The problem we're solvingLarge organisations are remarkably good at accumulating problems. A company with 100,000 employees can have thousands of operational challenges across its business units. Somewhere outside that organisation, a startup has probably already built part of the solution. Getting those two things to meet still happens through spreadsheets, long email threads, and meetings whose primary output is another meeting.GlassDollar OS is the operating system for venture clienting: problem → startup discovery → evaluation → PoC → adoption, in one repeatable workflow.Our customers are some of Europe's largest organisations, so the software has to move quickly and behave like something an enterprise can depend on. That tension creates the interesting engineering problems.
What we're looking forYou 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.You make the system better, not just the feature. You fix the spreading pattern rather than the single instance, make an API easier for the next person, and improve tests because the current setup makes everyone afraid to deploy. Your impact should show beyond the pull requests with your name on them.You can work across the stack. A feature might run from a React interaction through GraphQL into a Node service, a schema redesign, a permissions update, and a safe migration for existing customers. Curiosity to follow the problem matters more than equal depth everywhere.You own quality. We have QA. That's not where quality begins. What breaks if this request happens twice? What happens with old data, or when the API fails halfway through? We use Playwright and Jest alongside reviews and monitoring. The goal isn't coverage, it's confidence.You communicate like your decisions will matter later. Six months from now, somebody should understand an important decision without digging through seventeen Slack messages and a deleted Notion comment. That means writing things down when they matter, explaining trade-offs clearly, giving useful code reviews, and surfacing risks before they become incidents.You raise the engineering bar around you. You do not need a management title to have influence. Find the hole in an architecture, unblock someone without taking the keyboard away, disagree without turning every decision into a referendum. As you earn trust, you’ll naturally become the person people bring harder problems to.
What you'll doOver your first year:
How we workWe'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 hireNo seven-stage endurance test. No algorithm trivia disconnected from the work.
One last thingJob 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.
Find Jobs in Germany on Arbeitnow
Ready to apply?
Submit your application directly through the employer portal.
Du liebst es, vor der Kamera zu stehen, hast TikTok und Instagram komplett im Griff und willst moderne Hijabi-Mode perfekt in Szene setzen? Wir suchen eine kreative Hijabi Content
About Unblu Unblu helps the world's leading banks and insurance companies deliver conversational finance solutions. We provide highly secure engagement and collaboration software,
Shape our AI products with a real say on the roadmap, and win the TV customers who will use them. You find the telcos, Pay TV operators and broadcasters that should run on the 3Rea
Art der Stelle Unbefristete Stelle in Vollzeit Voraussichtliches Startdatum: Frühjahr 2027 Wir denken Tierarztpraxis neu Wir denken Tierarztpraxis neu! Als tierärztlich geführtes U