PRODUCT OWNER • ENGINEER

I own the whole chain, from idea to shipped product.

Product owner and engineer in one person. I decide what is worth building, then build it myself or lead the team that does. AI multiplies both roles; it is not the point.

See Cases About Me

Outcomes over output Builds and leads AI as leverage

Signal

Product + Engineering

Roles

Product Owner · Engineer

Scale

Solo or team

Delivery

Ship & learn

const goal = "solve the real problem";
ship(goal, { decide: me, build: me || team });

About Slava

Two roles, one owner.

I’m Viacheslav (Slava) Podmurnyi, product owner and engineer. Bachelor’s degree in computer science, hands that have shipped real systems. I hold both roles on purpose: the product side decides what is worth building, the engineering side knows what it costs and makes sure it works.

Right now I own a product end to end. With AI in the loop I can build most of it myself. When the work needs a team, I lead one: people who build the same way, faster, without lowering the bar. Business goal at one end, working product at the other, one owner in between.

Portrait of Viacheslav (Slava) Podmurnyi

Product and engineering, no handoff. Visionary without becoming corporate-boring. A rare mineral.

How I work

From business goal to shipped product.

Discovery

Talk to users and stakeholders, find the real problem, write it down on one page.

Decide

Rank by outcome and cost, say no out loud, keep the roadmap short.

Design the system

Architecture and clear stories, so the build starts from a plan, not a guess.

Build

Myself with AI in the loop, or with a team I lead. Same bar either way.

Ship and measure

Release small, watch the numbers, adjust.

Own the outcome

Uptime, cost, and whether it moved the business. That stays with me.

Skills

Product, engineering, leadership.

Product

Discovery & user research Roadmaps & prioritisation Backlog & user stories Metrics & experiments Stakeholder alignment Agile / Scrum Business cases Prototyping

Engineering

Agentic coding with Claude Code Multi-agent orchestration MCP servers & tool integration Spec-driven development Context engineering (CLAUDE.md, memory, skills) Evals & verification of AI output AI automation pipelines Architecture for AI systems

Leadership

Team leadership Leading AI-native teams Code review Delivery ownership

Cases

Real problems, shipped answers.

AI orchestration

Mission Control

A command layer for projects, agents, tasks, plans, and memories with reliable execution loops.

Role: Product owner and engineer
Outcome: One place where work is planned, handed to agents, and checked before it counts as done.

Automation

Automation Forge

Workflows that connect tools, APIs, alerts, and human approvals without turning into spaghetti.

Role: Product owner and engineer
Outcome: Busywork taken out of the loop; people kept where judgment matters.

Web products

Product Engineering

Clean interfaces, resilient backends, and deployment paths designed for iteration instead of drama.

Role: Product owner and engineer
Outcome: Fast, durable products that can be changed without fear.

Blog Preview

Field notes from the product floor.

Coming soon Owning both sides: product and code Coming soon Discovery without the theater Coming soon Building with AI without lowering the bar

Contact

Have a product worth forging?

Need someone to own a product, build it, or lead the team that will? Bring the goal, the constraints, and the messy backlog. I’ll bring clear priorities, working code, and a healthy disrespect for needless complexity.

Let’s Connect