Tech Lead: Was die Rolle erfordert
Einige Inhalte auf dieser Seite (Kompetenzen, Fragen) sind derzeit nur auf Englisch verfügbar.
Guides the technical direction of a single team while still contributing hands-on. Turns product goals into designs and plans, makes and records architectural decisions, and keeps the team's delivery and code quality healthy. Acts as a link between engineers, product and other teams.
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.
System Design
Zielniveau: vertieft / kann andere anleitenDesigning scalable, reliable systems by reasoning about requirements, components and trade-offs.
- Cloud design patterns (Azure Architecture Center) (reading, kostenlos)
- Pick a familiar product and sketch its design on paper: requirements, data model, scaling bottlenecks, failure modes; then explain it aloud in 20 minutes (practice, kostenlos)
Software Architecture
Zielniveau: vertieft / kann andere anleitenStructuring applications and landscapes for maintainability, quality attributes and change.
- Azure Architecture Guide (reading, kostenlos)
- Write three architecture decision records for real decisions in a project you know, including rejected options (practice, kostenlos)
Code Review
Zielniveau: vertieft / kann andere anleitenReviewing changes for correctness, readability and maintainability and giving constructive feedback.
- Google Engineering Practices: code review guide (reading, kostenlos)
Coaching & Mentoring
Zielniveau: vertieft / kann andere anleitenDeveloping others through feedback, coaching and mentoring.
- Mentor someone for three months with a written goal, and reflect on what changed (practice, kostenlos)
Communication
Zielniveau: vertieft / kann andere anleitenConveying 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.
Technical Strategy
Zielniveau: solide, selbstständigSetting 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)
Technical Writing
Zielniveau: vertieft / kann andere anleitenWriting clear documentation, design docs and decision records.
- Google Technical Writing courses (course, kostenlos)
Stakeholder Management
Zielniveau: solide, selbstständigAligning 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)
Agile Delivery
Zielniveau: solide, selbstständigDelivering iteratively with Scrum, Kanban and related practices.
- The Scrum Guide (reading, kostenlos)
- Manifesto for Agile Software Development (reading, kostenlos)
Prioritization
Zielniveau: solide, selbstständigDeciding what to do first using value, effort, risk and strategy.
- Prioritise a real backlog with two different frameworks and explain where they disagree (practice, kostenlos)
Delegation & Ownership
Zielniveau: solide, selbstständigDistributing 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)
Wünschenswert
Zusätzliche Stärken, die helfen, aber selten eine Voraussetzung sind.
Incident Management
Zielniveau: solide, selbstständigResponding to, communicating about and learning from production incidents.
- Managing Incidents, Google SRE book chapter (reading, kostenlos)
- Write a blameless postmortem for a past incident you were involved in: timeline, contributing factors, follow-up actions (practice, kostenlos)
Beispielhafte Interviewfragen
- Verhalten und Erfahrungen
Describe a situation where you had to say no to a request.
Shows a respectful no with reasons and alternatives, and the effect on the relationship.
- Verhalten und Erfahrungen
Describe a time when your priorities changed suddenly. How did you adapt?
Shows you can re-plan, communicate impacts and stop work cleanly, not simply absorb extra load silently.
- Verhalten und Erfahrungen
Describe a time you helped a teammate who was struggling.
Shows empathy and practical help while respecting their ownership. Explain how you noticed and what the result was.
- Verhalten und Erfahrungen
Describe how you handle competing requests from two senior stakeholders.
Shows you surface the conflict, give both parties the trade-offs and seek a decision from the right owner rather than quietly picking.
- Verhalten und Erfahrungen
How do you communicate bad news to your manager or a client?
Shows early, factual communication with impact, options and a plan, not waiting or softening it.
- Führung
How do you develop other people's skills without taking over their work?
Shows questioning, stretch tasks, feedback and tolerance for the other person's different way of solving things.
Alle Interviewfragen für General (any role) · 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.
- Engineering Manager7 gemeinsame Kompetenzen (54 % des Profils dieser Rolle)
- Senior Software Engineer7 gemeinsame Kompetenzen (54 % des Profils dieser Rolle)
- Solution Architect5 gemeinsame Kompetenzen (38 % des Profils dieser Rolle)
- Product Owner4 gemeinsame Kompetenzen (36 % des Profils dieser Rolle)
- Product Manager4 gemeinsame Kompetenzen (33 % des Profils dieser Rolle)
Vergleiche deinen Lebenslauf anhand eines transparenten Rasters mit Stellenanzeigen für Tech Lead.
Passungsanalyse ausprobieren