1:1 Coaching
for Product Engineers
Thank you for your interest in working together. Below I’ve outlined how I approach coaching and what makes a good fit.
What I Do
I help engineers become confident product thinkers. People who can build, decide, and communicate with clarity.
My specialty is the intersection of product and engineering.
I've worked as a Developer, PM, CTO, and CPO, and I coach through all these lenses.
Product Is Engineering. Engineering Is Product.
They were never meant to be separate. The best work happens when builders make trade-offs with a clear understanding of the business, the user, and the technology. Product Engineers bring these worlds together.
Who I Work With
Most of my clients are Engineers, Engineering Managers, or Heads of Engineering who choose to stay close to product. They're usually:
- Player-coaches who ship code and lead (projects, people, or agents)
- Direct communicators who value candor over corporate speak
- Self-aware about what they're bad at and want to fix it
- Willing to put in the work between sessions
I've worked with people from Migros, Swiss Marketplace Group, and Smallpdf, among others.
Note: My style is different from traditional coaching. I mix coaching and advising.
Instead of just reflecting your words back to you, I challenge your thinking and share what I've seen work (and fail). We find a solution together—one that fits your specific situation.
What We Work On
Sessions focus on the problems you're facing right now:
- Deciding in ambiguity. How to move forward when there's no PM telling you what to build
- Building influence without authority. Getting buy-in sideways and up
- Navigating trade-offs. Ship fast vs. build right, user value vs. business cost
- Diagnosing problems. Getting to the real issue instead of jumping to solutions
- Communicating clearly. Using sketches, writing, and structured thinking to drive alignment
- Talking business. Connecting your technical work to metrics, revenue, and company impact
We'll work through real scenarios, practice hard conversations, and build judgment for situations where there's no obvious right answer.
How It Works
Most engagements start with 6 months: we meet twice a month for the first three months, then once a month. This gives you time to practice what we discuss and see results.
Sessions are goal-oriented and practical. We focus on what changes your outcomes this week, not abstract frameworks or lifestyle optimization.
What People Say About Me
Clients tell me they value having a.n independent view from someone who's lived in both product and engineering, listens deeply, and speaks directly.
One client recently moved from Engineering Manager to Head of Engineering after applying what we worked on: making the implicit explicit, building bridges by understanding the other side.
We're Not a Fit If
This won't work if you:
- Want someone to only ask reflective questions and nod along
- Prefer discussing theory over practicing real scenarios
- Aren't willing to try things that feel uncomfortable
- Believe you can't change—that skills are inherited, not learned through practice
I'm direct. If I think you're off track, I'll tell you. If that sounds like judgment instead of clarity, we probably won't click.
Get in Touch
If this sounds useful, email me at adam [at] adamjuras [dot] com
Include a bit about your role, what you're struggling with, and what a good outcome looks like for you.
Why Me
I discovered the classic hill climbing algorithm early, and took it literally. I've worked across nearly every role in product development: Developer, Product Manager, UX Designer, CTO, and CPO.
All those learnings converge in the Product Engineer role: people who combine product and engineering skills to create products with impact. The best engineers I know work this way.
My mission: help more people bring product and engineering together.