Associate Director, Visual Design - US GTM
Kyndryl · Dallas, TX · 1 mo ago
On-siteDesign$144k–$273k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "Who We Are", "The Role", "What You Will Do", "Who You Are", "Preferred Skills And Experience", "Pay And Benefits", "Being You", "What You Can Expect". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map sections accordingly. We should not repeat job title. We need to include sections only when posting has real specific content.
We need to extract content for each heading.
We have:
- About the company? "Who We Are At Kyndryl, we design..." That's about the company. Could be "About the role"? Actually "About the role" is typical heading for role description. But we have "The Role" heading. Could map to "About the role". We'll use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map sections accordingly. We should not repeat job title. We need to include sections only when posting has real specific content.
We need to extract content for each heading.
We have:
- About the company? "Who We Are At Kyndryl, we design..." That's about the company. Could be "About the role"? Actually "About the role" is typical heading for role description. But we have "The Role" heading. Could map to "About the role". We'll use About the role
and put the paragraph(s) from "The Role" section.
- Responsibilities: "What You Will Do" list of duties. Use Responsibilities
with - items.
- Requirements: "Who You Are Required skills and experience". That's required skills. Use
Requirements
with list.
- Qualifications? Could be "Preferred Skills And Experience". Use Preferred Skills
maybe "Qualifications". But instruction list includes Qualifications as possible heading. We'll use Qualifications
for preferred skills.
- Skills: maybe we can combine? But we already have Requirements and Qualifications. Could also have Skills section but not needed.
- Benefits: "Pay And Benefits" includes pay range and benefits description. We need separate Pay and Benefits sections only if posting actually states them. It does state pay range and benefits. So we need Pay
with the compensation range details. And Benefits
with benefits description.
- Schedule: Not mentioned; we should not create Schedule section.
- Also there is "Being You" (diversity inclusion) and "What You Can Expect" (learning programs, volunteering). Could be considered as "About the company" or "Culture". Could map to "About the role"? Not exactly. Could create a section "Company Culture" but not in allowed list. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says "e.g." meaning those are examples, not exclusive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings. If content doesn't fit, maybe we omit or combine into existing sections.
We have "Who We Are" (company description) could go under About the role? Not ideal but maybe we can put under About the role as introductory paragraph.
"Being You" and "What You Can Expect" could be part of Benefits? Not really. Could be omitted? But we must preserve ALL substantive information; cannot invent or summarize away detail. So we need to include that info somewhere. If we cannot create a heading not in list, maybe we can incorporate into existing sections like Benefits or Qualifications? But that would misrepresent. However instruction: "Prefer a few substantive sections over many thin ones." It doesn't forbid other headings, but says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; we could also use other headings if needed? The examples are just examples. Safer to stick to those headings but we can include multiple paragraphs under each.
We could create sections: About the role (includes Who We Are + The Role), Responsibilities (What You Will Do), Requirements (Who You Are Required skills), Qualifications (Preferred Skills And Experience), Pay (Pay And Benefits compensation), Benefits (Pay And Benefits benefits + Being You + What You Can Expect maybe). But Benefits should be about benefits only; but we can include other culture info there? Might be stretching.
Alternatively we could create sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. And put culture info under Benefits? Not ideal.
Maybe we can create a section "Skills" for both required and preferred? But we already have Requirements and Qualifications.
Given the instruction to prefer few substantive sections, we could combine Required and Preferred into Requirements? But they said separate.
Let's think: The posting includes:
- Who We Are (company overview)
- The Role (role description)
- What You Will Do (responsibilities)
- Who You Are (required skills)
- Preferred Skills And Experience
- Pay And Benefits
- Being You (diversity inclusion)
- What You Can Expect (learning, volunteering, etc.)
We could map:
About the role: combine Who We Are + The Role (company + role description)
Responsibilities: What You Will Do
Requirements: Who You Are (required skills)
Qualifications: Preferred Skills And Experience
Pay: compensation range details
Benefits: benefits description + Being You + What You Can Expect (since they are about employee experience, benefits, culture). This seems plausible.
We must not create headings with filler text. All sections have real content.
Now we need to output HTML fragment only, no /. Use headings,
for prose,
- for lists.
We need to preserve all substantive information; not invent or summarize away detail. So we need to copy text exactly? We can keep the wording but ensure not to omit details.
Let's extract each section's content.
**Who We Are**: "At Kyndryl, we design, build, manage and modernize the mission-critical technology systems that the world depends on every day. So why work at Kyndryl? We are always moving forward – always pushing ourselves to go further in our efforts to build a more equitable, inclusive world for our employees, our customers and our communities."
**The Role**: "Your role As a Visual Designer, you will shape how Kyndryl shows up across key brand touchpoints by creating clear, consistent, and engaging visual experiences. The focus of this role is execution at the surface level, translating established brand direction into high quality design outputs that support business and customer goals. Your work will make information easier to understand, strengthen brand recognition, and ensure visual consistency across channels. You will primarily balance hands on design production with collaboration, working independently on assigned deliverables while partnering closely with marketing, communications, and experience teams."
Combine these two paragraphs for About the role.
**What You Will Do** (Responsibilities): list items:
- Create visual design assets that reflect Kyndryl brand standards across digital, social, web, print, and presentation formats
- Apply brand guidelines consistently to ensure a unified look and feel across all customer and internal touchpoints
- Translate briefs, content, and messaging into clear visual layouts that communicate information effectively
- Design graphics, layouts, and visual systems that support campaigns, programs, and storytelling needs
- Collaborate with writers, marketers, and experience designers to align visuals with intent and audience needs
- Adapt existing design systems and assets for new formats and use cases
- Prepare final design files that meet quality, accessibility, and delivery requirements
**Who You Are** (Required skills and experience): list:
- Proven experience in visual design with a portfolio demonstrating brand led work across multiple touchpoints
- Strong capability in graphic design, layout, typography, and visual hierarchy
- Experience applying established brand guidelines consistently across varied media
- Ability to translate written or verbal briefs into clear, effective visual solutions
- Proficiency with industry standard design tools used for digital and presentation design
- Experience working collaboratively with cross functional teams such as marketing, communications, or experience design
- Attention to detail in preparing final assets for production and distribution
**Preferred Skills And Experience**: list:
- Experience designing for enterprise or B2B audiences
- Familiarity with accessibility considerations in visual design
- Experience supporting campaigns across both digital and physical environments
- Exposure to presentation design and visual storytelling for executive audiences
**Pay And Benefits**: compensation range text:
"The compensation range for the position in the U.S. is - $143,640 to $273,000 based on a full-time schedule. Your actual compensation may vary depending on your geography, job-related skills and experience. For part-time roles, the compensation will be adjusted appropriately. The pay or salary range will not be below any applicable state, city or local minimum wage requirement. There is a different applicable compensation range for the following work locations: California (San Francisco Bay Area): $172,440 to $327,600 California (All Other): $158,040 to $300,360 Colorado: $143,640 to $273,000 Massachusetts/ Virginia: $143,640 to $300,360 New York City: $172,440 to $327,600 Washington: $158,040 to $300,360 Washington DC: $158,040 to $300,360 This position will be eligible for Kyndryl’s discretionary annual bonus program, based on performance and subject to the terms of Kyndryl’s applicable plans. You may also receive a comprehensive benefits package which includes medical and dental coverage, disability, retirement benefits, paid leave, and paid time off. Note: If this is a sales commission eligible role, you will be eligible to participate in a sales commission plan in lieu of the annual discretionary bonus program."
We need to split into Pay and Benefits sections.
Pay: compensation range details (including location-specific ranges, full-time, part-time, minimum wage note, bonus program, sales commission note). Benefits: comprehensive benefits package description (medical, dental, disability, retirement, paid leave, paid time off). Also maybe the note about sales commission is part of Pay.
Thus:
Pay section: include all compensation text except the benefits sentence.
Benefits section: include the sentence about comprehensive benefits package.
Now "Being You" and "What You Can Expect": we need to include them somewhere. Could put under Benefits as additional culture/benefits? But they are not benefits per se. However we could create a separate section "Skills"? Not appropriate.
Maybe we can create a section "About the role" also includes culture? But that seems off.
Given instruction to prefer few substantive sections, we could add another section "Culture" but not in examples. However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It does not forbid other headings, but says use those for section headings. It might be okay to use other headings as long as they are . But to be safe, we could incorporate Being You and What You Can Expect into Benefits section as additional employee offerings (like learning programs, volunteering). That seems plausible: benefits package can be extended to include learning programs, volunteering, etc. We'll include them as part of Benefits.
Thus Benefits section will contain:
- comprehensive benefits package which includes medical and dental coverage, disability, retirement benefits, paid leave, and paid time off.
- Through our company-wide volunteering and giving platform, you can donate, start fundraisers, volunteer, and search over 2 million non-profit organizations.
- Our employee learning programs give you access to the best learning in the industry to receive certifications, including Microsoft, Google, Amazon, Skillsoft, and many more.
- At Kyndryl, we invest heavily in you, we want you to succeed so that together, we will all succeed.
- Also include the Being You paragraph about diversity and inclusion networks.
We need to preserve all substantive information; we must not omit
Requirements
with list. - Qualifications? Could be "Preferred Skills And Experience". UsePreferred Skills
maybe "Qualifications". But instruction list includes Qualifications as possible heading. We'll useQualifications
for preferred skills. - Skills: maybe we can combine? But we already have Requirements and Qualifications. Could also have Skills section but not needed. - Benefits: "Pay And Benefits" includes pay range and benefits description. We need separate Pay and Benefits sections only if posting actually states them. It does state pay range and benefits. So we needPay
with the compensation range details. AndBenefits
with benefits description. - Schedule: Not mentioned; we should not create Schedule section. - Also there is "Being You" (diversity inclusion) and "What You Can Expect" (learning programs, volunteering). Could be considered as "About the company" or "Culture". Could map to "About the role"? Not exactly. Could create a section "Company Culture" but not in allowed list. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says "e.g." meaning those are examples, not exclusive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings. If content doesn't fit, maybe we omit or combine into existing sections.
We have "Who We Are" (company description) could go under About the role? Not ideal but maybe we can put under About the role as introductory paragraph.
"Being You" and "What You Can Expect" could be part of Benefits? Not really. Could be omitted? But we must preserve ALL substantive information; cannot invent or summarize away detail. So we need to include that info somewhere. If we cannot create a heading not in list, maybe we can incorporate into existing sections like Benefits or Qualifications? But that would misrepresent. However instruction: "Prefer a few substantive sections over many thin ones." It doesn't forbid other headings, but says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; we could also use other headings if needed? The examples are just examples. Safer to stick to those headings but we can include multiple paragraphs under each.
We could create sections: About the role (includes Who We Are + The Role), Responsibilities (What You Will Do), Requirements (Who You Are Required skills), Qualifications (Preferred Skills And Experience), Pay (Pay And Benefits compensation), Benefits (Pay And Benefits benefits + Being You + What You Can Expect maybe). But Benefits should be about benefits only; but we can include other culture info there? Might be stretching.
Alternatively we could create sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. And put culture info under Benefits? Not ideal.
Maybe we can create a section "Skills" for both required and preferred? But we already have Requirements and Qualifications.
Given the instruction to prefer few substantive sections, we could combine Required and Preferred into Requirements? But they said separate.
Let's think: The posting includes:
- Who We Are (company overview)
- The Role (role description)
- What You Will Do (responsibilities)
- Who You Are (required skills)
- Preferred Skills And Experience
- Pay And Benefits
- Being You (diversity inclusion)
- What You Can Expect (learning, volunteering, etc.)
We could map:
About the role: combine Who We Are + The Role (company + role description)
Responsibilities: What You Will Do
Requirements: Who You Are (required skills)
Qualifications: Preferred Skills And Experience
Pay: compensation range details
Benefits: benefits description + Being You + What You Can Expect (since they are about employee experience, benefits, culture). This seems plausible.
We must not create headings with filler text. All sections have real content.
Now we need to output HTML fragment only, no /. Use headings,
headings,
for prose,
- for lists.
We need to preserve all substantive information; not invent or summarize away detail. So we need to copy text exactly? We can keep the wording but ensure not to omit details.
Let's extract each section's content.
**Who We Are**: "At Kyndryl, we design, build, manage and modernize the mission-critical technology systems that the world depends on every day. So why work at Kyndryl? We are always moving forward – always pushing ourselves to go further in our efforts to build a more equitable, inclusive world for our employees, our customers and our communities."
**The Role**: "Your role As a Visual Designer, you will shape how Kyndryl shows up across key brand touchpoints by creating clear, consistent, and engaging visual experiences. The focus of this role is execution at the surface level, translating established brand direction into high quality design outputs that support business and customer goals. Your work will make information easier to understand, strengthen brand recognition, and ensure visual consistency across channels. You will primarily balance hands on design production with collaboration, working independently on assigned deliverables while partnering closely with marketing, communications, and experience teams."
Combine these two paragraphs for About the role.
**What You Will Do** (Responsibilities): list items:
- Create visual design assets that reflect Kyndryl brand standards across digital, social, web, print, and presentation formats
- Apply brand guidelines consistently to ensure a unified look and feel across all customer and internal touchpoints
- Translate briefs, content, and messaging into clear visual layouts that communicate information effectively
- Design graphics, layouts, and visual systems that support campaigns, programs, and storytelling needs
- Collaborate with writers, marketers, and experience designers to align visuals with intent and audience needs
- Adapt existing design systems and assets for new formats and use cases
- Prepare final design files that meet quality, accessibility, and delivery requirements
**Who You Are** (Required skills and experience): list:
- Proven experience in visual design with a portfolio demonstrating brand led work across multiple touchpoints
- Strong capability in graphic design, layout, typography, and visual hierarchy
- Experience applying established brand guidelines consistently across varied media
- Ability to translate written or verbal briefs into clear, effective visual solutions
- Proficiency with industry standard design tools used for digital and presentation design
- Experience working collaboratively with cross functional teams such as marketing, communications, or experience design
- Attention to detail in preparing final assets for production and distribution
**Preferred Skills And Experience**: list:
- Experience designing for enterprise or B2B audiences
- Familiarity with accessibility considerations in visual design
- Experience supporting campaigns across both digital and physical environments
- Exposure to presentation design and visual storytelling for executive audiences
**Pay And Benefits**: compensation range text:
"The compensation range for the position in the U.S. is - $143,640 to $273,000 based on a full-time schedule. Your actual compensation may vary depending on your geography, job-related skills and experience. For part-time roles, the compensation will be adjusted appropriately. The pay or salary range will not be below any applicable state, city or local minimum wage requirement. There is a different applicable compensation range for the following work locations: California (San Francisco Bay Area): $172,440 to $327,600 California (All Other): $158,040 to $300,360 Colorado: $143,640 to $273,000 Massachusetts/ Virginia: $143,640 to $300,360 New York City: $172,440 to $327,600 Washington: $158,040 to $300,360 Washington DC: $158,040 to $300,360 This position will be eligible for Kyndryl’s discretionary annual bonus program, based on performance and subject to the terms of Kyndryl’s applicable plans. You may also receive a comprehensive benefits package which includes medical and dental coverage, disability, retirement benefits, paid leave, and paid time off. Note: If this is a sales commission eligible role, you will be eligible to participate in a sales commission plan in lieu of the annual discretionary bonus program."
We need to split into Pay and Benefits sections.
Pay: compensation range details (including location-specific ranges, full-time, part-time, minimum wage note, bonus program, sales commission note). Benefits: comprehensive benefits package description (medical, dental, disability, retirement, paid leave, paid time off). Also maybe the note about sales commission is part of Pay.
Thus:
Pay section: include all compensation text except the benefits sentence.
Benefits section: include the sentence about comprehensive benefits package.
Now "Being You" and "What You Can Expect": we need to include them somewhere. Could put under Benefits as additional culture/benefits? But they are not benefits per se. However we could create a separate section "Skills"? Not appropriate.
Maybe we can create a section "About the role" also includes culture? But that seems off.
Given instruction to prefer few substantive sections, we could add another section "Culture" but not in examples. However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It does not forbid other headings, but says use those for section headings. It might be okay to use other headings as long as they are
. But to be safe, we could incorporate Being You and What You Can Expect into Benefits section as additional employee offerings (like learning programs, volunteering). That seems plausible: benefits package can be extended to include learning programs, volunteering, etc. We'll include them as part of Benefits. Thus Benefits section will contain: - comprehensive benefits package which includes medical and dental coverage, disability, retirement benefits, paid leave, and paid time off. - Through our company-wide volunteering and giving platform, you can donate, start fundraisers, volunteer, and search over 2 million non-profit organizations. - Our employee learning programs give you access to the best learning in the industry to receive certifications, including Microsoft, Google, Amazon, Skillsoft, and many more. - At Kyndryl, we invest heavily in you, we want you to succeed so that together, we will all succeed. - Also include the Being You paragraph about diversity and inclusion networks. We need to preserve all substantive information; we must not omit