Visual Communications Coordinator

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. Let's parse the posting. Content includes: - Intro about HDR culture (maybe "About the role"? Actually "About the role" could be the description of role responsibilities? The posting includes "In the role of Visual Communications Coordinator, we’ll count on you to:" then a list of duties. That's responsibilities. - There's a "Preferred Qualifications" list. - There's a "Required Qualifications" list. - There's "What We Believe" and "Our Commitment" maybe about culture; could be "About the role"? Not exactly. Could be "About the role" maybe summarizing role? But we have responsibilities already. - There's benefits: "We provide a comprehensive benefits package that promotes employee ownership, employee health, performance, and success, which includes medical, dental, vision, short and long-term disability, life insurance, an employee assistance program, paid time away, parental leave, paid holidays, a retirement savings plan with employer match, employee referral bonus and tuition reimbursement." - Pay: "The expected compensation range for this position depends upon skills, experience, education and geographical location. (Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits.) Chicago, IL: $30.58 - $43.69 per hour Los Angeles, CA: $31.97 - $45.68 per hour New York, NY: $34.75 - $49.65 per hour San Francisco, CA: $36.14 - $51.64 per hour" - Schedule: "Schedule:Full-time Employee Status:Regular" - Also location info: Primary Location: United States-Illinois-Chicago etc. Could be part of "About the role"? Not needed. - There's "Industry:Marketing/Communications" maybe not needed. - There's "BusinessClass:Marketing and Admin" maybe not needed. - There's "Job Posting:Sep 15, 2026" maybe drop. - There's EEO boilerplate: remove. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. - About the role: maybe a brief paragraph summarizing the role: "At HDR, our employee-owners are fully engaged..." but that's generic company culture. Could be considered "About the role"? Might be better to put that as "About the role". However the instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have About the role heading with a paragraph describing the role and its impact. We have content: "At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story:' https://www.hdrinc.com/our-story' Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world." That's generic but could be About the role. Responsibilities: list after "In the role of Visual Communications Coordinator, we’ll count on you to:" then bullet list (actually sentences separated by line breaks). We'll convert each sentence to

. Requirements: maybe combine Preferred and Required? The instruction: Use sections Requirements and Qualifications separately? Possibly Requirements = Required Qualifications, Qualifications = Preferred Qualifications? Or Requirements could be both? We'll interpret: Requirements = Required Qualifications (must-have). Qualifications = Preferred Qualifications (nice-to-have). Skills: maybe we can extract skills from both lists? But we might not need Skills section if content overlaps. However we need to include a section only when posting has real specific content. We have skills mentioned: "Strong knowledge in Adobe Creative Suite (Photoshop, Illustrator, and InDesign)", "Microsoft Office suite", "Ability to design a wide variety of styles", "Eye for design details, such as typography, alignment, hierarchy, etc", "Strong portfolio showing design experience", "Strong skills in customer service, communication and negotiation skills, flexibility, time management, project management, detail oriented, leadership, and teamwork", "Understanding of branding/brand development, communications, and research". Also from Preferred: "Experience translating complex technical or design information into clear, audience-friendly visual communications", "Familiarity with architectural drawings, diagrams, sections, renderings, and visualization workflows", "Experience with 3D modeling, visualization, or rendering software such as Rhino, Blender, Unreal Engine, or comparable platforms", "Experience with Premiere, After Effects, Dreamweaver, and CSS", "Experience with offset printing, digital printing, and color correction", "Research-oriented mindset with strong visual storytelling and creative problem-solving abilities". Those are skills. We could put skills in a Skills section, but we also have Requirements and Qualifications sections. Might be redundant but allowed. However instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one? But they ask to use those headings if content exists. We have both Required and Preferred, so we can have Requirements (Required Qualifications) and Qualifications (Preferred Qualifications). Skills could be derived but maybe we can omit Skills to avoid thin sections. However we have many skill details; could be placed under Requirements and Qualifications as part of those lists. But the instruction says use

• for any list of duties/requirements/benefits. So we can put Required Qualifications as a list under Requirements heading, Preferred Qualifications as list under Qualifications heading. Skills could be integrated into those lists; we don't need separate Skills section. Benefits: we have benefits list. Pay: we have pay ranges. Schedule: we have schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include empty sections. Now craft HTML. We need to use

  for each heading. Inside each section, use

  for prose,

  • for lists. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting. Let's extract each piece. About the role paragraph: The intro paragraph(s) before responsibilities. Let's combine: "At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story: https://www.hdrinc.com/our-story Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world." We should keep the URL as plain text (maybe not as link? The instruction didn't forbid links but we can keep as plain text). We'll keep as is. Responsibilities: list each duty after "In the role of Visual Communications Coordinator, we’ll count on you to:" The list: - Plan, manage, and deliver visual communication projects from concept through completion - Translate architectural, planning, sustainability, research, and design concepts into compelling graphics, diagrams, infographics, layouts, and visual stories - Conceptualize and design high-quality corporate and marketing materials, including publications, brochures, media kits, presentations, social media assets, and web graphics - Develop and refine architectural drawings, diagrams, renderings, sections, and visualizations to communicate design ideas and project stories clearly - Collaborate with architects, designers, researchers, planners, marketers, and other subject matter experts to simplify complex information for a variety of audiences - Work with other designers on multicomponent and multidisciplinary projects and partner with internal clients to shape deliverables - Apply strong graphic design principles, including typography, composition, hierarchy, alignment, and visual consistency - Assist in the development and presentation of materials and serve as a contributor or leader for meetings and task force assignments - Produce accessible visual content that communicates technical, sustainability, and research-driven concepts - Research industry trends, design publications, emerging visualization tools, production techniques, and processes appropriate to each project - Maintain organized project files and manage multiple assignments while meeting deadlines and quality expectations - Ensure quality control through review and approval of proofs, press checks, and review or testing of materials before deployment - Demonstrate effective leadership with clients and provide guidance or mentorship when appropriate - Perform other duties as needed We'll put each as
  • . Requirements (Required Qualifications): list: - A minimum of 2 years relevant industry experience - Strong knowledge in Adobe Creative Suite (Photoshop, Illustrator, and InDesign) - Microsoft Office suite - Ability to design a wide variety of styles - Eye for design details, such as typography, alignment, hierarchy, etc - Strong portfolio showing design experience - Strong skills in customer service, communication and negotiation skills, flexibility, time management, project management, detail oriented, leadership, and teamwork - Understanding of branding/brand development, communications, and research We'll keep as list. Qualifications (Preferred Qualifications): list: - Bachelor’s degree in Architecture, Graphic Design, Web Design, Visual Communications, Data Visualization, Fine Arts, or a related field, or equivalent experience - Minimum 3 years of professional design experience - Minimum 3 years of experience within the architecture, engineering, and construction industry - Experience translating complex technical or design information into clear, audience-friendly visual communications - Familiarity with architectural drawings, diagrams, sections, renderings, and visualization workflows - Experience with 3D modeling, visualization, or rendering software such as Rhino, Blender, Unreal Engine, or comparable platforms - Experience with Premiere, After Effects, Dreamweaver, and CSS - Experience with offset printing, digital printing, and color correction - Research-oriented mindset with strong visual storytelling and creative problem-solving abilities We'll keep as list. Benefits: list: - medical - dental - vision - short and long-term disability - life insurance - an employee assistance program - paid time away - parental leave - paid holidays - a retirement savings plan with employer match - employee referral bonus - tuition reimbursement We'll keep as list. Pay: we have ranges per location. We need to present as prose maybe. Could be a

    with the ranges. We'll include all four locations. Pay paragraph: "The expected compensation range for this position depends upon skills, experience, education and geographical location. (Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits.) Chicago, IL: $30.58 - $43.69 per hour; Los Angeles, CA: $31.97 - $45.68 per hour; New York, NY: $34.75 - $49.65 per hour; San Francisco, CA: $36.14 - $51.64 per hour." We'll keep as

    . Schedule: we have "Schedule:Full-time Employee Status:Regular". Could be a

    "Schedule: Full-time; Employee Status: Regular." We'll output as

    . Now ensure we don't include any boilerplate like EEO, etc. Now produce HTML fragment. We must not include or . Just the sections. Let's craft:

    About the role

    At HDR, our employee-