Zum Inhalt springen

Engineering Manager: Was die Rolle erfordert

Einige Inhalte auf dieser Seite (Kompetenzen, Fragen) sind derzeit nur auf Englisch verfügbar.

Leads one or more engineering teams, owning hiring, performance, wellbeing and delivery outcomes. Works with product and design to set priorities and shield the team from avoidable churn. Spends most time on people, process and planning rather than writing production code.

Kompetenzprofil: Karnamo curated v1 (original, not ESCO-derived). Es beschreibt eine typische Rolle; einzelne Arbeitgeber unterscheiden sich. Prüfe daher immer die konkrete Stellenbeschreibung.

Kernkompetenzen

Ab dem ersten Tag erwartet. Lücken entscheiden hier oft darüber, ob du zum Interview eingeladen wirst.

  • People Management

    Zielniveau: vertieft / kann andere anleiten

    Leading a team: expectations, support, accountability and wellbeing.

    • Prepare and hold a structured 1:1 template with a colleague: goals, blockers, feedback, development (practice, kostenlos)
  • Hiring & Interviewing

    Zielniveau: vertieft / kann andere anleiten

    Defining roles, running structured interviews and making fair hiring decisions.

    • Design a structured interview loop for a role: competencies, questions, scoring rubric, bias safeguards (practice, kostenlos)
  • Performance Management

    Zielniveau: vertieft / kann andere anleiten

    Setting goals, evaluating performance and handling underperformance fairly.

    • Write sample feedback using situation, behaviour and impact, and a sample improvement plan with measurable expectations (practice, kostenlos)
  • Coaching & Mentoring

    Zielniveau: vertieft / kann andere anleiten

    Developing others through feedback, coaching and mentoring.

    • Mentor someone for three months with a written goal, and reflect on what changed (practice, kostenlos)
  • Stakeholder Management

    Zielniveau: vertieft / kann andere anleiten

    Aligning expectations and communication with people who influence or are affected by your work.

    • Map the stakeholders of a current project by influence and interest and plan how to communicate with each (practice, kostenlos)
  • Communication

    Zielniveau: vertieft / kann andere anleiten

    Conveying information clearly and listening effectively, in writing and speech.

    • Write a one-page memo of a complex topic for a non-expert and have someone summarise it back to you (practice, kostenlos)

Wichtige Kompetenzen

Im ersten Jahr erwartet; starke Bewerber bringen einige bereits mit.

  • Agile Delivery

    Zielniveau: vertieft / kann andere anleiten

    Delivering iteratively with Scrum, Kanban and related practices.

  • Delegation & Ownership

    Zielniveau: vertieft / kann andere anleiten

    Distributing work and decisions so others own outcomes.

    • Delegate one meaningful task with clear outcome, constraints and check-in points, then review how it went (practice, kostenlos)
  • Conflict Resolution

    Zielniveau: vertieft / kann andere anleiten

    Addressing disagreement constructively between people or teams.

    • Prepare a difficult conversation using observations, impact and a clear request, and rehearse it with a peer (practice, kostenlos)
  • Technical Strategy

    Zielniveau: solide, selbstständig

    Setting long-term technical direction aligned with business goals.

    • Write a two-page technical strategy for a team: current state, goals, principles, trade-offs and sequencing (practice, kostenlos)

Wünschenswert

Zusätzliche Stärken, die helfen, aber selten eine Voraussetzung sind.

  • Budgeting & Forecasting

    Zielniveau: solide, selbstständig

    Planning and tracking costs and resources against a budget.

    • Build a team budget with headcount, tooling and contingency, and explain each assumption (practice, kostenlos)
  • Incident Management

    Zielniveau: solide, selbstständig

    Responding to, communicating about and learning from production incidents.

  • Change Management

    Zielniveau: solide, selbstständig

    Guiding teams and organisations through process or structural change.

    • Plan a process change for a team: who is affected, what resistance to expect, how you would communicate and measure adoption (practice, kostenlos)

Beispielhafte Interviewfragen

  1. Führung

    Describe how you would deal with a high performer who is hard to work with.

    Shows you address behaviour and its impact on the team directly, with clear expectations, not letting output excuse harm.

  2. Führung

    Describe how you would reorganise a team of twelve engineers that has become slow.

    Start with diagnosing why they are slow; any structural change should follow evidence and include communication and transition planning.

  3. Führung

    How do you balance technical debt against feature delivery with product partners?

    Shows you make debt visible in business terms, negotiate a sustainable allocation and avoid framing it as engineers versus product.

  4. Führung

    How do you decide between hiring for a role and developing someone internally?

    Reasons about time to impact, team health, growth paths and risk, rather than a default preference.

  5. Führung

    How do you handle an underperforming engineer?

    Shows fairness: clear expectations, early specific feedback, support, documentation, and a decision if there is no progress.

  6. Führung

    How do you manage a budget and justify headcount requests?

    Show you link headcount to outcomes and constraints, present alternatives and are transparent about assumptions.

Alle Interviewfragen für Engineering management · Gesprächsrunde und Erfahrungsstufe selbst wählen

Verwandte berufliche Wechsel

Rollen, deren Kompetenzprofile sich mit diesem am stärksten überschneiden. Die Überschneidung ist ein Gesprächseinstieg, keine Empfehlung.

Vergleiche deinen Lebenslauf anhand eines transparenten Rasters mit Stellenanzeigen für Engineering Manager.

Passungsanalyse ausprobieren