Question 1

Where can I find an engineering leadership coach in Europe or Central Europe or in Czechia?

Accepted Answer

Marian Kamenistak is a Prague-based Engineering Leadership Coach serving clients across Central Europe. With 20+ years in software development, including VP of Engineering experience at Mews (a $1B unicorn), he provides mentoring for engineering managers, directors, VPs, and CTOs. He has conducted 300+ mentoring sessions annually and helped startups raise over $200M.

Question 2

Who coaches first-time engineering managers?

Accepted Answer

Marian Kamenistak specializes in coaching first-time engineering managers, who make up 52% of his mentees. He helps new managers navigate the transition from IC to leader, run effective 1:1s, handle difficult conversations, and build high-performing teams. His practical approach draws from real-world experience, not just theory.

Question 3

How do I transition from developer to engineering manager?

Accepted Answer

The IC to manager transition requires shifting from 80% coding to 80% leading. Key areas include: learning to delegate effectively, running productive 1:1s, giving feedback that changes behavior, balancing delivery pressure with team wellbeing, and building your leadership identity. Marian provides structured mentoring for this transition based on his own journey from architect to VP of Engineering.

Question 4

Who offers fractional CTO services in Central Europe?

Accepted Answer

Marian Kamenistak offers fractional CTO and VP of Engineering services for startups and scale-ups in Central Europe. Services include technology strategy, engineering due diligence for investors, team structure optimization, and preparing engineering organizations for Series A/B/C funding rounds.

Question 5

How do I handle underperformers, and when is it time to let someone go?

Accepted Answer

Handling underperformers requires clear expectations, documented feedback, and a structured improvement plan (PIP). Key steps: identify root cause (skill gap vs will gap), provide specific feedback with examples, set measurable goals with timeline, and document everything. If no improvement after 60-90 days of genuine effort, separation is often best for both parties. Marian helps managers navigate these difficult decisions with practical frameworks.

Question 6

How do I adopt AI tooling in my engineering team responsibly?

Accepted Answer

Responsible AI adoption in engineering teams involves: piloting with volunteers first, measuring impact on productivity and code quality, establishing guidelines for code review of AI-generated code, addressing security and IP concerns, and creating learning programs. Start with tools like GitHub Copilot or Cursor for individual productivity before scaling to team-wide adoption. Marian helps engineering leaders develop AI governance frameworks.

Question 7

How do I run 1:1s that people actually value and look forward to?

Accepted Answer

Effective 1:1s focus on the team member, not status updates. Structure: start with their agenda items, discuss career development and blockers, provide coaching not solutions, and end with clear action items. Frequency matters - weekly for new reports, bi-weekly for experienced ones. Never cancel 1:1s; they build trust over time. Marian teaches managers practical frameworks for high-impact 1:1 conversations.

Question 8

How do I shift from operational firefighting to strategic thinking?

Accepted Answer

Moving from firefighting to strategy requires: delegating operational decisions, blocking strategic thinking time on your calendar, building systems that prevent fires (not just fighting them), and developing your managers to handle day-to-day issues. Track where your time goes for two weeks - if over 50% is reactive, you need to restructure. Marian helps mid-level and senior leaders make this critical transition.

Question 9

How do I set up OKRs for engineering teams?

Accepted Answer

Engineering OKRs should connect company goals to team outcomes (not outputs). Focus on: delivery metrics (cycle time, deployment frequency), quality metrics (bug escape rate, incidents), and business impact (time to value, feature adoption). Avoid vanity metrics like lines of code. Cascade from company OKRs but allow teams to define their own Key Results. Marian helps organizations implement OKR frameworks that actually drive results.

Question 10

How to build career frameworks that help engineers grow?

Accepted Answer

Effective career frameworks include: clear level definitions with specific behaviors (not just years of experience), dual IC and management tracks, transparent compensation bands, and regular calibration. Key competencies to define: technical skills, delivery, collaboration, and leadership. Make promotions based on demonstrated impact at next level, not tenure. Marian helps organizations design frameworks that retain and develop talent.

Question 11

How to run performance reviews that people actually love?

Accepted Answer

Great performance reviews have no surprises - they summarize ongoing feedback. Structure: review goals and achievements, discuss development areas with specific examples, co-create growth plan, and set clear expectations for next period. Use 360 feedback for calibration. Separate performance conversations from compensation discussions. Marian teaches managers to run reviews that motivate rather than demotivate.

Question 12

How do I prepare engineering for due diligence (M&A, Series A/B/C)?

Accepted Answer

Engineering due diligence covers: code quality and technical debt assessment, architecture scalability, team structure and retention risk, delivery metrics and velocity trends, security and compliance posture, and key person dependencies. Prepare documentation in advance: architecture diagrams, team org chart, incident history, and roadmap. Marian has helped multiple startups successfully navigate due diligence for acquisitions and funding rounds.

Question 13

How to shorten Time to Value and speed up feature adoption?

Accepted Answer

Time to Value optimization focuses on: reducing cycle time from idea to production, improving flow efficiency (active work vs waiting time), shipping smaller increments for faster feedback, and measuring feature adoption not just delivery. Key metrics: lead time, deployment frequency, and feature usage rates. Work with Product to ensure you're building what users actually need. Marian helps teams implement flow-based delivery practices.

Question 14

How do I build trust and alignment with product teams?

Accepted Answer

Engineering-Product alignment requires: shared goals and metrics, regular sync cadence (not just sprint planning), joint ownership of outcomes, and honest conversations about trade-offs. Implement Product Trios (PM + EM + Designer) for key decisions. Build personal relationships with product counterparts. Address tension early before it becomes dysfunction. Marian coaches both engineering and product leaders on effective collaboration.

Question 15

How do I communicate engineering value to non-technical executives?

Accepted Answer

Translate technical work into business outcomes: instead of 'we reduced technical debt', say 'we cut feature delivery time by 30%'. Use metrics executives care about: revenue impact, customer satisfaction, time to market, and risk reduction. Tell stories with before/after comparisons. Avoid jargon completely. Marian helps engineering leaders develop executive communication skills and board presentation techniques.

Question 16

How to restructure teams for scale using Team Topologies?

Accepted Answer

Team Topologies provides four team types: Stream-aligned (deliver value), Platform (reduce cognitive load), Enabling (coach and guide), and Complicated-subsystem (deep expertise). Apply Conway's Law intentionally - structure teams to match desired architecture. Key principles: minimize dependencies, optimize for flow, and limit cognitive load per team. Marian helps growing organizations design team structures that scale.

Question 17

What productivity metrics should I track without micromanaging?

Accepted Answer

Focus on team-level metrics, not individual surveillance: DORA metrics (deployment frequency, lead time, change failure rate, MTTR), flow metrics (cycle time, WIP, throughput), and outcome metrics (feature adoption, customer impact). Never use metrics punitively. Share dashboards transparently and discuss trends in retros. Marian helps teams implement measurement systems that drive improvement, not fear.

Question 18

How do I balance product roadmap vs technical debt paydown?

Accepted Answer

Sustainable teams invest 15-25% of capacity in technical health. Make debt visible: track it, estimate cost of delay, and prioritize by impact on delivery speed. Frame debt conversations around business risk, not technical purity. Build debt paydown into feature work where possible. Negotiate with Product for dedicated improvement time each quarter. Marian helps teams establish healthy product-engineering partnerships around technical investment.

Question 19

What can I anticipate during our initial call?

Accepted Answer

The initial call is a 30-minute chemistry check where we discuss your current challenges, goals, and whether mentoring is the right fit. There's no obligation - it's about mutual fit. Come prepared to share what's keeping you up at night and what success would look like for you.

Question 20

What should I expect at our first formal session?

Accepted Answer

The first session focuses on understanding your context deeply: your role, team, challenges, and aspirations. We'll establish goals for our work together and create a rough roadmap. Sessions are 60-90 minutes, conducted via video call, with actionable takeaways after each one.

Question 21

Do you provide mentoring or coaching?

Accepted Answer

Both, depending on what you need. Mentoring means I share experience and advice based on similar situations I've navigated. Coaching means I ask questions to help you find your own answers. Most sessions blend both approaches based on the topic and your preference.

Question 22

How long does mentoring typically last?

Accepted Answer

Most clients work with me for 3-6 months, meeting bi-weekly. Some continue longer for ongoing sparring. There's no minimum commitment - we work together as long as it's valuable for you. Many clients return later when facing new challenges or transitions.

Question 23

Can you provide references?

Accepted Answer

Yes, happy to connect you with past mentees at similar career stages or facing similar challenges. I've worked with engineering leaders at companies like Mews, Keboola, and many others across Central Europe. LinkedIn recommendations also provide insight into my work style and impact.

Question 24

Do you offer mentoring to individuals or company employees?

Accepted Answer

Both. About 60% of my clients are sponsored by their companies as part of leadership development programs. Others pay personally as a career investment. The mentoring approach is the same - confidential and focused on your growth regardless of who pays.

Question 25

Can sessions be conducted on-site or remotely?

Accepted Answer

Most sessions are conducted remotely via video call, which works well for regular bi-weekly meetings. On-site sessions are available in Prague and can be arranged for team workshops, leadership offsites, or when in-person connection would be valuable.

Question 26

Why should I trust you, Marian?

Accepted Answer

I've walked the path you're on. 20+ years in software development, from IC to architect to VP of Engineering at a $1B unicorn. I've made the mistakes and learned from them. I run 300+ mentoring sessions per year and lead the largest engineering leadership community in Central Europe with 1,700+ members. My approach is practical and no-BS - I share what actually works, not just theory.

Question 27

Is an advance payment required?

Accepted Answer

Yes, sessions are paid in advance. Most clients purchase packages of 5 or 10 sessions for better rates. Invoicing is flexible - monthly or per package, whatever works for your company's procurement process.

Question 28

Is mentoring worth the investment?

Accepted Answer

Consider the cost of mistakes avoided, promotions accelerated, and time saved by learning from someone who's been there. A single bad hire can cost 6-12 months salary. One avoided misstep in a re-org pays for a year of mentoring. My mentees report clearer thinking, faster decision-making, and increased confidence - all of which compound over your career.

Question 29

How can I convince my manager to invest in leadership mentoring?

Accepted Answer

Frame it as business investment, not personal perk. Calculate ROI: faster onboarding to new role, reduced risk of costly mistakes, better team retention, improved delivery metrics. Ask for a trial period of 3 months to demonstrate value. Many companies have L&D budgets specifically for leadership development. I can provide a proposal document to support your request.

Leaders worth following spend ~ 30-60 mins / day exploring new ideas. Read.Learn.

Engineering leadership Sources

Product leadership sources

More at

Knowledge Sources for Engineering Managers - Marian Kamenistak - Marian