Droga5 Design Director
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must not repeat job title as heading. We need to include sections only when posting has real specific content.
We need to preserve all substantive info, no boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). So we must strip out EEO statements, accommodation request, equal opportunity, etc. Also remove "Requesting an Accommodation", "Equal Employment Opportunity Statement", "Other Employment Statements", etc. Also remove "Visit Droga5.com or @droga5..."? That's about who we are, maybe keep as part of About the role? The "Who we are" is substantive about company. We can put under a heading maybe "About the company" but allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use "About the role" for job summary? Actually "About the role" could contain job summary and who we are? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when appropriate. We can also possibly use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those. So we need to map content to these sections.
We have:
- Who we are (company description) could go under About the role? Might be okay.
- Design @ Droga5 (team description) also maybe About the role.
- Job Summary: could be About the role.
- Job Responsibilities: Responsibilities section.
- Basic Qualifications: Requirements? Or Qualifications? There's both Basic and Preferred Qualifications. Could combine into Requirements and Qualifications? The list includes Requirements and Qualifications separate. Could put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications.
- Skills: maybe we can extract skills from qualifications (e.g., Expert proficiency in Photoshop and InDesign, etc.) Could put under Skills.
- Benefits: we have benefits description.
- Pay: we have compensation ranges per location.
- Schedule: not mentioned; we should not create Schedule section if no info.
We must not include placeholder text like "commensurate with experience". We have actual salary ranges.
We must not include boilerplate like EEO, accommodation request, etc.
We must preserve all substantive info: company description, design team description, job summary, responsibilities, basic qualifications, preferred qualifications, skills (maybe from qualifications), benefits, pay ranges per location.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those. So we need to map content to these sections.
We have:
- Who we are (company description) could go under About the role? Might be okay.
- Design @ Droga5 (team description) also maybe About the role.
- Job Summary: could be About the role.
- Job Responsibilities: Responsibilities section.
- Basic Qualifications: Requirements? Or Qualifications? There's both Basic and Preferred Qualifications. Could combine into Requirements and Qualifications? The list includes Requirements and Qualifications separate. Could put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications.
- Skills: maybe we can extract skills from qualifications (e.g., Expert proficiency in Photoshop and InDesign, etc.) Could put under Skills.
- Benefits: we have benefits description.
- Pay: we have compensation ranges per location.
- Schedule: not mentioned; we should not create Schedule section if no info.
We must not include placeholder text like "commensurate with experience". We have actual salary ranges.
We must not include boilerplate like EEO, accommodation request, etc.
We must preserve all substantive info: company description, design team description, job summary, responsibilities, basic qualifications, preferred qualifications, skills (maybe from qualifications), benefits, pay ranges per location.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
... combine who we are, design @ droga5, job summary.
ThenResponsibilities
- ... each responsibility.
Requirements
- ... basic qualifications.
Qualifications
- ... preferred qualifications.
Skills
- ... skills extracted: Expert proficiency in Photoshop and InDesign, any new and emerging design-specific software, excellent oral/written communication and presentation skills, strong interpersonal skills, ability to multi-task, collaborative, understanding of design process beyond campaign work, expert production experience.
Benefits
Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off.
ThenPay
Compensation varies by location; see ranges below:
- California: $94,400 to $224,600
- Colorado: $94,400 to $194,100
- Connecticut: $94,400 to $194,100
- District of Columbia: $100,500 to $206,700
- Illinois: $87,400 to $194,100
- Maine: $80,400 to $165,300
- Maryland: $94,400 to $194,100
- Massachusetts: $94,400 to $206,700
- Minnesota: $94,400 to $194,100
- New York: $87,400 to $224,600
- New Jersey: $100,500 to $224,600
- Ohio: $87,400 to $179,700
- Virginia: $87,400 to $206,700
- Washington: $100,500 to $206,700
or drop it. This is minor metadata (posting date). Could drop it. Safer to drop. Also "Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience." That's substantive about compensation; we can include. Thus Pay section could have a paragraph describing compensation variability, then list ranges. Now check we didn't include any duplicated lines: we have not repeated. Now ensure we didn't include any "EEO" etc. We removed those sections. Now output HTML. Let's construct:
About the role
Droga5, part of Accenture Song, is a creative agency with offices in New York, London, Dublin, Tokyo and São Paulo. From integrated communications and experience innovation to business design, Droga5 exists to build and sustain the most influential brands of the 21st century through creativity. Droga5 was founded in 2006 and has been recognized as Agency of the Year more than 25 times and was named both Ad Age and Adweek’s Agency of the Decade (2010–2019). Design @ Droga5: We are a team of multidisciplinary designers curious about how brands influence culture and affect the human experience by way of concept-driven aesthetics and systematic design thinking. We avoid trends and seek meaning to create work that is award-winning and career-defining through integrated experiences, interactions, and environments. The Design Director works autonomously, leads a team, and brings the vision of multiple projects to life with little or no oversight. The Design Director works closely with the co-leaders across departments and with clients, thinking on a higher level about how best to drive the business. Internally, the Design Director is a key contributor to the department and agency culture, and a mentor to shape more junior designers’ careers. Their work is consistent in excellence and originality.
Responsibilities
- Oversee multiple pieces of business at once, effectively managing time and delegating work