- Role: "Kamu penulis konten lowongan kerja Indonesia" (Indonesian job content writer)

• Role: "Kamu penulis konten lowongan kerja Indonesia" (Indonesian job content writer)

- Task: Rewrite given info into an attractive blog article (400-700 words) - Source: Perumda Pengelolaan Air Limbah Jaya (Paljaya), DKI Jakarta BUMD handling domestic wastewater - Source URL: https://www.disnakerja.com/rekrutmen-perumda-pengelolaan-air-limbah-jaya-paljaya/ - Format: Markdown with specific structure - Rules: - H1 title interesting - include company name + "Lowongan Kerja", max 60 chars - Intro 2-3 sentences about company/agency - H2 "Posisi yang Dibuka" - bullet list, minimum 3 reasonable positions for the industry - H2 "Kualifikasi Umum" - bullet list reasonable qualifications - H2 "Cara Melamar" - numbered steps + source link as anchor text "halaman resmi Rekrutmen Perumda Pengelolaan " - H2 "Tips Lolos Seleksi" - 3-4 short bullet tips - Language: Indonesian santai-profesional - Prohibited: Making up specific details (salary, address) - write "cek informasi lengkap di halaman resmi" - Start directly from H1, no introduction/pioneer - Don't mention these instructions - Company: Perumda Paljaya (BUMD Provinsi DKI Jakarta) - Field: pengelolaan air limbah domestik (domestic wastewater management) - Source: disnakerja.com job posting - Need to extract general info but keep it factual from the prompt, not invent specifics not given. - The system prompt gives me a persona: "lazy senior developer" but the user request is about writing job content. I need to adapt the "lazy" principles? Wait, the system prompt is a meta-instruction about how I should behave as an AI, but the user request is specific: "Kamu penulis konten lowongan kerja Indonesia." The system prompt is about coding/technical writing, but I must follow the user's current request format and rules. However, the system prompt says "ACTIVE EVERY RESPONSE" and gives patterns. I need to integrate the requested format while adhering to the system's operational guidelines if applicable, but the user request is the primary task. Let me re-read carefully.

Actually, the system prompt is a set of core instructions for me as an AI. It covers various scenarios. The user request is "Kamu penulis konten lowongan kerja Indonesia." I need to output in the specified Markdown format. The system prompt's "lazy developer" etc. might not directly apply to content writing, but I should keep it concise, avoid fluff, follow the format exactly, and not add extra stuff. The "ACTIVE EVERY RESPONSE" means I should be engaged and follow the pattern. The format pattern at the end: [code] → skipped: [X], add when [Y]. But that seems like a general pattern for me to output if I skip things. The user wants a specific output. I'll focus on the user request format.

Let me extract the key requirements from the user prompt:
- Output Markdown
- H1: max 60 chars, include company name + "Lowongan Kerja"
- Intro: 2-3 sentences about company/agency
- H2 "Posisi yang Dibuka": bullet list, min 3 positions reasonable for the industry
- H2 "Kualifikasi Umum": bullet list reasonable qualifications
- H2 "Cara Melamar": numbered steps + link source as anchor text "halaman resmi Rekrutmen Perumda Pengelolaan "
- H2 "Tips Lolos Seleksi": 3-4 short bullet tips
- Language: Indonesian santai-profesional
- No made-up specifics (salary, address) -> "cek informasi lengkap di halaman resmi"
- Start directly from H1, no preamble
- Don't mention instructions

I'll construct the content based on the provided info. I need to make up reasonable positions and qualifications that fit a wastewater management BUMD in Jakarta, but without inventing specific details not in the source. The source is a job posting on disnakerja.com. I can infer typical positions: Operator, Admin, Engineer, etc. But I must be careful not to hallucinate exact titles or numbers if not certain. I'll keep it generic but reasonable, and note "cek informasi lengkap di halaman resmi" for specifics.

Let's draft:

H1: Rekrutmen Perumda Pengelolaan Air Limbah Jaya Paljaya Lowongan Kerja
(Check char count: "Rekrutmen Perumda Pengelolaan Air Limbah Jaya Paljaya Lowongan Kerja" = let's count: Rekrutmen(9) + space(1) + Perumda(6) + space(1) + Pengelolaan(10) + space(1) + Air(3) + space(1) + Limbah(6) + space(1) + Jaya(4) + space(1) + Lowongan(8) + space(1) + Kerja(5) = 9+1+6+1+10+1+3+1+6+1+4+1+8+1+5 = 62. Oops, over 60. I need max 60 chars. I'll trim. Maybe: "Rekrutmen Perumda Paljaya Lowongan Kerja" - Count: Rekrutmen(9)+space(1)+Perumda(6)+space(1)+Paljaya(6)+space(1)+Lowongan(8)+space(1)+Kerja(5) = 38. Good, but does it include "Pengelolaan Air Limbah"? The rule says "sertakan nama perusahaan + kata 'Lowongan Kerja'". Perusahaan is Perumda Paljaya. I can include the field briefly but keep under 60. Let's try: "Rekrutmen Perumda Paljaya Lowongan Kerja" - 38 chars. Safe. Or "Perumda Paljaya Lowongan Kerja Pengelolaan Air" - count: Perumda(6)+space(1)+Paljaya(6)+space(1)+Lowongan(8)+space(1)+Kerja(5)+space(1)+Pengelolaan(10)+space(1)+Air(3) = 42. Good. I'll use: "Perumda Paljaya Lowongan Kerja Pengelolaan Air" - under 60. Actually, the rule: "sertakan nama perusahaan + kata 'Lowongan Kerja'". Nama perusahaan is "Perumda Pengelolaan Air Limbah Jaya (Paljaya)" per the prompt, but the short name is Perumda Paljaya. I'll do: "Rekrutmen Perumda Paljaya Lowongan Kerja" - that's fine. I'll keep it simple: "Rekrutmen Perumda Paljaya Lowongan Kerja" (38 chars). It includes company name and "Lowongan Kerja". Good.

Wait, the prompt says: "H1 judul menarik — sertakan nama perusahaan + kata "Lowongan Kerja", maks 60 karakter". So I need company name + "Lowongan Kerja". I'll do: "Rekrutmen Perumda Paljaya Lowongan Kerja". That's safe.

Intro: 2-3 sentences about Perumda Paljaya as BUMD DKI Jakarta in domestic wastewater management. Keep it professional-simple.

H2 "Posisi yang Dibuka": bullet list, min 3 positions. I'll list reasonable ones: "Operator Pengelolaan Air Limbah", "Staf Administrasi", "Teknis Pengawasan". Or keep generic: "Posisan Teknis", "Posisan Administrasi", "Posisan Support". I'll make them plausible.

H2 "Kualifikasi Umum": bullet list: diploma/minimum, relevant field, age, etc. But no specifics. I'll keep it general: "Pendidikan minimal SMA/SMK/D3/S1 sesuai bidang", "Pernalatan administrasi", "Mengetahui prosedur pengelolaan air limbah". Actually, I should not invent too much. I'll stick to generic that fits.

H2 "Cara Melamar": numbered steps. Step 1: Klik link berikut. Step 2: Isi formulir. Step 3: Tunggu proses. Anchor text: "halaman resmi Rekrutmen Perumda Pengelolaan" linking to the URL. The rule: "link sumber sebagai anchor text "halaman resmi