Senior Associate, Creative Services

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Physical Requirements & Working Conditions"? That's not in list of allowed headings; but we could maybe treat as part of Responsibilities? Actually it's separate but not in allowed headings list; we should not create a heading for it unless we map to allowed headings. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only use those headings. If content doesn't fit those, we can embed in

without heading? Probably we should include relevant info under appropriate headings. For Physical Requirements & Working Conditions maybe could go under Responsibilities? Or maybe we can omit because not required heading; but we must preserve ALL substantive information. So we need to include that info somewhere. Could put under a

after Responsibilities heading without a heading? Or we could create a heading "Working Conditions" but not allowed. Better to embed within Responsibilities or maybe a generic

after Responsibilities. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. Likely they expect only those headings. We can still include other info as paragraphs without heading. We need to include Pay section because compensation is given: $73,000 - $98,000. So we need a Pay heading

Pay

with

containing the range and note. Schedule: The posting mentions "Hours of work may vary, including evenings, weekends, and holidays, especially during peak event periods." That's schedule info. So we can include Schedule heading. Benefits: The posting includes "What We Offer" bullet list: chance to shape brand, collaborative studio culture, high-visibility work, real growth. Those are benefits. So Benefits heading. About the role: The "Role Purpose" paragraph can be About the role. Responsibilities: Key Responsibilities bullet list. Requirements: Could be Required Competencies bullet list (or maybe Requirements). Qualifications: maybe same as Required Competencies? But we need to avoid duplication. We could treat Required Competencies as Requirements, and Valued Experience as Qualifications? Or Skills: maybe expertise in tools. Let's map: - About the role: Role Purpose paragraph. - Responsibilities: Key Responsibilities bullet list. - Requirements: Required Competencies bullet list (4+ years experience, expertise in tools, advanced understanding, portfolio, proven ability). - Qualifications: maybe Valued Experience bullet list (passion for sport, experience contributing to team culture, flexibility, collaborative approach). Or we could treat Valued Experience as Qualifications. - Skills: maybe we could list specific skills like Figma, Adobe CC, presentation tools, typography, layout, visual storytelling, etc. But that overlaps with Requirements. Could combine. We need to avoid thin sections. Perhaps we combine Requirements and Qualifications into one section? But we need headings only when real specific content. We could have Requirements (including both required and valued) and Skills separate? Let's think. We have: - Required Competencies (specific bullet list) - Valued Experience (bullet list) - Expertise in tools etc (part of Required Competencies) - Physical Requirements & Working Conditions (paragraph) - Compensation (Pay) - Hours (Schedule) - What We Offer (Benefits) - Role Purpose (About the role) - Key Responsibilities (Responsibilities) Thus we can map:

About the role

Role Purpose paragraph.

Responsibilities

• ...

Requirements

• Required Competencies bullets

Qualifications

• Valued Experience bullets

Skills

maybe we could list specific skills: Figma, Adobe Creative Cloud, presentation tools, typography, layout systems, visual storytelling, imagery, building cohesive scalable brand identity. But those are already in Requirements. Could still list them but might be duplication. However we need to preserve all substantive info; duplication is okay as long as we don't invent. But we should avoid repeating same content verbatim? Not prohibited. But better to avoid thin sections. Skills could be a short list of tools and abilities. Alternatively we could omit Skills section and put those details under Requirements. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we skip Skills. Benefits:

Benefits

• What We Offer bullets

Pay:

Pay

The annual base salary range for this position is $73,000 - $98,000. The pay scale provided is the range that LA28 reasonably expects to pay as starting base compensation for this role. All LA28 compensation remains subject to final determination based on individual candidate qualifications, experience, or other reasonable criteria consistent with LA28's operational business needs and applicable law.

Schedule:

Schedule

Hours of work may vary, including evenings, weekends, and holidays, especially during peak event periods.

We also need to include Physical Requirements & Working Conditions and maybe Accommodation, Equal Opportunity etc. Those are boilerplate? Accommodation and Equal Opportunity are legal/EEO boilerplate; we should remove them per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we drop Accommodation, Equal Opportunity, etc. Physical Requirements & Working Conditions is not legal boilerplate; it's substantive. We need to preserve it. Where to put? Could be under Responsibilities or a separate section like "Working Conditions" but not allowed heading. Could add a

after Responsibilities or after Schedule. Let's add a

after Schedule maybe under a heading? Could add a

Working Conditions

but not in allowed list. Might be okay but risk. Better to embed within Responsibilities as an additional bullet? But it's not a responsibility. Could add a

after Responsibilities heading: "Physical Requirements & Working Conditions: Available to work onsite in our Downtown Los Angeles-based office. The majority of work will be conducted in an office setting, requiring extended periods of time using computers, phones, and other office equipment. The LA28 office is an open floorplan working environment; employees must be able to work efficiently in an open cubicle environment. Hours of work may vary, including evenings, weekends, and holidays, especially during peak event periods. Perform other duties as required; the role will evolve over time and may include operational responsibilities during the Olympic and Paralympic Games." But we already have Schedule heading covering hours variation; we could combine. However Physical Requirements includes onsite requirement, open floorplan, etc. We'll keep that as a

after Responsibilities maybe under a heading "Working Conditions"? But to avoid extra heading, we can just put a

after Responsibilities without heading. That's okay. We must not include duplicated lines. Ensure we don't repeat the same bullet. Let's extract bullet points. Key Responsibilities: - Lead creative service requests from intake through final execution across multiple functional areas, managing competing priorities. - Translate stakeholder needs into strategic, visually compelling creative that advances major organizational initiatives and campaigns. - Develop presentations, campaign assets, environmental graphics, event materials, and branded collateral to a consistently high standard. - Establish scalable, reusable design systems while maintaining quality control and production readiness across concurrent projects. - Serve as a day-to-day brand steward and mentor junior contributors, shaping the team's creative culture. Required Competencies: - 4+ years of agency, in-house, sports, entertainment, experiential, or brand design experience delivering polished, on-brand work. - Expertise in Figma, Adobe Creative Cloud, and presentation tools, applied fluently across the full design and production process. - Advanced understanding of typography, layout systems, visual storytelling, imagery, and building cohesive, scalable brand identity systems. - A strong portfolio demonstrating traditional layout design, conceptual design thinking, and executional excellence is required with your application. - Proven ability to independently lead multiple projects and influence outcomes, backed by excellent communication, collaboration, and organizational skills. Valued Experience: - Passion for sport and the Olympic and Paralympic movements. - Experience contributing to a team culture of creativity and co-creation. - Flexibility and adaptability when priorities and timelines shift. - A collaborative approach to cross-vertical ideation and internal feedback. What We Offer: - The chance to shape a bold new brand for the Los Angeles 2028 Games. - A collaborative, co-creative studio culture grounded in inclusion and craft. - High-visibility, high-impact creative work seen by a global audience. - Real growth alongside a diverse, world-class creative team. Role Purpose paragraph: "As Senior Associate, Creative Services, you will bring the LA28 brand to life across everything people see, touch, and experience. Working from intake through final execution, you will translate stakeholder needs into strategic, visually compelling design — presentations, campaign assets, environmental graphics, and branded collateral. In the years leading up to the Games, you will help establish scalable design systems that keep a fast-growing brand consistent and bold. You will act as a day-to-day brand steward, elevating storytelling through typography, layout, and visual hierarchy while learning and growing alongside a world-class creative team." Physical Requirements & Working Conditions paragraph: "Available to work onsite in our Downtown Los Angeles-based office. The majority of work will be conducted in an office setting, requiring extended periods of time using computers, phones, and other office equipment. The LA28 office is an open floorplan working environment; employees must be able to work efficiently in an open cubicle environment. Hours of work may vary, including evenings, weekends, and holidays, especially during peak event periods. Perform other duties as required; the role will evolve over time and may include operational responsibilities during the Olympic and Paralympic Games." Compensation paragraph: "The annual base salary range for this position is $73,000 - $98,000.The pay scale provided is the range that LA28 reasonably expects to pay as starting base compensation for this role. All LA28 compensation remains subject to final determination based on individual candidate qualifications, experience, or other reasonable criteria consistent with LA28's operational business needs and applicable law." Note there is no space after period before "The". We'll keep as is but can add space for readability; but must preserve info, not change meaning. Adding a space is okay. Schedule: we already have hours variation in Physical Requirements; but we can still have Schedule heading referencing that. To avoid duplication, we could put Schedule heading with same sentence about hours. But that duplicates info from Physical Requirements. Might be considered duplication. Better to not have separate Schedule if we already covered hours in Physical Requirements. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state hours variation, so we could have Schedule. But we also have Physical Requirements containing that sentence. If we include both, we duplicate. We could keep Schedule and remove the hours sentence from Physical Requirements to avoid duplication. But we must preserve ALL substantive information; removing the hours sentence would lose that info. However we could keep the hours sentence in Schedule and keep other physical requirements (onsite, open floorplan) in Physical Requirements paragraph without hours. That way we preserve all info without duplication. Thus: Physical Requirements & Working Conditions paragraph (without hours):