Marketing Coordinator

Here's a thinking process: 1. **Analyze the Request:** - Input: A job posting for "Marketing Coordinator" at Kidder Mathews. - Task: Reformat into clean, well-structured semantic HTML. - Rules: - Use `

` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). - Use `

• ` for lists of duties/requirements/benefits. - Use `

  ` for prose. - Do NOT repeat the job title as a heading (page already shows it). - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. - Output ONLY the HTML fragment — no `/`, no markdown code fences. 2. **Analyze the Input Text:** - Company info: Kidder Mathews, 60 years, workplace awards, largest fully independent CRE firm in Western US, 900 professionals, 19 offices, services, transaction volume, space managed, assignments annually. - Job Summary: Marketing Coordinator role description. - Essential Functions: List of duties/responsibilities. - Essential Qualifications: Knowledge, Skills & Ability, Education-Certification, Experience Required. - Work Environment: Standard office environment, physical demands. - Supervisory Responsibilities: None. - EEO/Equal Opportunity boilerplate at the end. - Location-specific notes (AZ, NV, OR, WA E-Verify; CA data privacy). - Application contact info. - Need to remove: EEO statement, E-Verify mention, CA data privacy notice, application instructions ("Please contact..."), scam warning, duplicated lines, job title repetition, job ID/requisition (not present anyway). - Need to keep: Company description, job summary, essential functions, qualifications, skills, work environment, physical demands. - Section mapping per rules: - "About the role" could combine company intro + job summary, but rules say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only create if real content. - Let's map the actual content to these headings: - "About the role" / Job Summary: The first paragraph after "Job Summary" describes the role. Could use `

  About the role

  ` or maybe just keep it as prose. The rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I'll use headings that match content present. - "Responsibilities": Essential Functions list. - "Requirements" or "Qualifications": Essential Qualifications section. The heading options include "Requirements" and "Qualifications". I'll pick one or combine. The rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I'll use "Requirements" or "Qualifications". Let's see the content: it has "Required Knowledge", "Skills & Ability", "EDUCATION-CERTIFICATION", "Experience Required". I'll structure it as "Qualifications" with sub-lists, or maybe "Requirements". I'll use "Qualifications" as the heading since it's listed in the example. - "Skills": The "Skills & Ability" section could be "Skills", but there's also "Required Knowledge". I'll maybe merge into "Qualifications" or use "Skills" if there's distinct content. Looking at the rules: "Prefer a few substantive sections over many thin ones." I'll likely use "Qualifications" to cover knowledge, skills, education, experience. - "Benefits": Not present in the posting. No mention of benefits, pay, schedule. So I must NOT create a Benefits section, Pay section, or Schedule section. - "Pay" / "Schedule": Not present, so skip entirely. - Let's outline the HTML structure mentally: - No `` or ``. - Start with maybe a `

  ` for "About the role" or just jump into content. The rule: "do NOT repeat the job title as a heading (the page already shows it)". The job title is "Marketing Coordinator". I won't use that as a heading. - I'll use `

  ` headings that match actual content. - Possible headings to use: "About the role", "Responsibilities", "Qualifications". I won't use "Skills" separately if I can fold into Qualifications. I won't use "Benefits", "Pay", "Schedule". - Let's map carefully: - "About the role": The Job Summary paragraph and company intro. But the company intro is quite long. I could put it under "About the role" or maybe separate. The rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I'll use "About the role" for the job summary + company blurb, or maybe just "Job Summary". But the example lists "About the role". I'll use "About the role" and put the summary there. However, the company description (60 years, awards, etc.) is also part of the posting. I'll include it under "About the role" or maybe I should have a separate intro? The rules say "Preserve ALL substantive information; do NOT invent or summarize away detail." I'll put the company description and job summary together under "About the role", or maybe use two headings? But rules prefer "a few substantive sections over many thin ones." I'll combine company intro + job summary under "About the role". - "Responsibilities": Essential Functions list. Will use `

  • ` for each duty. - "Qualifications": Essential Qualifications section. Will include Required Knowledge, Skills & Ability, Education-Certification, Experience Required. I'll structure as a list or multiple lists under the heading. - I should NOT include "Skills" as a separate heading if it's thin, but the content under "Skills & Ability" is substantial. I could fold it into "Qualifications". The rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I have to choose headings from that list or similar. I'll use "Qualifications" to cover all that. - Work Environment and Physical Demands: These are substantive. I could include them under "About the role" or maybe "Work Environment". But the allowed headings don't explicitly list "Work Environment". The rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." means examples, not exhaustive. But it also says "Prefer a few substantive sections over many thin ones." I need to decide if "Work Environment" and "Physical Demands" warrant headings. They are specific sections in the posting. I think I should include them, maybe as `

    Work Environment

    ` and `

    Physical Demands

    `, but the rules restrict headings to the listed examples? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could mean I should only use those headings, or those are the permitted ones. To be safe, I'll map Work Environment and Physical Demands into existing headings or use them if they fit. But the rule also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So I can create headings that match content. I think it's okay to use "Work Environment" and "Physical Demands" as headings since they are real sections, but the prompt's examples list specific ones. I'll check the exact wording: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests these are examples, but the list might be the intended set. To be safe and follow "Prefer a few substantive sections over many thin ones", I'll probably stick to the listed headings where content exists, and fold other content into them. Work Environment and Physical Demands could go under "About the role" or "Qualifications", but that might lose detail. Alternatively, I could use "Work Environment" as an `

    ` since it's substantive. The rule doesn't strictly forbid other headings, it just gives examples. I'll use headings that make sense and are in the spirit of the list. I'll probably use: "About the role", "Responsibilities", "Qualifications". I'll fold Work Environment and Physical Demands into "About the role" or "Qualifications" as prose, or maybe add "Work Environment" if I feel it's necessary. But the rule "Prefer a few substantive sections over many thin ones" suggests I shouldn't create too many sections. I'll aim for 3-4 sections max. - Let's re-read the removal rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I must remove the entire EEO paragraph at the end, the E-Verify mention, the CA data privacy notice, and the "Please contact recruiting..." line. - "Do NOT repeat the job title as a heading (the page already shows it)" - so no `

    Marketing Coordinator

    `. - "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." - No job ID present, fine. - "Preserve ALL substantive information; do NOT invent or summarize away detail." - I need to keep all the detailed lists, descriptions, etc. - "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." - Critical. I must not create Pay/Schedule/Benefits. The posting has no such info, so I skip those sections entirely. - Let's plan the HTML output structure: I'll use these headings (only where content exists): - `

    About the role

    ` - will contain the Job Summary paragraph and the company description? Or maybe separate? The company description is at the top. I'll include it under "About the role" or maybe I should have a brief intro. Actually, the posting starts with company info, then "Job Summary". I'll put the company info + job summary under "About the role". But the job summary is specifically about the role. I'll maybe use two headings: "About the role" for company intro, and then job summary is part of it. Or I could use "About the role" for the summary, and fold company info into a `

    ` at the start? The rules say "Output ONLY the HTML fragment — no