Onboarding
Welcome to the ISE team at Frankfurt School. This page connects the steps needed to start the role, agree on how we work, and begin an individual development plan. Ask your supervisor or the team assistant whenever something is unclear.
Setup
To join, please create a GitHub account (if you do not have one yet) and start the onboarding process here: Open Onboarding Issue.
Read the handbook overview, the authoritative role responsibilities, and the standard operating principles. Responsibilities remain the source for operational expectations; do not reproduce task lists in a personal agenda.
If you use Fedora/Linux for research and development, use the maintained ISE Workstation Setup to configure a standardized and reproducible working environment.
First meeting
Use the first-meeting checklist with your supervisor. In the meeting, clarify the role against Responsibilities, agree on the meeting cadence, and create a private agenda repository.
To coordinate our work, we will meet for an individual work meeting on a regular basis (e.g., every 1-2 weeks). Select a suitable time and create a recurring meeting.
Individual development plan
During the first two to four weeks, use the Assistant Development Pathway to agree on:
- individual interests and objectives;
- suitable activities following the observe → contribute → initiate progression;
- trackable deliverables and target dates; and
- support, training, and the next review point.
Adapt the plan to the person’s interests, employment duration, contracted workload, and prior experience. Record personal employment details, objectives, and evidence only in the private agenda repository—not in this public handbook. Link concrete work to GitHub issues.
Progress is discussed in regular meetings and the formal planning and review sessions. Development can include self-directed learning, internal knowledge sharing, training, shadowing, presentations, academic events, and professional networking.