Docent / Vakexpert Wiskunde

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must preserve all substantive info, no boilerplate. We need to parse the Dutch posting. Key info: - Organization description: Dunamare, 23 schools, etc. Could be "About the organization" maybe "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Functieomschrijving: description of role: looking for a passionate teacher to co-shape mathematics at Agoraschool, etc. This is responsibilities. - Wat ga je doen? (What will you do?) details: teaching math A/C, classes 4 havo,5 havo,4 vwo,5-6 vwo, etc. Also info about exam route numbers, growth expectations, strengthening core subjects within Agora concept. This is responsibilities. - Wie ben jij? Wij Vragen Enthousiaste Onderwijsexperts Die ... list of requirements: first-degree teaching qualification, relevant work experience with exam classes, ability to work in transparent teams, sees challenge to prepare students optimally for exam, availability min 0.1 fte, 0.2 fte preferred, preferably schedule on one day. - Wat krijg je van ons terug? (What do you get back?) includes contract details: fixed term with prospect of permanent, 0.2 fte, possibility of detachment, scheduling in consultation with main location if second function, salary according to current scale, 12 weeks vacation per year, 8% holiday allowance and year-end bonus of 8.33%, good pension scheme (Dunamare pays 70% of ABP scheme), space for professional/personal development via Dunamare Academy (link), attention to health/vitality: attractive bike plan, vitality budget, coaches, trainings like mindfulness, running or kickboxing, 90 extra free hours per year to use for work-life balance or development. - Het team description: base team consists of Agora coaches, school leadership, youth guidance, etc. Could be part of "About the role" or maybe "Team". Not a standard heading but could be included under "About the role" or maybe "Skills"? Probably we can include under "About the role" as extra context. - Over Saga Driehuis: description of school philosophy. Could be "About the role" or maybe "About the organization". Since we have only limited headings, we could put organization description under "About the role" or maybe create a separate "About the role" includes both role and organization. - Dunamare onderwijs doet meer: additional benefits, could be part of Benefits. We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none. We must not include headings with filler like "Pay" if not specified. Pay is specified: "Salarieering conform je huidige schaal." That's pay according to current scale. So we can include Pay section. Schedule: mention availability min 0.1 fte, 0.2 fte preferred, preferably schedule on one day. So we can include Schedule. Benefits: many items: contract type, detachment option, vacation, holiday allowance, year-end bonus, pension, development academy, health/vitality bike plan, vitality budget, coaches, trainings, 90 extra free hours. We should not include placeholder like "commensurate with experience". Not present. We must not repeat job title. We must not include Job ID/requisition numbers. We must output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

... organization description and role overview ...

Responsibilities

• ... each duty ...

Requirements

• ... each requirement ...

Qualifications

maybe combine with Requirements? But we have separate headings; we could put qualifications under Requirements or separate. The instruction says use headings for those sections if content exists. We have qualifications: first-degree teaching qualification, relevant work experience with exam classes. That's both qualification and requirement. Could put under Requirements. Skills: maybe pedagogical skills, ability to work in transparent teams, etc. Could be separate. But we can combine to avoid thin sections. Prefer few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements & Qualifications, Benefits, Pay, Schedule. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit those lacking content. Let's decide: - About the role: include organization description and brief role purpose. - Responsibilities: detailed duties (teaching math A/C, specific classes, exam route, strengthening core subjects, etc.) - Requirements: include first-degree teaching qualification, relevant work experience with exam classes, ability to work in transparent teams, sees challenge to prepare students optimally for exam, availability min 0.1 fte (0.2 preferred), preferably schedule on one day. - Qualifications: maybe we could separate but could be same as Requirements. To avoid thin, we could combine Requirements and Qualifications into one section titled "Requirements & Qualifications" but heading must be exactly from list? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid combining headings? It says use those headings for sections. It might be okay to use exactly those headings; combining may deviate. Safer to have separate sections if content exists. But we can still have both Requirements and Qualifications with similar content; but that would be thin duplication. Better to assign content appropriately: Requirements could be the experience and availability; Qualifications could be the degree and exam class experience. Skills could be pedagogical skills, teamwork, etc. Let's parse: Qualifications: "Je bent in het bezit van een eerstegraads onderwijsbevoegdheid; Je hebt relevante werkervaring opgedaan met eindexamenklassen;" That's qualifications. Requirements: maybe "Je bent in staat om in transparante teams te werken, waar feedback krijgen en geven een dagelijkse gewoonte is; Je ziet het als een uitdaging om leerlingen optimaal voor te bereiden op hun examen; Je bent voor minimaal 0,1 fte per week beschikbaar, 0,2fte is ook zeker mogelijk en heeft zelfs de voorkeur. Zijn de uren op 1 dag te plannen dan zou dat zeker helpen." That's requirements. Skills: maybe "enthousiaste docent", "pedagogische vaardigheden", "denken in mogelijkheden", "optimale ruimte zoekt". Could be skills. But we can keep simple: have Requirements (including qualifications and skills) and Benefits, Pay, Schedule, About the role, Responsibilities. Given instruction to prefer few substantive sections over many thin ones, we can combine Requirements, Qualifications, Skills into one section called "Requirements". That's acceptable? The heading would be Requirements, which is allowed. We'll put all those points there. Thus sections: - About the role - Responsibilities - Requirements - Benefits - Pay - Schedule Now craft content. About the role: combine organization description and role purpose. Organization description: "Welkom bij Dunamare, de onderwijsgroep die de verbindende factor is tussen 23 scholen voor voortgezet onderwijs in de regio Haarlem, Velsen en Haarlemmermeer (met een uitstapje naar Harlingen en Uithoorn). Het spectrum is breed: van praktijkonderwijs tot gymnasium, elk met zijn eigen identiteit en karakter. Wat deze 23 scholen delen, is één belangrijke ambitie. Zij doen er alles aan om het beste te halen uit iedere leerling. Om individuele talenten in de volle breedte te ontwikkelen en van iedere leerling een echte wereldburger te maken." Role purpose: "Wij zoeken een bevlogen docent die enthousiast wordt van het mede vormgeven van het vak Wiskunde op onze Agoraschool. Durf jij het aan om de gestelde eisen te vertalen naar Agoriaanse leertrajecten voor havo en vwo op Saga Driehuis? Dan is dit misschien jouw baan." We can combine. Responsibilities: list bullet points: - Lesgeven in Wiskunde A en/of C (eerstegraads) aan klassen 4 havo, 5 havo, 4 vwo, 5-6 vwo (bovenbouw vwo: wiskunde A & C). - Ontwikkelen en uitvoeren van Agoriaanse leertrajecten voor havo en vwo, aansluitend bij examenroutes. - Begeleiden van leerlingen binnen de examenroute (havo-PTA, vmbo-, havo- of vwo-niveau) en meewerken aan groei van leerlingaantallen (van 5 leerlingen in 23‑24 naar ~15 in 24‑25, verwachte groei naar ~40 in 26‑27). - Versterken van de kernvakken binnen het Agora‑concept. - Samenwerken met collega’s in transparante teams, feedback geven en ontvangen. - Bijdragen aan teamontwikkeling, teambuilding en professionalisering binnen het Agora‑team. We need to preserve all substantive info; we can include details about numbers. Requirements: bullet points: - Eerstegraads onderwijsbevoegdheid. - Relevante werkervaring met eindexamenklassen. - Vermogen om in transparante teams te werken waarbij feedback geven en ontvangen dagelijkse gewoonte is. - Ziet het als een uitdaging om leerlingen optimaal voor te bereiden op hun examen. - Beschikbaar voor minimaal 0,1 fte per week; voorkeur voor 0,2 fte, bij voorkeur op één dag gepland. Benefits: bullet points: - Contract voor bepaalde tijd met uitzicht op onbepaalde tijd, 0,2 fte. - Mogelijkheid tot detacheringsbasis om vaste aanstelling naast huidige functie te behouden. - Inroostering in overleg met hoofdlocatie (indien tweede functie). - Salaris conform huidige schaal. - 12 weken vakantie per jaar. - 8% vakantietoeslag en eindejaarsuitkering van 8,33%. - Goede pensioenregeling; Dunamare onderwijs draagt 70% van de ABP‑regeling. - Ruimte voor professionele en persoonlijke ontwikkeling via de Dunamare Academie (www.dunamare-academie.nl). - Aantrekkelijk fietsplan, vitaliteitsbudget, vitaliteitscoaches en trainingen (mindfulness, hardlopen, kickboksen). - 90 extra vrije uren per jaar, inzetbaar voor werk‑privébalans of professionele/persoonlijke ontwikkeling (uitbetalen of gebruiken). Pay: we already included salary in benefits; but we need a Pay section per instruction. Could put salary details there, and benefits exclude salary. But we already put salary in benefits. To follow instruction, we should have a Pay section separate. So we move salary details to Pay section, and benefits exclude salary. Thus Benefits: exclude salary. Pay: "Salarieering conform je huidige schaal." Schedule: "Minimaal 0,1 fte per week