Kokoaikainen kiinteistönhoitaja, Hyvinkää
About the role
... description ...
Responsibilities
- ... indoor tasks ...
- ... outdoor tasks ... maybe combine. But we need to preserve all substantive information; we should not lose details. Let's extract details: From "Kurkistus tulevaan työrooliisi": - Etsimme kiinteistönhoitajaa työskentelemään monipuolisissa kiinteistönhoidon tehtävissä. - Työskentelet sekä liike- että asuinkiinteistöissä, joissa tehtävät vaihtelevat sisä- ja ulkotöiden välillä. - Sisätöissä hoidat kiinteistöjen ylläpitoa, korjaus- ja huoltotöitä. - Ulkotöihin sisältyy vuodenaikojen mukaan esimerkiksi lumityöt, liukkaudentorjunta, nurmikon leikkuu sekä roskakierrokset ja liputukset. - Työ tarjoaa vaihtelevia tehtäviä joka päivä, joten toivomme joustavuutta ja hyvää asiakaspalveluasennetta. We can put that as About the role paragraph. Responsibilities: maybe we can list duties: sisätöissä (maintenance, repair, maintenance), ulkotöissä (lumityöt, liukkaudentorjunta, nurmikon leikkuu, roskakierrokset, liputukset). Also mention working in commercial and residential properties, varied tasks each day. Requirements: list from "Mitä työssä menestyminen edellyttää?": - Aiempaa kokemusta kiinteistönhoidosta - Koneiden ajotaito katsotaan eduksi - Kiinteistönhoitajan perus- tai ammattitutkintoa - B-ajokorttia - Työturvallisuuskortti katsotaan eduksi - Ratkaisukeskeistä asennetta ja oma-aloitteista työotetta - Vastuullisuutta ja järjestelmällisyyttä työtehtävissä - Sujuvaa suomen kielen taitoa, englannin kielen taito katsotaan eduksi We could separate Qualifications (education, licenses, certificates) and Skills (experience, language, attitude). But we can also combine into Requirements and Skills sections. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section "Requirements" that includes experience, education, licenses, certificates, language, attitude. Then Skills maybe not needed. But we need to include sections only when posting has real specific content. We have content for Requirements. For Skills we could include language skills and machine operation as skills, but that overlaps. Might be better to have Requirements (experience, education, licenses) and Skills (language, machine operation, attitude). However we risk thin sections. Let's think: The posting includes: - Experience: previous experience in property maintenance (requirement) - Machine operation skill considered an advantage (skill) - Qualification: basic or vocational qualification in property maintenance (qualification) - B driver's license (qualification/requirement) - Occupational safety card considered an advantage (qualification/advantage) - Solution-oriented attitude and proactive work approach (skill/attribute) - Responsibility and systematicness (skill/attribute) - Good Finnish language skill, English considered advantage (skill) Thus we could have sections: Requirements (experience, qualification, licenses, certificates) and Skills (language, machine operation, attitude, responsibility). But we need to avoid duplication. Alternatively, we could have one section "Requirements and Skills" but the instruction says use headings for specific categories like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid combining but we should follow headings if content exists. Since we have content for Requirements, Qualifications, Skills, we could output all three. But we must avoid thin sections; each should have substantive content. Let's see if each has enough: Requirements: previous experience in property maintenance (maybe also B license? but that's qualification). Could be just experience. Qualifications: basic or vocational qualification, B driver's license, occupational safety card (advantage). That's substantive. Skills: machine operation skill, solution-oriented attitude, responsibility, systematicness, Finnish language, English advantage. That's substantive. Thus we can have three sections. Responsibilities: we have duties. Benefits: from "Miksi Luotealle töihin?" we have many benefits: reliable employer, salary on time, thorough orientation, modern work equipment, supervisor support, competence development, occupational health support, broader services for full-time, nurse's sick reception for part-time, sickness fund for >20h/week. Pay: salary range: Kiinteistöpalvelualan TES pl 8-9 (16,55-17,22 €/h) + possible supplements. Schedule: Working time: primarily Mon-Fri 7:00-16:00, occasional weekend shifts. Location and start date maybe could be included in About the role or a separate meta but we are told not to create headings for Job ID etc. Location and start date could be placed in a short
under About the role or maybe a separate "About the role" includes location? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location, start date, employment type as a short paragraph maybe under About the role or separate? Probably we can include them in About the role paragraph as part of description. But we already have a description about role; we could add a sentence: "Sijainti: Hyvinkää, Uusimaa. Työsuhde: kokoaikainen (37,5 h/vk), vakituinen. Aloitus: 19.10.2026 / sopimuksen mukaan." That is minor metadata, we can fold into a short
. However we must not repeat job title. It's fine. Thus About the role could contain a short paragraph with location, employment type, start date, plus the role description. Alternatively we could have a separate
for metadata before the role description. But we need to output only HTML fragment; we can have multiple
elements. Let's structure:
About the role
Sijainti: Hyvinkää, Uusimaa. Työsuhde: kokoa