Staff Backend Engineer

Terminal
Madrid, Spain
4 days ago

Role details

Contract type
Permanent contract
Employment type
Full-time (> 32 hours)
Experience required
0 years minimum
Working hours
Regular working hours

Tech stack

Java (Programming Language) Artificial Intelligence Amazon Web Services Cursor (Graphical User Interface Elements) Distributed Systems Python (Programming Language) PostgreSQL MongoDB Ruby TypeScript ReactJS Large Language Models
+9 more
Prompt Engineering Backend Kotlin Event Driven Architecture Kubernetes Cloudflare Figma Terraform Looker Analytics

Job description

About Productboard Productboard was founded in ** by Hubert Palan and Daniel Hejl with a simple mission: to help companies make products that matter.In the years since, we’ve grown from a handful of people to hundreds, backed by a number of the most renowned VC firms in Silicon Valley.Today, Productboard is recognized as one of the hottest tech startups, appearing on the Forbes’ Next Billion-Dollar Startups list and being named the most valuable startup in the Czech Republic by Forbes Magazine.About The Role We\ ‘re hiring a Staff 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 northstar here will be: get from idea to validated learning twice as fast.What You’ll Do How we workWe\ ‘ve moved away from process and toward judgment. The shift looks like this:One named driver per initiative. End-to-end ownership of the outcome, the path, the decisions, and the learnings. No approval chains. The driver decides; leadership unblocks.One-page pre-reads as the unit of decision. Big work starts with a brief covering the problem, expected outcome, risks, and effort. Leadership reads it and decides. No 30-slide decks. No two-week alignment cycles.Continuous delivery, no quarterly planning. Roadmap committed one month out. Beyond that, AI moves too fast for longer cycles to mean anything. We ship to internal first, then beta, then GA. Validation comes from real usage.PMs and designers ship to production. Not just specs and Figma. They prototype with AI tools and ship alongside engineers. PMs own what gets built and when. Engineers own how. If you\ ‘ve been a founding engineer or founder, this should feel familiar. If you\ ‘ve been waiting for a place that operates like that at scale, this is one. The system around youWe invest before we expect. We are actively looking for the next set of constraints to remove before they slow us down.Best AI tools from day one. Cursor, Claude Code, Codex, Glean. No waiting list, no approval process. If a better tool shows up tomorrow, you get that one too.AI Champions embedded on every team. Engineers (not coordinators) who pair with you, unblock you, and help you move faster with agents. Four hours every week dedicated to team enablement.A codebase built for agents. Curated AGENTS.Md files, repo-versioned skills, clean contracts. Continuously evaluated, not accumulating.Ship It with AI days. Two days every six weeks. No meetings for ICs. Pick a real problem, try a new AI workflow, ship to production within 48 hours.Knowledge that compounds. Monthly engineer-to-engineer events where we share what we\ ‘re experimenting with, learning, and shipping with AI.What You\ ‘ll BringYou ship with AIevery day. You think in outcomes, not output. You can name a tradeoff you made between scope and quality and tell us why you made it. You can describe what you\ ‘ve stopped doing because AI made it unnecessary. You\ ‘ve owned features end-to-endand know what it costs to get something to GA. Concretely, we\ ‘re looking for:6-10+ years of production software engineering experienceStrong backend skills in Python, Kotlin, or Java, with experience evolving service-level logic and infrastructureHands-on LLM experience in real products: prompt design, context management, evaluation, real understanding of trade-offs (hallucinations, latency, cost, reliability)Comfort with distributed systems and event-driven architectures (queues, async processing, service-to-service communication)Daily use of AI coding tools as a core part of your workflow - pushing them, refining prompts, knowing where they break Strong fit: Former founding engineer or founder. A 0-to-1 engineer who turns business insights into prototypes to validate ideas quickly. Someone who\ ‘s built agentic systems in production, or done deep work with multi-step LLM workflows (tool use, memory, orchestration). Our tech stackAI layer: Python, Pydantic AI, BraintrustFrontend: TypeScript, React, Relay, GraphQLBackend: Kotlin, Ruby (legacy services we\ ‘re modernizing), with new services built in KotlinStorage: PostgreSQL, MongoDB, Elastic, RedisData pipeline: Python, Keboola, Looker, SnowflakeInfrastructure: AWS, Cloudflare, Kubernetes, Terraform This job posting exists to fill a vacancy.#J-**-Ljbffr

Requirements

coordinators) who pair with you, unblock you, and help you move faster with agents. Four hours every week dedicated to team enablement.A codebase built for agents. Curated AGENTS.Md files, repo-versioned skills, clean contracts. Continuously evaluated, not accumulating.Ship It with AI days. Two days every six weeks. No meetings for ICs. Pick a real problem, try a new AI workflow, ship to production within 48 hours.Knowledge that compounds. Monthly engineer-to-engineer events where we share what we\ ‘re experimenting with, learning, and shipping with AI.What You\ ‘ll BringYou ship with AIevery day. You think in outcomes, not output. You can name a tradeoff you made between scope and quality and tell us why you made it. You can describe what you\ ‘ve stopped doing because AI made it unnecessary. You\ ‘ve owned features end-to-endand know what it costs to get something to GA. Concretely, we\ ‘re looking for:6-10+ years of production software engineering experienceStrong backend skills in Python, Kotlin, or Java, with experience evolving service-level logic and infrastructureHands-on LLM experience in real products: prompt design, context management, evaluation, real understanding of trade-offs (hallucinations, latency, cost, reliability)Comfort with distributed systems and event-driven architectures (queues, async processing, service-to-service communication)Daily use of AI coding tools as a core part of your workflow - pushing them, refining prompts, knowing where they break Strong fit: Former founding engineer or founder. A 0-to-1 engineer who turns business insights into prototypes to validate ideas quickly. Someone who\ ‘s built agentic systems in production, or done deep work with multi-step LLM workflows (tool use, memory, orchestration). Our tech stackAI layer: Python, Pydantic AI, BraintrustFrontend: TypeScript, React, Relay, GraphQLBackend: Kotlin, Ruby (legacy services we\ ‘re modernizing), with new services built in KotlinStorage: PostgreSQL, MongoDB, Elastic, RedisData pipeline: Python, Keboola, Looker, SnowflakeInfrastructure: AWS, Cloudflare, Kubernetes, Terraform This job posting exists to fill a vacancy. #J-**-Ljbffr

About the company

Madrid, EspaĂąa

About Productboard Productboard was founded in ** by Hubert Palan and Daniel Hejl with a simple mission: to help companies make products that matter. In the years since, we’ve grown from a handful of people to hundreds, backed by a number of the most renowned VC firms in Silicon Valley. Today, Productboard is recognized as one of the hottest tech startups, appearing on the Forbes’ Next Billion-Dollar Startups list and being named the most valuable startup in the Czech Republic by Forbes Magazine.About The Role We\ ‘re hiring a Staff 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 northstar here will be: get from idea to validated learning twice as fast.What You’ll Do How we workWe\ ‘ve moved away from process and toward judgment. The shift looks like this:One named driver per initiative. End-to-end ownership of the outcome, the path, the decisions, and the learnings. No approval chains. The driver decides; leadership unblocks.One-page pre-reads as the unit of decision. Big work starts with a brief covering the problem, expected outcome, risks, and effort.

Apply for this position

This job is hosted externally. Click below to view the full posting and apply.

Apply on www.buscojobs.com.es

Good distractions

Talks and stories from around this role — technically off-topic, practically not.

1:44 min

Balancing artisanal coding skills with automated agent oversight

Jyoti Bansal Jyoti Bansal +1 ¡ World Congress 2026 Europe

50 sec

Why developer happiness matters in web frameworks

Eileen Uchitelle Eileen Uchitelle +1 ¡ Coffee With Developers

5:04 min

Configuring the Figma MCP for local code generation

Perf + AI

3:09 min

Understanding Kotlin Multiplatform and its compiler targets

Petar Marijanović · LIVE

1:24 min

Building client-facing AI agents for engineering teams

Alfonso Graziano Alfonso Graziano ¡ Coffee With Developers

3:30 min

Falling in love with Ruby and creating Basecamp

David Heinemeier Hansson David Heinemeier Hansson +1 ¡ Coffee With Developers

Videos

See all

Related articles

See all