Account Coordinator, Technology Public Relations

We need to output HTML fragment with sections: About Us? The instruction: use

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

• for any list of duties/requirements/benefits, and

  for prose. 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. 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. We need to parse the posting. The posting includes: - About Us paragraph (multiple sentences). This is about the company. Could be considered "About Us" but not in list of allowed headings? The allowed headings list includes "About the role" etc. "About Us" is not listed. However we can still use

  for section headings; they gave examples but not exclusive? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical, but we can use other headings if needed? Probably we should stick to those headings; but we have content about company overview. Could we put that under "About the role"? Not exactly. The "Overview" section after About Us describes the role. So we could have: - Overview (maybe treat as About the role). The instruction says "About the role" heading is appropriate. So we can put the overview description under

  About the role

  . - Responsibilities: list bullet points. - Qualifications: bullet points. - Benefits: bullet points (they list many benefits). Also they mention Hybrid work environment etc. That's benefits. - Pay: they have compensation range: $45k-$55k. Also mention additional perks. So we should include Pay section. - Schedule: they mention Hybrid work environment with home and office schedule (2+ days in office per week) and work from anywhere weeks. That's schedule info. Could be under Schedule. We need to avoid filler placeholder. All content is substantive. We must remove boilerplate: Equal Opportunities paragraph, etc. Also remove "Equal Opportunities" heading? It's boilerplate; we should drop it. Also remove "Compensation" heading? Actually we need Pay section; we can incorporate compensation details there. We must not repeat job title as heading. Not needed. We must not include application instructions. We must not include duplicated lines. We need to preserve all substantive information: About Us description, Overview, Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to format as HTML fragment: use

  for each section heading, then content: either

  for prose or

  • for lists. We need to decide which content is prose vs list. About Us: could be a

    containing the paragraph(s). There's multiple sentences; we can combine into one

    maybe with line breaks? We'll just put as one

    . Overview: also prose. Responsibilities: list bullet points; we can make

    • each. Qualifications: list bullet points. Benefits: list bullet points. Pay: maybe a

      with compensation range and note about additional perks. Schedule: maybe a

      describing hybrid work. We need to ensure we don't create sections with filler. All have content. Now extract specifics. About Us text: "We imagine the new. Inspire the next. And use the power of our creativity to help build up those around us. At Allison, we provide a limitless environment where you can build, create, and grow. Our openly collaborative and highly supportive culture is free from bureaucracy and red tape. With over 1,000 innovators from diverse backgrounds, we break new ground for world-class clients across 50 global markets and dozens of industries. We believe in creating a space where everyone can freely express their opinions, share their ideas and dreams for the future, and be themselves. We foster an inclusive culture that attracts builders from all backgrounds who can envision new solutions and create outcomes that move our clients' businesses forward, while helping everyone on the team learn and grow together. Our shared ideal of the builder's mindset is limitless and available to everyone, and we push the boundaries to create new and innovative solutions for our clients and ourselves. We create lasting impact and relationships, and our culture fosters meaningful connections and friendships that last beyond the workplace. If you're ready to join a team that pushes you to be your best, supports you every step of the way, and celebrates your successes, welcome to the Allison family." We'll keep that as is. Overview text: "We’re loo king for an Account Coordinator to join Allison’s fast-moving, ideas-driven practice . This is an entry level position where you’ll have the opportunity to learn more about the PR industry and best practices in client service, media relations and content development. You will be responsible for developing a curated media lists of reporters that cover client and industry-specific news, issues and announcements, while also conducting regular news monitoring to share trending stories the account team can leverage for clients. You will also develop influencer and media relationships, pitch media to secure press opportunities, track coverage, and support overall account management and administration with weekly meeting agendas, action items and reports." Note there is a typo "loo king". We should preserve as is? Probably keep exactly but maybe fix? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't say to correct typos. We'll keep as is. Responsibilities bullet points (from the text): - Participate in team and client calls and provide thorough notes and action items to move deliverables forward every week. - Develop the first draft of written content (e.g., press release, briefing books, media pitches, bylines). - Monitor and flag client and industry media coverage for the account team. - Conduct entry-level media relations with instruction from AE/SAE; pitching news announcements and conducting follow up via phone and email. - Research speaking opportunities, events, and awards. - Produce monthly or weekly reports outlining key account activities and initiatives. - Learn and become proficient in media tracking, monitoring and data analytics tools such as MuckRack, Critical Mention, Cision and Meltwater. - Conduct new business research to support pitches and presentations. - Promote and uphold Allison’s core values; participate in agency-wide training and professional development program Check if any duplicated lines: none. Qualifications bullet points: - Preferred experience as an intern/apprentice in public relations, marketing or a related field. - Technology Industry interest strongly preferred. - Self-motivated, eager to learn and enthusiastic about the work. - Eye for detail and organization. - Comfortable and knowledgeable working in Microsoft Outlook, Word, PowerPoint and Excel alongside Zoom and Microsoft Teams. - Ability to take direction, ask clarifying questions and follow through on required deadlines. Benefits bullet points (from Benefits section): - Hybrid work environment with home and office schedule (2+ days in office per week) and work from anywhere weeks - Comprehensive health benefits (healthcare, vision, dental, pet, home, and auto insurance) - Generous time off policies (unlimited paid time off, wellness days, national holidays, summer Fridays) - Four-week sabbatical every five years of employment - Exceptional parental leave benefits - Global mentorship and networking programs - Monthly cell phone reimbursement - 401k savings and employee stock purchase plan - Volunteer hours (20 hours annually) for designated non-profit partner and personal choice - Globally driven DEI initiatives (Employee Advocacy Groups, DEI committee) - Career growth opportunities, such as Allison University (multi-day customized trainings for each level) Note: Hybrid work environment also appears in schedule; but we can keep it under Benefits as it's a benefit. However schedule section may also need to mention hybrid schedule. The instruction says prefer few substantive sections over many thin ones. Could combine hybrid schedule under Benefits or Schedule. But we have both Benefits and Schedule sections; we need to avoid duplication. The Benefits list includes hybrid work environment; the Schedule could mention home/office schedule and work from anywhere weeks. To avoid duplication, we could keep hybrid work under Benefits and not repeat in Schedule, or we could keep Schedule separate and remove hybrid from Benefits. Which is better? The Benefits section originally includes hybrid work environment as a benefit; it's indeed a benefit. The Schedule section would be about work schedule. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state hybrid work environment under Benefits. It also mentions "Hybrid work environment with home and office schedule (2+ days in office per week) and work from anywhere weeks". That's both benefit and schedule. We could keep Benefits section with that item, and Schedule section could be omitted or could mention something else? There's no other schedule info besides that. If we create Schedule section, we would need to include that same info, causing duplication. The instruction says prefer a few substantive sections over many thin ones. So maybe we should not create a separate Schedule section; instead include schedule info within Benefits. However the instruction also says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule info (home and office schedule, work from anywhere weeks) as part of Benefits. So we could still have a Benefits section that includes that. No need for separate Schedule. Thus we will have sections: About the role (overview), Responsibilities, Qualifications, Benefits, Pay. We also have About Us company description; maybe we could put that under "About the company"? Not in allowed headings but we could still use

      About Us

      . The instruction didn't forbid other headings; just gave examples. It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings. However to be safe, we could incorporate About Us into a

      before any headings, or we could treat it as "About the role"? Not appropriate. Better to have a heading "About Us". Since they didn't forbid, we can use it. But the instruction says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are typical but not exclusive. I'd include About Us as a heading. Thus final HTML:

      About Us

      ...

      About the role

      ...

      Responsibilities

      • ...
      ...

      Qualifications

      • ...
      ...

      Benefits

      • ...
      ...

      Pay

      ...

      We must not include any extra text like comments. Now ensure we preserve all substantive information from Benefits list, including hybrid work environment etc. Pay section: The posting says: "Compensation In order to comply with equal pay and salary transparency laws in various locations, we believe the target range of base compensation in all locations within the United States for this role is $45k-$55k. Actual compensation is influenced by a wide array of factors including