Read Gem boards through the job board's GraphQL API
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
76187d5862
commit
1fc9668110
5 files changed
+335
No files matched your search
Vendored
+1
@@ -0,0 +1 @@
|
||||
{"data":{"oatsExternalJobPosting":{"id":"T2F0c0pvYlBvc3Q6MTA0NDAzNA==","title":"Staff AI Product Engineer (Prague/Brno/Remote EU)","descriptionHtml":"<div><strong>Only the best engineers are being built here.</strong></div><div>At Productboard, we are defining AI-first Product Engineering. Not as a one-time achievement, but as a baseline we raise every time we reach it. We remove every bottleneck as it surfaces and rebuild how product teams work from first principles, not just adding AI to existing workflows.</div><div>AI tools are everywhere now. Agents can write code. That\u2019s today\u2019s baseline.What we're building is the environment where the baseline makes you better: focused on outcomes, writing specs that agents build from, leveling up with every feature you ship.</div><div>We are defining what AI-native product development becomes. We're all in.</div><h3><strong>What you will build</strong></h3><div>You'd lead the architectural work that makes our codebase AI-native. Specifically:</div><ul><li class=\"\"><strong>Agent-native architecture standards.</strong> Clear API contracts, semantic naming, well-defined module boundaries. The patterns that keep AI effective as our systems grow.</li><li class=\"\"><strong>A context infrastructure layer.</strong> Repo-versioned guidance that AI tools load automatically \u2014 improving the output of Cursor, Claude Code, and Codex simultaneously.</li><li class=\"\"><strong>Self-healing workflows for incidents.</strong> Agents that triage alerts, pull logs, surface relevant history, suggest remediation. Humans intervene where judgment matters.</li><li class=\"\"><strong>Agent workflows that go beyond chat.</strong> Multi-step reasoning, tool use, autonomous task execution with human-gated checkpoints \u2014 for product features, not internal demos.</li><li class=\"\"><strong>Systematic optimization of AI code review.</strong> Earlier detection of correctness, security, and maintainability issues, with the noise filtered out before it reaches a human reviewer.</li></ul><h3>The opportunity</h3><div>The first shift in our teams has already happened: agents write code. That\u2019s the baseline everywhere. Now we\u2019re building an AI-first Product Engineering organization where learning matters as much as shipping.</div><div>Only a few companies build a product that makes them better. What we\u2019re building next is a single place where work lives. Specs, plans, and full product context live in Productboard. There\u2019s a seamless loop between <a href=\"https://www.productboard.com/product/spark/\" rel=\"noopener noreferrer\" target=\"_blank\">Spark</a>, our AI agent, and the coding agents. Engineers can steer from anywhere and focus on directing the work instead of typing it all out.</div><div>Our own teams run on Productboard and Spark, so the feedback loop isn't a survey next quarter. It's the next conversation you overhear.</div><div>Imagine you ship a feature before lunch and by the afternoon, half the floor is working with it. Not in a demo, not on a roadmap slide: in our real work, minutes after you merged.</div><div>We feel the gaps our customers feel, and we close them first. Every feature goes straight to real product teams solving real problems, starting with ours.</div><div>We are looking for a Staff AI Engineer who wants to build this from the inside.</div><h3>Why this matters for your career</h3><div><strong>Engineers own more.</strong> Not just the code: the outcome it drives.</div><div>You won't just use AI tools. You will shape the architecture that makes agents effective, define the workflows that make them reliable, and build the evaluation systems that make them trustworthy.</div><div>This is where you become a pure product engineer. Someone who owns the problem, the trade-offs, and the result, not just the implementation. Every maker has an orchestra. The craft is knowing what it should play. And we never outsource our thinking.</div><div>The skills you build here (designing codebases agents can work in confidently, writing specs that carry your judgment into every build, building evaluations that catch what AI misses) will define senior engineering for the next decade. What you learn here doesn't just make you faster today. It makes you more valuable for years to come.</div><h3><strong>What you will do</strong></h3><div>We're hiring a Staff AI Engineer to own the architectural layer that makes this real, working alongside our engineers, PMs, and designers shipping AI-first product features end-to-end. You'd ship code, set technical direction, and shape decisions about what's worth building. Your north star here will be: get from idea to validated learning twice as fast.</div><h3><strong>How we work</strong></h3><div>We've moved away from process and toward judgment. The shift looks like this:</div><ul><li class=\"\"><strong>One named driver per initiative.</strong> End-to-end ownership of the outcome, the path, the decisions, and the learnLine truncated
|
||||
Reference in new issue
Block a user