Work with me
Open to full-time Product Manager and Product Engineer roles, plus selected consulting and advisory work.
A role, a product problem you are working through, or an early conversation — any of those is a good reason to get in touch.
Or write directly: hello@erdeniztunc.com
Where I start
In the first 30 days, my priority is to build a clear view of the current product, identify the customer problem that matters most, and decide what should happen first.
Understand the product today
I look at the product, its customers, company goals, existing data, feedback, and the realities of the team building and selling it.
The result is a shared understanding of what is working, what is unclear, and where the main uncertainty sits.
Choose the problem that deserves focus
I separate symptoms from the underlying problem.
The bottleneck may be the product itself, the target segment, onboarding, positioning, pricing, activation, or the way value is communicated.
Decide the first move
I turn the evidence into one practical priority.
That may be a product change, a clearer segment decision, a prototype, a messaging test, a focused product slice, or a decision not to build.
What happens next
The first 30 days create a clear direction. I then help turn that direction into clear scope, a testable solution, engineering decisions, launch preparation, and the next learning loop.
From there, the work continues through the full product cycle: building with engineering, shipping, learning from real customer feedback, and deciding what to improve next.
Detailed view
See what I bring to a company in practice →When I'm useful
- You have a product idea, but do not know what to validate firstI run discovery, identify the riskiest assumption, define the smallest useful scope, and create a working artifact to test the direction before engineering commits significant time.
- You have a product in development, but the product side needs stronger ownershipI work alongside engineering on backlog decisions, sprint scope, trade-offs, edge cases, and product questions that emerge during the build. Product ownership does not stop at handoff.
- You are preparing to launch and need a clearer path to marketI connect product readiness, positioning, go-to-market, rollout, analytics, and early customer feedback so the team can launch with a clear plan and turn what it learns into the next product decision.
Where I do my best work
Company size matters less to me than how the team operates. I do my best work where context is shared openly, decisions move quickly, product has meaningful ownership, and customer and engineering access is direct.
That can be an idea-stage startup, a scaling company, or a larger product organization. The common ground is transparent communication, trust, and a willingness to test assumptions and change direction when the evidence requires it.