Zum Inhalt springen

Senior Software Engineer: Was die Rolle erfordert

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

Designs and delivers complex features end to end and is accountable for the quality of what ships. Shapes technical decisions within a team, reviews others' work and mentors less experienced colleagues. Balances delivery speed against maintainability and operational risk.

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 anleiten

    Designing 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 Testing

    Zielniveau: vertieft / kann andere anleiten

    Designing unit, integration and end-to-end tests and reasoning about test strategy.

  • Code Review

    Zielniveau: vertieft / kann andere anleiten

    Reviewing changes for correctness, readability and maintainability and giving constructive feedback.

  • 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.

  • Software Architecture

    Zielniveau: solide, selbstständig

    Structuring 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)
  • Coaching & Mentoring

    Zielniveau: solide, selbstständig

    Developing others through feedback, coaching and mentoring.

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

    Zielniveau: solide, selbstständig

    Measuring and improving latency, throughput and resource usage.

    • Profile a slow endpoint or page, record a baseline, make one change at a time and measure each result (practice, kostenlos)
  • Observability & Monitoring

    Zielniveau: solide, selbstständig

    Using logs, metrics and traces to understand and alert on system behaviour.

  • Security Fundamentals

    Zielniveau: solide, selbstständig

    Core application and infrastructure security: authentication, secrets, common vulnerabilities.

  • CI/CD

    Zielniveau: solide, selbstständig

    Automated build, test and deployment pipelines for frequent, safe releases.

    • GitHub Actions documentation (reading, kostenlos)
    • Set up a pipeline that builds, tests and deploys a sample app on every merge, with a rollback step (project, kostenlos)
  • REST API Design

    Zielniveau: vertieft / kann andere anleiten

    Designing consistent, versioned and well-documented HTTP APIs.

  • Technical Writing

    Zielniveau: solide, selbstständig

    Writing clear documentation, design docs and decision records.

Wünschenswert

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

  • Stakeholder Management

    Zielniveau: solide, selbstständig

    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)

Beispielhafte Interviewfragen

  1. 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.

  2. 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.

  3. Verhalten und Erfahrungen

    How do you handle a situation where you disagree with a decision after it has been made?

    Shows you can disagree and commit, voice concerns through the right channel, and avoid undermining the decision.

  4. Einstellende Führungskraft

    How do you prefer to receive feedback, and how do you give it?

    Shows maturity and self-awareness. Give an example of feedback that changed your behaviour, and describe how you make feedback specific and kind.

  5. Gesprächsrunde mit mehreren Beteiligten

    How would you work with the different disciplines in a cross-functional team, such as product, design and engineering?

    Show respect for each discipline's expertise and concrete collaboration habits like early involvement and shared goals.

  6. Verhalten und Erfahrungen

    Tell me about a time a stakeholder was unhappy with your work. How did you respond?

    Shows you sought to understand the real concern, took responsibility where due and rebuilt trust through actions.

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.

Vergleiche deinen Lebenslauf anhand eines transparenten Rasters mit Stellenanzeigen für Senior Software Engineer.

Passungsanalyse ausprobieren