36 lines
1.1 KiB
Markdown
36 lines
1.1 KiB
Markdown
|
# Zielstellen-Profil
|
|||
|
|
|
|||
|
|
## Ideale Stellenbezeichnungen
|
|||
|
|
- [z.B. Senior Fullstack Developer]
|
|||
|
|
- [z.B. Lead Software Engineer]
|
|||
|
|
- [z.B. Backend Developer (Python/Node.js)]
|
|||
|
|
|
|||
|
|
## Must-Have Kriterien
|
|||
|
|
- [z.B. Remote-Option (mind. 80%)]
|
|||
|
|
- [z.B. Moderner Tech-Stack (kein COBOL/SAP)]
|
|||
|
|
- [z.B. Agile Arbeitsweise]
|
|||
|
|
- [z.B. Unbefristeter Vertrag]
|
|||
|
|
|
|||
|
|
## Nice-to-Have Kriterien
|
|||
|
|
- [z.B. Startup-/Scale-up-Kultur]
|
|||
|
|
- [z.B. Open-Source-Beteiligung]
|
|||
|
|
- [z.B. Weiterbildungsbudget]
|
|||
|
|
- [z.B. 4-Tage-Woche / flexible Arbeitszeiten]
|
|||
|
|
|
|||
|
|
## Relevante Keywords in Stellenausschreibungen
|
|||
|
|
- [z.B. React, TypeScript, Node.js, Python, PostgreSQL]
|
|||
|
|
- [z.B. Docker, Kubernetes, CI/CD, AWS/GCP]
|
|||
|
|
- [z.B. REST API, Microservices, Event-Driven]
|
|||
|
|
- [z.B. Agile, Scrum, Kanban]
|
|||
|
|
|
|||
|
|
## Ausschlusskriterien (Red Flags)
|
|||
|
|
- [z.B. "Rockstar Developer" / toxische Kultur-Signale]
|
|||
|
|
- [z.B. Keine Remote-Option]
|
|||
|
|
- [z.B. Veralteter Tech-Stack ohne Modernisierungsplan]
|
|||
|
|
- [z.B. Unbezahlte Überstunden erwartet]
|
|||
|
|
|
|||
|
|
## Unternehmensgröße
|
|||
|
|
- **Bevorzugt:** [z.B. 20–200 Mitarbeiter / Scale-up]
|
|||
|
|
- **Auch ok:** [z.B. Konzern mit autonomen Teams]
|
|||
|
|
- **Weniger passend:** [z.B. Einzelkämpfer-Rolle in Kleinstunternehmen]
|