Technical Product Owner
Own your future
Transcenda is a US-headquartered, full-lifecycle product development company with 300+ team members across the US, Europe (Poland, Romania, Ukraine), and LATAM (Colombia, Brazil). We partner with Fortune 500 companies and well-funded startups to deliver world-class software products, from ideation and design through engineering and launch. Our teams are fully remote, embedded long-term with clients, and trusted as strategic thought partners on product, architecture, and engineering decisions.
Our client builds software that schools and districts use to run their websites and communicate with families. You’ll be the Product Owner for one of their product teams, owning the backlog for a product that thousands of schools and millions of families rely on.
This work needs two kinds of care. Every release reaches real customers, and a bug can affect students, parents, and school staff directly. At the same time, one product serves many schools with different settings, so a change that works for one school can break another. You’ll decide what your product should and shouldn’t do, and turn that into backlog items the team can build and test without guessing.
Must haves
- Product Owner or product management experience, including owning releases.
- Experience with a multi-tenant or white-label product, where one change affects many customers with different configurations.
- Technical fluency to work with engineers on front end, backend APIs, and third-party services. You read code and API contracts, challenge estimates, and spot cross-team dependencies early. You don’t need to write production code.
- Experience taking products from prototype to production, including deciding how to evaluate output that is probabilistic and imperfect.
- Comfort with feature flags, staged rollouts, and release risk, including saying “not yet.” You’ve handled hotfixes, rollbacks, and phased release decisions.
- Hands-on use of AI tools (e.g. Claude Code, Cursor, Figma Make, v0, Lovable) for prototyping, discovery, and understanding unfamiliar code. Show us something you built.
- Ability to turn customer and stakeholder feedback, often relayed through Support and Services, into clear priorities, and to tell a loud customer from a systemic gap.
As a plus
- Experience on a customer-facing product used by real end users, including working within external review, platform, or policy constraints (e.g. app stores, marketplaces, regulated environments).
- Experience with real-time or high-volume systems such as messaging, notifications, or integrations: delivery reliability, moderation, permissions, and user-to-user safety.
- K-12 or education software experience, including student information system integrations and how school roles and rosters work.
- Working knowledge of privacy and accessibility obligations for software that handles minors’ data (FERPA, COPPA, ADA/WCAG), or a demonstrated ability to get up to speed fast.
- Experience working across teams that share a data model or API (e.g. web, mobile, communications).
- Experience with an AI-assisted software development lifecycle, such as writing tickets for coding agents and reviewing agent output.
- Experience with product analytics and data tooling.
- Experience running alpha or early-access programs with contracted customers rather than self-selected enthusiasts.
- Shipped LLM-powered features inside an existing product, especially where PII, moderation, or output quality was a risk.
Key responsibilities
- Own your team’s backlog and sprint goals. Balance new features, defects, tech debt, and compliance or platform work. Defend the mix to leadership and to other teams that depend on you.
- Turn product requirements into agent-ready work. Write stories and tasks with clear intent, binary acceptance criteria, files in scope, and a runnable verification step, so both engineers and AI coding agents can pick them up without a meeting.
- Prototype to learn, then write down what matters. Use AI tools to build working concepts quickly. Before engineering builds, convert them into constraints: per-customer scoping, permissions, feature flags, data contracts. Keep written decision records wherever your product meets another system or team.
- Run staged rollouts and early-access programs. Plan customer cohorts, flags, and rollback paths. Pick launch customers and set expectations with them through Support and Services.
- Own release readiness. Decide with engineering and QA what is safe to ship, coordinate releases and hotfixes, and keep release notes and help content current.
- Triage production issues. Work with engineers to find root cause, decide severity, and communicate impact to stakeholders in plain language.
- Turn feedback into direction. Synthesize input from Support, Services, and customers into priorities.
- Define and measure success. Instrument what you ship and pull your own numbers from product analytics and the data warehouse.