Mach aus dieser Rolle ein Bewerbungsgespräch — ein Lebenslauf und ein Anschreiben, die genau auf das zugeschnitten sind, was dieser Arbeitgeber sucht.
Sharpist is seeking a Staff Product Engineer to bridge product and users, turning insights into shipped solutions using AI-assisted coaching features.
You will own end-to-end initiatives from problem definition to delivery, with a focus on scalable architectures, LLM-enabled tooling, and a fast feedback loop in a hybrid Berlin setting.
Join a team that values fast learning, strong engineering judgments, and cross-functional collaboration.
Sharpist exists to help people become more self-aware and effective at work and in life.
We combine human coaching with an AI Coach so that employees at every level can access meaningful support when they need it.
Our goal: to make coaching scalable - not to replace humans, but to enhance them.
As a Staff Product Engineer, you sit where that product meets the people using it. Your work turns that support into something people actually use to reflect, learn, and act.
Meet our AI Coach in action - and see how Sharpist empowers leaders and talents to grow every day:
The Role
You get a business problem and own it from there: shaping the solution, writing the technical specification, working through implementation, releasing it, and checking whether it actually worked. There is no hand-off in the middle and no shipping blind.
We're working toward a one-week cycle, although we're not there yet. For now, we'd rather ship at roughly 70%, learn from real usage, and improve the next version than spend too long polishing something in private.
The difficult part isn't coding on its own. It's the synthesis: taking a fuzzy problem and turning it into a technically sound, properly scoped solution quickly enough to keep the cycle moving. That's where many engineers slow down. This role is here to close that gap.
LLMs now handle a growing share of implementation, and you should use them as part of your everyday workflow. What they can't replace is the judgment to recognise when the architecture is wrong, when an abstraction won't hold, or when a shortcut is likely to become next quarter's incident. The important thing is catching that before it gets built, rather than after it reaches production.
TypeScript, React, React Native, Node.js , MongoDB, Redis, Docker, Google Cloud, BigQuery, Google Dataform, Lightdash, Prometheus, Grafana.
Hybrid in Berlin, 3 days per week in the office. We find that being together in person is what builds the kind of relationships where real conversations happen: the ones that change how you think, how you work, and how the product evolves.