Product Visual Design Lead — Immediate Need

We need to output HTML fragment with sections: About the role? Actually we have sections: Company Description, Job Description (Scope, Impact, What Success Looks Like), Qualifications, Additional information (Compensation & Benefits, Workplace, Work Authorization, Our Commitment). We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We need to map content to these headings appropriately. We have: Company Description (maybe "About the role"? Actually company description is about company, not role. Could be "About the role" but we have no explicit "About the role". Could use "Company Description" but not in allowed headings list. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should use those headings when appropriate. Probably we should use those exact headings if we have content. Let's see what we have: - About the role: could be a brief summary of the role. We have Job Description: Scope, Impact, What Success Looks Like. Could combine into About the role? Might be better to use "About the role" for a brief paragraph summarizing the role. Then "Responsibilities" for Scope (lead visual design work...). "Requirements" or "Qualifications" for qualifications. "Skills" maybe for Figma skills etc. "Benefits" for compensation & benefits. "Pay" for salary range. "Schedule" maybe for workplace expectations (in-person collaboration, days per week). We need to avoid filler. We must preserve all substantive information, not invent or summarize away detail. So we need to include details exactly as given, but we can format them into lists. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "I'm interested Share this job" etc. Those are likely boilerplate/application instructions; we should remove them. We need to output only HTML fragment, no /, no markdown fences. Let's extract substantive content: Company Description: "Ready Set Rocket (A Sia Company), partners with ambitious brands to solve complex business challenges through integrated marketing, digital experience, customer strategy, creative, media, data and technology. We are building on significant momentum and investing in the next stage of our growth. Our clients look to us for strategic partnership that connects business objectives with measurable outcomes across the full customer journey." Job Description: includes Scope, Impact, What Success Looks Like. Scope: "Lead the visual design work in Figma: determine how complex product information should be organized and presented, make the design decisions, resolve challenges as they arise, and deliver polished final work. You’ll set the pace and drive the project forward independently, with minimal oversight or rounds of review." Impact: "Make detailed product information clear and easy to use without sacrificing visual quality. Your decisions about hierarchy, typography, layout, and consistency will directly shape the finished experience." What Success Looks Like: "You take ownership of an assignment, identify what needs to happen next, and deliver accurate, high-quality work without relying on frequent direction or review. Your portfolio demonstrates strong visual craft in digital products or interfaces, ideally including tables, dashboards, comparison views, or other information-rich work." Qualifications: list bullet points: - Advanced Figma skills and strong visual design craft. - Proven success leading digital product or interface design work from initial direction through final delivery. - Experience working independently, setting direction for your own work, and driving projects forward with minimal oversight. - Exceptional attention to detail, especially when designing complex, information-rich layouts. - A portfolio that demonstrates your hands-on design work, ideally including tables, dashboards, comparison views, or similar product experiences. Additional information: Compensation & Benefits: - Compensation Base Salary: $125,000-135,00. (typo: missing .00? but keep as is) - Actual compensation within this range will be determined based on experience, qualifications, geographic location, and other job-related factors permitted by applicable law. - Annual Performance Bonus - Benefits: Medical, dental, and vision; company-paid life and AD&D; voluntary supplemental insurance and EAP; 401(k) with company match and immediate vesting; HSA and FSA options; College savings and student loan repayment programs; Paid parental leave; generous PTO, nine company holidays, and one floating holiday; Cell phone stipend; well-being and professional development programs - Benefits are subject to applicable plan terms and eligibility requirements. Workplace: - Sia values in-person collaboration. When serving clients, consultants may be required to work onsite at a client location based on engagement needs. - Between client engagements, consultants are expected to work from a Sia office or approved coworking location at least three days per week. - Candidates should reside within a reasonable commuting distance of a Sia office or approved coworking location. - Sia maintains offices and coworking arrangements across multiple U.S. markets, including New York City, Charlotte, Greater Seattle, San Francisco Greater Bay Area, Los Angeles, Houston, Atlanta, Baltimore, Chicago, Washington D.C. Work Authorization: - Applicants must be legally authorized to work in the United States at the time of application and throughout their employment. - This position is not eligible for employment visa sponsorship now or in the future. Our Commitment: - At Sia, we believe in fostering a diverse, equitable, and inclusive culture where our employees and partners are valued and thrive in a sense of belonging. We need to decide headings. Possible sections: - About the role: maybe a brief paragraph summarizing role: could combine company description? But company description is about company, not role. Could put company description under "About the role"? Might be okay but not ideal. However we have no explicit "About the role" content. Could we omit About the role? The instruction: "Prefer a few substantive sections over many thin ones." So we can skip sections lacking real specific content. We have company description; we could put that under "About the role" as it's about the company/context. Might be acceptable. Alternatively we could have sections: Responsibilities, Qualifications, Benefits, Pay, Schedule. Also maybe "Company Overview" not in list but we could still use

with custom heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings, but maybe we can also use other headings if needed? It says "use

for section headings (e.g. ...)" meaning those are examples of headings we should use; we should not invent other headings. So we should stick to those. Thus we need to map content to those headings. Let's see what we have for each: - About the role: could be a short summary: "Immediate need for a Product Visual Design Lead to lead visual design work in Figma for a leading technology innovator, focusing on product-facing, data-heavy design." That's derived from job description. We can include that. - Responsibilities: Scope and Impact maybe combined. - Requirements: maybe Qualifications? But we have Qualifications heading separate. Could use Requirements for mandatory items? But we have Qualifications; we can use Qualifications heading. - Skills: maybe Figma skills etc. Could be under Skills. - Benefits: Benefits. - Pay: Salary range and bonus. - Schedule: Workplace expectations (in-person, days per week). We also have Work Authorization and Our Commitment; those could be placed under maybe "Requirements" or "Qualifications"? But they are not exactly qualifications. Could we omit them? They are substantive info; we need to preserve ALL substantive information. So we need to include them somewhere. Perhaps we can add a section "Requirements" for work authorization and commitment? Or we could add a section "Additional Information" but not in allowed headings. However we could incorporate them under "Qualifications" as extra bullet points? Might be okay but could dilute meaning. Better: Use "Requirements" for work authorization and commitment (since they are requirements). Use "Qualifications" for skills/experience. Use "Skills" for Figma etc. But we have overlapping. Let's think: The posting has Qualifications list (skills/experience). Also there is "Additional information" containing compensation, benefits, workplace, work authorization, commitment. We could structure:

About the role

Immediate need for a Product Visual Design Lead to lead visual design work in Figma for a leading technology innovator, focusing on product-facing, data-heavy design that calls for exceptional visual craft, clarity, and precision.

Responsibilities

• Lead the visual design work in Figma: determine how complex product information should be organized and presented, make the design decisions, resolve challenges as they arise, and deliver polished final work.
• Set the pace and drive the project forward independently, with minimal oversight or rounds of review.
• Make detailed product information clear and easy to use without sacrificing visual quality.
• Decisions about hierarchy, typography, layout, and consistency directly shape the finished experience.
• Take ownership of an assignment, identify what needs to happen next, and deliver accurate, high-quality work without relying on frequent direction or review.

Qualifications

• Proven success leading digital product or interface design work from initial direction through final delivery.
• Experience working independently, setting direction for your own work, and driving projects forward with minimal oversight.
• A portfolio that demonstrates hands-on design work, ideally including tables, dashboards, comparison views, or similar product experiences.

Skills

• Advanced Figma skills and strong visual design craft.
• Exceptional attention to detail, especially when designing complex, information-rich layouts.

Benefits

• Medical, dental, and vision; company-paid life and AD&D; voluntary supplemental insurance and EAP.
• 401(k) with company match and immediate vesting; HSA and FSA options.
• College savings and student loan repayment programs.
• Paid parental leave; generous PTO, nine company holidays, and one floating holiday.
• Cell phone stipend; well-being and professional development programs.

Pay

Base Salary: $125,000-135,00. Actual compensation within this range will be determined based on experience, qualifications, geographic location, and other job-related factors permitted by applicable law. Annual Performance Bonus.

Schedule

Sia values in-person collaboration. When serving clients, consultants may be required to work onsite at a client location based on engagement needs. Between client engagements, consultants are expected to work from a Sia office or approved coworking location at least three days per week. Candidates should reside within a reasonable commuting distance of a Sia office or approved coworking location. Sia maintains offices and coworking arrangements across multiple U.S. markets, including New York City, Charlotte, Greater Seattle, San Francisco Greater Bay Area, Los Angeles, Houston, Atlanta, Baltimore, Chicago, Washington D.C.

We still need to include Work Authorization and Our Commitment. Where to put? Could add under "Requirements" heading (we haven't used Requirements). Let's add a

Requirements

with those items. Thus:

Requirements

• Applicants must be legally authorized to work in the United States at the time of application and throughout their employment.
• This position