VA-ingenjör med fokus på tillskotsvatten och ledningsnät
for each section heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Content:
- Plats Blekinge län, Karlskrona Sista ansökningsdag 2026-10-12 (metadata)
- Intro text about public sector, etc. (some boilerplate about public sector, application being public record, identity verification, etc.) This is likely boilerplate but includes some specifics: identity verification requirements, protected personal data, etc. Might be considered boilerplate but maybe we need to keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The identity verification and protected personal data might be considered legal boilerplate. Likely we should drop that. The intro about public sector being fun and important maybe also boilerplate? It's generic but maybe we keep as "About the role"? However we need to preserve substantive information: job description, responsibilities, qualifications, etc.
Let's extract substantive sections:
Jobbeskrivning (Job description)
Om arbetsplatsen (About the workplace)
Arbetsuppgifter (Tasks)
Andra arbetsuppgifter inom enhetens verksamhetsområde kan förekomma utifrån verksamhetens behov. Beredskap kan ingå i tjänsten.
Kvalifikationer
Krav
- Utbildning som VA-ingenjör eller annan utbildning som arbetsgivaren bedömer som likvärdig.
- Tidigare erfarenhet och kunskap inom tillskottsvattenarbete.
- God förståelse för hydrauliska beräkningar och dimensionering.
- Erfarenhet av projektering av VA-ledningar samt arbete i CAD- och GIS-system.
- B-körkort är ett krav.
Personliga Egenskaper
- Strukturerad och noggrann med god förmåga att planera och prioritera.
- Kommunikativ och samarbetsinriktad.
- Lösningsorienterad och initiativtagande.
Meriterande
- Erfarenhet av arbete inom kommunal VA-verksamhet.
- Utbildning och/eller erfarenhet inom VA-taxa och KFVA.
- Kunskap om entreprenadjuridik och upphandlingsprocesser.
Anställningens omfattning
Anställningsform: Tillsvidareanställning
Omfattning: Heltid
Tillträde: Enligt överenskommelse
Varaktighet: Tillsvidare
Ansökan
Ansök senast: 2026-10-12
Referensnummer: C342030
Anställning Antal annonserade arbetstillfällen: 1
Arbetstid: Dagtid
Kontakt
Kontaktperson Reto Lerch Rörnätschef Mobiltelefon Telefon +46455321417 E-postadress reto.lerch@karlskrona.se
Facklig företrädare Nicklas Lundström Vision Mobiltelefon Telefon +46455303261 E-postadress Nicklas.Lundstrom@karlskrona.se
Övrigt
Urval och intervjuer sker löpande, och tjänsten kan tillsättas innan sista ansökningsdag.
I Karlskrona kommun har du som medarbetare ett flertal förmåner. Några av de förmånerna är extra semesterdagar när du når en viss ålder, friskvårdsbidrag, möjligheten att gratis simma i någon av kommunens simhallar och ett riktigt bra tjänstepensionsavtal.
Vill du veta var vi finns? Se arbetsplatsen på karta här
We need to decide which sections to include: About the role (maybe from Om arbetsplatsen and intro), Responsibilities (Arbetsuppgifter), Requirements/Qualifications (Krav and Personliga Egenskaper maybe as Requirements), Skills (maybe Meriterande as Skills?), Benefits (the paragraph about benefits), Pay (not mentioned), Schedule (Arbetstid: Dagtid, maybe schedule). Also we have Tillträde (start date) and Anställningsform etc. Might be considered metadata but could be placed in a short p.
We must not create Pay/Schedule/Benefits unless posting actually states them. Benefits are stated: extra semesterdagar, friskvårdsbidrag, gratis sim, tjänstepensionsavtal. So we can include Benefits section.
Schedule: Arbetstid: Dagtid (working hours daytime). That's a schedule detail. So we can include Schedule section.
Pay: Not mentioned, so omit.
We need to avoid duplication. Also we need to avoid putting Job ID/requisition numbers as headings; we can fold into a short p.
We need to use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
Thus we need to include:
- About the role: maybe combine Om arbetsplatsen and intro about ambitions. The intro: "I Karlskrona är våra ambitioner höga och vi brinner för att utveckla den moderna staden i havet. Nu söker vi dig som vill vara med och göra skillnad. Välkommen till Blekinges största arbetsgivare, där dina möjligheter att utvecklas är goda." That's substantive about the workplace. Also "Om arbetsplatsen" repeats similar. We'll combine into a prose
.
- Responsibilities: Arbetsuppgifter section: list of duties. We'll make a
- list.
- Requirements: Krav (requirements) and Personliga Egenskaper (personal traits). Could be combined as Requirements? Or separate sections: Requirements and Skills? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Qualifications maybe for education/experience; Skills for personal traits/meritorious. But we can decide.
Better: Use "Requirements" for Krav (education, experience, B-körkort). Use "Skills" for Personliga Egenskaper and Meriterande (maybe as Skills). Or we could have "Qualifications" for education/experience and "Skills" for personal traits. Let's see.
We have Krav: education as VA-ingenjör or equivalent, tidigare erfarenhet inom tillskottsvattenarbete, god förståelse för hydrauliska beräkningar och dimensionering, erfarenhet av projektering av VA-ledningar samt arbete i CAD- och GIS-system, B-körkort.
Personliga Egenskaper: strukturerad och noggrann, kommunikativ och samarbetsinriktad, lösningsorienterad och initiativtagande.
Meriterande: erfarenhet inom kommunal VA-verksamhet, utbildning och/eller erfarenhet inom VA-taxa och KFVA, kunskap om entreprenadjuridik och upphandlingsprocesser.
Thus we could have:
- Requirements: Krav (list)
- Skills: Personliga Egenskaper + Meriterande (list) maybe.
But we also have "Qualifications" maybe for education/experience; but we already used Requirements for that. Could also have Qualifications for education/experience and Skills for personal traits. However we need to avoid thin sections; better to combine.
We'll create:
About the role
... (combined intro)
Responsibilities
- ... each duty
Requirements
- ... each krav
Skills
- ... personliga egenskaper
- ... meriterande
maybe separate items.
Benefits
... benefits paragraph
Schedule
Arbetstid: Dagtid
We also need to include maybe start date and employment type? Could be placed in a short p under About the role or separate? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short or drop it. So we can include a short p for metadata like "Anställningsform: Tillsvidareanställning, Omfattning: Heltid, Tillträde: Enligt överenskommelse, Varaktighet: Tillsvidare". That's minor metadata; we can put in a
maybe under About the role or separate small section? But we shouldn't create a heading for it. So we can add a
after About the role containing that.
Also we need to include application deadline? That's also metadata; we could fold into a short p as well. But we already have schedule section for working hours; deadline maybe also metadata. Could add a p: "Sista ansökningsdag: 2026-10-12". Or we could drop it? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The deadline is substantive. So we need to keep it. We can put it in a
maybe under About the role or separate small paragraph.
We also need to include contact info? That's also metadata; we could fold into a short p. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Contact info is minor metadata; we can include in a p.
We need to avoid duplication: there are duplicated lines like "Jag har tagit del av ovanstående information och vill gå vidare med min ansökan." repeated; we should drop those.
Also we need to drop the application instructions like "Ja Välj ett alternativ." etc.
Now craft HTML.
We need to ensure we only output HTML fragment, no /, no markdown fences.
Let's draft:
About the role
I Karlskrona är våra ambitioner höga och vi brinner för att utveckla den moderna staden i havet. Nu söker vi dig som vill vara med och göra skillnad. Välkommen till Blekinges största arbetsgivare, där dina möjligheter att utvecklas är goda.
Anställningsform: Tillsvidareanställning, Omfattning: Heltid, Tillträde: Enligt överenskommelse, Varaktighet: Tillsvidare. Sista ansökningsdag: 2026-10-12.
Kontaktperson: Reto Ler
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: - Plats Blekinge län, Karlskrona Sista ansökningsdag 2026-10-12 (metadata) - Intro text about public sector, etc. (some boilerplate about public sector, application being public record, identity verification, etc.) This is likely boilerplate but includes some specifics: identity verification requirements, protected personal data, etc. Might be considered boilerplate but maybe we need to keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The identity verification and protected personal data might be considered legal boilerplate. Likely we should drop that. The intro about public sector being fun and important maybe also boilerplate? It's generic but maybe we keep as "About the role"? However we need to preserve substantive information: job description, responsibilities, qualifications, etc. Let's extract substantive sections: Jobbeskrivning (Job description) Om arbetsplatsen (About the workplace) Arbetsuppgifter (Tasks) Andra arbetsuppgifter inom enhetens verksamhetsområde kan förekomma utifrån verksamhetens behov. Beredskap kan ingå i tjänsten. Kvalifikationer Krav - Utbildning som VA-ingenjör eller annan utbildning som arbetsgivaren bedömer som likvärdig. - Tidigare erfarenhet och kunskap inom tillskottsvattenarbete. - God förståelse för hydrauliska beräkningar och dimensionering. - Erfarenhet av projektering av VA-ledningar samt arbete i CAD- och GIS-system. - B-körkort är ett krav. Personliga Egenskaper - Strukturerad och noggrann med god förmåga att planera och prioritera. - Kommunikativ och samarbetsinriktad. - Lösningsorienterad och initiativtagande. Meriterande - Erfarenhet av arbete inom kommunal VA-verksamhet. - Utbildning och/eller erfarenhet inom VA-taxa och KFVA. - Kunskap om entreprenadjuridik och upphandlingsprocesser. Anställningens omfattning Anställningsform: Tillsvidareanställning Omfattning: Heltid Tillträde: Enligt överenskommelse Varaktighet: Tillsvidare Ansökan Ansök senast: 2026-10-12 Referensnummer: C342030 Anställning Antal annonserade arbetstillfällen: 1 Arbetstid: Dagtid Kontakt Kontaktperson Reto Lerch Rörnätschef Mobiltelefon Telefon +46455321417 E-postadress reto.lerch@karlskrona.se Facklig företrädare Nicklas Lundström Vision Mobiltelefon Telefon +46455303261 E-postadress Nicklas.Lundstrom@karlskrona.se Övrigt Urval och intervjuer sker löpande, och tjänsten kan tillsättas innan sista ansökningsdag. I Karlskrona kommun har du som medarbetare ett flertal förmåner. Några av de förmånerna är extra semesterdagar när du når en viss ålder, friskvårdsbidrag, möjligheten att gratis simma i någon av kommunens simhallar och ett riktigt bra tjänstepensionsavtal. Vill du veta var vi finns? Se arbetsplatsen på karta här We need to decide which sections to include: About the role (maybe from Om arbetsplatsen and intro), Responsibilities (Arbetsuppgifter), Requirements/Qualifications (Krav and Personliga Egenskaper maybe as Requirements), Skills (maybe Meriterande as Skills?), Benefits (the paragraph about benefits), Pay (not mentioned), Schedule (Arbetstid: Dagtid, maybe schedule). Also we have Tillträde (start date) and Anställningsform etc. Might be considered metadata but could be placed in a short p. We must not create Pay/Schedule/Benefits unless posting actually states them. Benefits are stated: extra semesterdagar, friskvårdsbidrag, gratis sim, tjänstepensionsavtal. So we can include Benefits section. Schedule: Arbetstid: Dagtid (working hours daytime). That's a schedule detail. So we can include Schedule section. Pay: Not mentioned, so omit. We need to avoid duplication. Also we need to avoid putting Job ID/requisition numbers as headings; we can fold into a short p. We need to use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
Thus we need to include:
- About the role: maybe combine Om arbetsplatsen and intro about ambitions. The intro: "I Karlskrona är våra ambitioner höga och vi brinner för att utveckla den moderna staden i havet. Nu söker vi dig som vill vara med och göra skillnad. Välkommen till Blekinges största arbetsgivare, där dina möjligheter att utvecklas är goda." That's substantive about the workplace. Also "Om arbetsplatsen" repeats similar. We'll combine into a prose
.
- Responsibilities: Arbetsuppgifter section: list of duties. We'll make a
- list.
- Requirements: Krav (requirements) and Personliga Egenskaper (personal traits). Could be combined as Requirements? Or separate sections: Requirements and Skills? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Qualifications maybe for education/experience; Skills for personal traits/meritorious. But we can decide.
Better: Use "Requirements" for Krav (education, experience, B-körkort). Use "Skills" for Personliga Egenskaper and Meriterande (maybe as Skills). Or we could have "Qualifications" for education/experience and "Skills" for personal traits. Let's see.
We have Krav: education as VA-ingenjör or equivalent, tidigare erfarenhet inom tillskottsvattenarbete, god förståelse för hydrauliska beräkningar och dimensionering, erfarenhet av projektering av VA-ledningar samt arbete i CAD- och GIS-system, B-körkort.
Personliga Egenskaper: strukturerad och noggrann, kommunikativ och samarbetsinriktad, lösningsorienterad och initiativtagande.
Meriterande: erfarenhet inom kommunal VA-verksamhet, utbildning och/eller erfarenhet inom VA-taxa och KFVA, kunskap om entreprenadjuridik och upphandlingsprocesser.
Thus we could have:
- Requirements: Krav (list)
- Skills: Personliga Egenskaper + Meriterande (list) maybe.
But we also have "Qualifications" maybe for education/experience; but we already used Requirements for that. Could also have Qualifications for education/experience and Skills for personal traits. However we need to avoid thin sections; better to combine.
We'll create:
About the role
... (combined intro)
Responsibilities
- ... each duty
Requirements
- ... each krav
Skills
- ... personliga egenskaper
- ... meriterande
maybe separate items.
Benefits
... benefits paragraph
Schedule
Arbetstid: Dagtid
We also need to include maybe start date and employment type? Could be placed in a short p under About the role or separate? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short or drop it. So we can include a short p for metadata like "Anställningsform: Tillsvidareanställning, Omfattning: Heltid, Tillträde: Enligt överenskommelse, Varaktighet: Tillsvidare". That's minor metadata; we can put in a
maybe under About the role or separate small section? But we shouldn't create a heading for it. So we can add a
after About the role containing that.
Also we need to include application deadline? That's also metadata; we could fold into a short p as well. But we already have schedule section for working hours; deadline maybe also metadata. Could add a p: "Sista ansökningsdag: 2026-10-12". Or we could drop it? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The deadline is substantive. So we need to keep it. We can put it in a
maybe under About the role or separate small paragraph.
We also need to include contact info? That's also metadata; we could fold into a short p. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Contact info is minor metadata; we can include in a p.
We need to avoid duplication: there are duplicated lines like "Jag har tagit del av ovanstående information och vill gå vidare med min ansökan." repeated; we should drop those.
Also we need to drop the application instructions like "Ja Välj ett alternativ." etc.
Now craft HTML.
We need to ensure we only output HTML fragment, no /, no markdown fences.
Let's draft:
About the role
I Karlskrona är våra ambitioner höga och vi brinner för att utveckla den moderna staden i havet. Nu söker vi dig som vill vara med och göra skillnad. Välkommen till Blekinges största arbetsgivare, där dina möjligheter att utvecklas är goda.
Anställningsform: Tillsvidareanställning, Omfattning: Heltid, Tillträde: Enligt överenskommelse, Varaktighet: Tillsvidare. Sista ansökningsdag: 2026-10-12.
Kontaktperson: Reto Ler
for prose. We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to include: - About the role: maybe combine Om arbetsplatsen and intro about ambitions. The intro: "I Karlskrona är våra ambitioner höga och vi brinner för att utveckla den moderna staden i havet. Nu söker vi dig som vill vara med och göra skillnad. Välkommen till Blekinges största arbetsgivare, där dina möjligheter att utvecklas är goda." That's substantive about the workplace. Also "Om arbetsplatsen" repeats similar. We'll combine into a prose
. - Responsibilities: Arbetsuppgifter section: list of duties. We'll make a
- list.
- Requirements: Krav (requirements) and Personliga Egenskaper (personal traits). Could be combined as Requirements? Or separate sections: Requirements and Skills? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Qualifications maybe for education/experience; Skills for personal traits/meritorious. But we can decide.
Better: Use "Requirements" for Krav (education, experience, B-körkort). Use "Skills" for Personliga Egenskaper and Meriterande (maybe as Skills). Or we could have "Qualifications" for education/experience and "Skills" for personal traits. Let's see.
We have Krav: education as VA-ingenjör or equivalent, tidigare erfarenhet inom tillskottsvattenarbete, god förståelse för hydrauliska beräkningar och dimensionering, erfarenhet av projektering av VA-ledningar samt arbete i CAD- och GIS-system, B-körkort.
Personliga Egenskaper: strukturerad och noggrann, kommunikativ och samarbetsinriktad, lösningsorienterad och initiativtagande.
Meriterande: erfarenhet inom kommunal VA-verksamhet, utbildning och/eller erfarenhet inom VA-taxa och KFVA, kunskap om entreprenadjuridik och upphandlingsprocesser.
Thus we could have:
- Requirements: Krav (list)
- Skills: Personliga Egenskaper + Meriterande (list) maybe.
But we also have "Qualifications" maybe for education/experience; but we already used Requirements for that. Could also have Qualifications for education/experience and Skills for personal traits. However we need to avoid thin sections; better to combine.
We'll create:
About the role
... (combined intro)
Responsibilities
- ... each duty
Requirements
- ... each krav
Skills
- ... personliga egenskaper
- ... meriterande
Benefits
... benefits paragraph
Schedule
Arbetstid: Dagtid
We also need to include maybe start date and employment type? Could be placed in a short p under About the role or separate? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a shortor drop it. So we can include a short p for metadata like "Anställningsform: Tillsvidareanställning, Omfattning: Heltid, Tillträde: Enligt överenskommelse, Varaktighet: Tillsvidare". That's minor metadata; we can put in a
maybe under About the role or separate small section? But we shouldn't create a heading for it. So we can add a
after About the role containing that. Also we need to include application deadline? That's also metadata; we could fold into a short p as well. But we already have schedule section for working hours; deadline maybe also metadata. Could add a p: "Sista ansökningsdag: 2026-10-12". Or we could drop it? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The deadline is substantive. So we need to keep it. We can put it in a
maybe under About the role or separate small paragraph. We also need to include contact info? That's also metadata; we could fold into a short p. The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Contact info is minor metadata; we can include in a p. We need to avoid duplication: there are duplicated lines like "Jag har tagit del av ovanstående information och vill gå vidare med min ansökan." repeated; we should drop those. Also we need to drop the application instructions like "Ja Välj ett alternativ." etc. Now craft HTML. We need to ensure we only output HTML fragment, no /, no markdown fences. Let's draft:
About the role
I Karlskrona är våra ambitioner höga och vi brinner för att utveckla den moderna staden i havet. Nu söker vi dig som vill vara med och göra skillnad. Välkommen till Blekinges största arbetsgivare, där dina möjligheter att utvecklas är goda.
Anställningsform: Tillsvidareanställning, Omfattning: Heltid, Tillträde: Enligt överenskommelse, Varaktighet: Tillsvidare. Sista ansökningsdag: 2026-10-12.
Kontaktperson: Reto Ler