We're building a team of Product Architects at Bloomreach. As a Senior Staff Product Architect, you own or co-own the architecture of a single product, with deliberate overlap across related products so architecture stays aligned where our products meet.

You are a product builder first. This is not a role for someone who cares about technology for its own sake: you take genuine part in defining the product — what it should be, who it's for, why it matters — and you bring system-level technical judgment into that definition, not after it. You sit at the intersection of product and engineering: close enough to product decisions to co-shape them, and close enough to the code to know what you're talking about — you'll spend 20–30% of your time hands-on, coding or prototyping.

AI runs through everything you'll build. Our products are, to varying degrees, AI-led, and the architecture you own decides how well they get to be. You'll work with internal AI foundations such as our knowledge graph, and you'll use AI daily as a tool of your own craft — in design, prototyping, and analysis.

It's a rare shape of seniority: director-level scope and impact, zero direct reports. If you've led engineering teams and want your leverage back in product and technical judgment rather than people management, this role was designed for you. You will work remotely (from Czechia / Slovakia), but we are more than happy to meet you in our nice offices in Bratislava, Brno or Prague.

What you'll do

• Co-define the product with product managers and UX — from the earliest ideation through shaping. You're in the room before the roadmap is set, contributing to what we build and why, not only how
• Constructively challenge PRDs and provide formal technical input and recommendations before work is prioritized
• Lead or facilitate technical shaping of initiatives, matching your involvement to their complexity, with a clear escalation path to the VPs of Product and Engineering
• Architect AI-led product capabilities — decide where AI belongs in the product, how it's grounded in our data and internal foundations (such as the knowledge graph), and how it stays reliable, safe, and cost-effective at scale
• Maintain the architectural runway — keep enabling technical work identified and ready ahead of the roadmap, so product ambitions never stall on foundations
• Own key technical tradeoffs and non-functional requirements for your product: scalability, reliability, security, cost
• Drive cross-product architectural alignment through our architecture chapter, growing its review and challenge culture over time
• Stay hands-on (20–30%) through coding and prototyping, using AI tooling as a first-class part of the work — your judgment stays grounded in the real system

What success looks like

Six months in, the products you architect show a faster idea-to-implementation flow — above all a shorter, clearer shaping phase: ideas reach engineering well-formed, technical risks surfaced early, fewer late reversals.

What you bring

• A product builder's mindset — you've shaped what products became, not just how they were built, and you care about users and outcomes as much as systems
• A Staff+ engineering background — you've operated at the level where your technical decisions shaped whole products
• Strength in product conversations — you engage with product managers on the why and what, not just the how
• Prior management experience, ideally as a senior engineering manager — you understand how organizations ship software, and you've chosen technical leadership deliberately
• Excellent stakeholder management — you build alignment across product, engineering, and leadership, and you challenge without friction
• Fluency with AI on both sides: experience shaping products with AI/LLM capabilities, and a habit of using AI tools in your own work

Nice to have

• Experience as an engineering director
• Experience as an architect
• Experience with marketing products or solutions (marketing automation, CDP, campaign tooling, martech)
• Experience with knowledge graphs, agentic systems, or LLM-grounding architectures (RAG, tool use, evaluation)

How this role differs

• Not a software architect in the classic sense: your scope is a product, not a codebase — you help shape what gets built, not only how
• Not a product manager: the PM owns the roadmap and priorities; you co-own the product definition and own the technical judgment behind it
• Not an engineering manager: no direct reports — your influence comes from insight and challenge, not line authority
• Not a technologist for technology's sake: if the most interesting part of the job for you is the stack, this isn't the role

#LI-KP1