> Markdown version of [/jobs/ext/420588-staff-software-engineer](https://www.wearedevelopers.com/jobs/ext/420588-staff-software-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). --- # Staff Software Engineer - **Company:** Sharpist GmbH - **Location:** Berlin, Germany - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, BigQuery, Software Bug Management, MongoDB, Node.Js, Redis, Prometheus, TypeScript, Google Cloud, ReactJS, Large Language Models, Grafana, React Native, Docker - **Published:** June 20, 2026 - **Apply:** https://de.indeed.com/viewjob?jk=c479d37af7a3adee ## About the Role Do you have experience in TypeScript?, Do you have a Master's degree?, * You think like a Product Engineer: you've had full ownership of feature development, defining the solution, not just building what someone else specified * You can write a clear, technically grounded PRD, and you know what makes one bad * You have a strong intuition for UX: what confuses users, what creates friction, what feels right * You use AI/LLM tools as a core part of how you work, across specs, prototyping, and implementation, not as a gimmick. Self-directed experiments and side projects count as evidence * You can spot what LLMs miss: a wrong abstraction, a brittle data model, a spec that looks fine until it hits production * Fluent English (written and spoken) Nice to have: * Experience building AI/LLM product features (prompting, evaluation, guardrails) * Worked in a B2B SaaS or HR tech environment ## Description Our goal: to make coaching scalable - not to replace humans, but to enhance them. Human and intelligent., You get a business problem and you own it from there: solution concept, PRD, implementation, release, and measuring whether it worked. No hand-off, no shipping blind. We're working toward a one-week cycle, but we're not there yet. We'd rather ship at ~70% and learn from real usage than polish in private. The hard part isn't the coding. It's the synthesis: going from a fuzzy problem to a technically sound, scoped solution fast enough to keep the cycle moving. That's where most engineers slow down. That's the gap this role fills. LLMs handle a growing share of the implementation. What they can't replace is the judgment to know when the architecture is wrong, when an abstraction won't hold, when a shortcut becomes next quarter's incident. Catching that before it's built, not after., * Get deep into the Sharpist product: the AI Coach, the coaching platform, the learner journey * Audit existing solution concepts and PRDs; understand what's shipping and why * Shadow one full problem-to-delivery cycle with the engineering team * Ship your first small improvements or bug fixes First quarter: * Own your first problem end-to-end: define the problem space, design the solution, write the PRD * Use LLMs as a core workflow tool: prompt for specs, evaluate for efficiency and soundness, iterate * Work directly with engineers to ensure what gets built matches what was intended * Talk directly to users and stakeholders to ground each problem in real insight, not assumptions * Give structured feedback on PRDs from others: technical feasibility, scope, edge cases Year one: * Own multiple features end-to-end: define, ship, measure, and know what worked and what didn't * Contribute to the team's weekly give & take: share what you learned, pick up what others discovered * Make the developer experience meaningfully better: tooling, workflow, or process improvements the team actually uses The Stack TypeScript, React, React Native, Node.js, MongoDB, Redis, Docker, Google Cloud, BigQuery, Google Dataform, Lightdash, Prometheus, Grafana. ## Related Videos - [Reducing LLM Calls with Vector Search Patterns - Raphael De Lio (Redis)](https://www.wearedevelopers.com/videos/1714-reducing-llm-calls-with-vector-search-patterns-raphael-de-lio-redis) - [Docker Compose: Rediscovered](https://www.wearedevelopers.com/videos/1978-docker-compose-rediscovered) - [40 Minutes to Build a Serverless COVID-19 REST and GraphQL APIs](https://www.wearedevelopers.com/videos/208-40-minutes-to-build-a-serverless-covid-19-rest-and-graphql-apis) - [Navigating the Corporate Jungle: Life as a Developer in a large Company](https://www.wearedevelopers.com/videos/621-navigating-the-corporate-jungle-life-as-a-developer-in-a-large-company) - [Accelerating Authentication Architecture: Taking Passwordless to the Next Level](https://www.wearedevelopers.com/videos/733-accelerating-authentication-architecture-taking-passwordless-to-the-next-level) - [Slopquatting, API Keys, Fun with Fonts, Recruiters vs AI and more - The Best of LIVE 2025 - Part 2](https://www.wearedevelopers.com/videos/1765-slopquatting-api-keys-fun-with-fonts-recruiters-vs-ai-and-more-the-best-of-live-2025-part-2) ## Related Articles - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [The Biggest German Tech Companies](https://www.wearedevelopers.com/magazine/424-the-biggest-german-tech-companies) - [Dev Digest 159: AI Pipelines, 10x Faster TypeScript, How to Interview](https://www.wearedevelopers.com/magazine/563-dev-digest-159-ai-pipelines-10x-faster-typescript-how-to-interview) - [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix) - [Dev Digest 150 - The shift to AI generated code, fingerprinting and OKRs vs. doing your job](https://www.wearedevelopers.com/magazine/533-dev-digest-150-the-shift-to-ai-generated-code-fingerprinting-and-okrs-vs-doing-your-job)