Part-Time Junior IT Specialist
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Include only sections with real specific content.
We have content: About Westman Atelier (company description) and About Our Founder (founder bio). Those are not required sections but could be considered "About the role"? Actually "About the role" is a heading we could use for the position summary. The posting includes "Position Summary" paragraph. So we can put that under
About the role
with containing the position summary.
Responsibilities: we have bullet-like paragraphs under "Responsibilities:" with subheadings: IT Support & Troubleshooting, User & Device Management, IT Operations & Vendor Coordination. Those are subheadings but we can treat each as list items? The instruction: Use
- for any list of duties/requirements/benefits. So we can create a
with each duty as - . We could keep subheadings inside
- maybe as strong text. But we can just list each bullet.
Requirements: list of requirements after "Requirements:" with many bullet-like sentences. We'll put them in
- .
Qualifications: Not separate; maybe we can combine with Requirements? The instruction says use sections only when posting has real specific content. There's no separate Qualifications section distinct from Requirements. So we skip Qualifications.
Skills: Not separate; maybe we can treat some as skills but we already have Requirements. Could create Skills section if there is explicit list of skills. The posting includes "Strong proficiency with Apple/macOS and Windows operating systems", etc. Those are skills. But we can keep them under Requirements. The instruction: Prefer a few substantive sections over many thin ones. So we can combine Requirements and Skills into one section maybe called Requirements (or Skills). But we have to use allowed headings; we can choose either Requirements or Skills. Since the posting has a "Requirements:" heading, we should use that. So we will have
Requirements
with list.
Benefits: Not mentioned. No benefits specifics. So we skip Benefits.
Pay: The posting includes "The base pay for this position will range from $25-$35/hour. Exact compensation may vary based on job related skills, experience, and location." That's specific pay info. So we need a Pay section with that info. Use .
Schedule: The posting includes "Ability to work a flexible part-time schedule on-site at our NYC headquarters as required". That's schedule info. So we need Schedule section with that info.
We also have "About Westman Atelier" and "About Our Founder". Those are company description; not required sections but could be considered "About the role"? Probably not. 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 those sections. It doesn't say we cannot add other headings, but we should follow the pattern. Probably we should include an "About the company" maybe not needed. The instruction: "Prefer a few substantive sections over many thin ones." So we could include a brief intro paragraph before sections, maybe as a
without heading. That is allowed. The job title is not repeated as heading. So we can start with a
containing the company description and founder bio? That might be too much but it's substantive. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info. We can include it as a
before sections, maybe under a heading like "About Westman Atelier"? But that's not in the allowed list. Could we still use it? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but it's implied to use those for those sections. Safer to stick to allowed headings only. So we can put the company description as a
without heading before the sections. That's acceptable.
Thus output:
About Westman Atelier ... About Our Founder ...
Then About the role
with containing Position Summary.
Then
Responsibilities
with - ... each duty.
Then
Requirements
with - ... each requirement.
Then
Pay
with pay range.
Then
Schedule
with schedule info.
We must not include sections with filler like "commensurate with experience". Not present.
Now we need to extract the exact text.
Let's copy the relevant parts.
Company description:
"About Westman Atelier A new standard of clean luxury. Founded by world-renowned editorial makeup artist Gucci Westman, Westman Atelier is a curated edit of skin-loving, performance-first makeup that is always effortless, never overdone. A mother, makeup artist, and champion of holistic living, Gucci believes passionately that ‘luxury’, ‘efficacy’ and ‘clean’ can be synonymous with exceptional makeup. A skincare approach to high performance make-up formulated with clean ingredients and no-compromise integrityBalancing perfect shades and buttery textures that melt into the skin with plant-based actives and cutting-edge science About Our Founder Gucci Westman has more than 20 years of professional experience as a major editorial makeup artist, contributing to publications like Vogue and Harper’s Bazaar. Gucci is known for creating dewy, supernaturally glowy looks and her highly coveted “second-skin approach” to makeup, resulting in naturally beautiful, radiantly amplified skin."
Note there is a missing space between "integrityBalancing". We'll keep as is.
Position Summary:
"In this role, based in NYC, you will provide day-to-day technical support to employees across our corporate and retail environments, ensuring our teams have the technology, access, and tools required to work effectively. Reporting to the VP, People, you will troubleshoot hardware and software issues, support onboarding and offboarding tech logistics, oversee IT inventory, and partner with external IT vendors on complex escalations. This is a dynamic, highly collaborative role ideal for an entry-to-junior level IT professional looking to build a strong foundation across IT support, systems administration, asset management, security, and technology operations within a fast-growing prestige brand environment"
Now Responsibilities: The text after "Responsibilities:" includes three sub-sections.
We need to capture each duty as list items.
Let's extract:
IT Support & Troubleshooting
- Serve as the primary first-line technical support to corporate and retail employees, resolving hardware, software, network connectivity, and user access issues across Mac and PC environments
- Provide dedicated, hands-on on-site support in our NYC office for hardware setups, printer/Wi-Fi troubleshooting, and any other employee tech needs
- Respond to and prioritize IT support tickets and requests in a timely, service-oriented manner based on business impact and urgency
- Set up, configure, deploy, and troubleshoot workplace hardware, including laptops, monitors, mobile devices, printers, conference room AV equipment, and other workplace technology
- Escalate more complex technical issues to external IT partners or appropriate internal resources while maintaining ownership through resolution
- Document recurring IT issues, solutions, standard operating procedures, equipment inventory, and system information to streamline internal IT operations
User & Device Management
- Manage the IT lifecycle for employee onboarding and offboarding, including account setup/deprovisioning (Google Workspace, Slack, etc.), device preparation, access provisioning, and equipment collection
- Maintain complete and accurate records of company IT assets, including laptops, iPads, mobile devices, monitors, and accessories using inventory management tools
- Perform routine software installations, operating system updates, and device configuration
- Coordinate user access permissions across core business applications, enforcing established security, password and access standards
IT Operations & Vendor Coordination
- Partner closely with external IT providers, consultants, and technology vendors to escalate and resolve complex network or technical infrastructure issues
- Assist with IT projects, system implementations, technology rollouts, and hardware upgrades as needed
- Stay current on new tools and technology, and proactively identify opportunities to improve the employee technology experience and streamline or automate repetitive administrative workflows
We'll combine into a single list.
Now Requirements: after "Requirements:" we have a paragraph with many items separated by semicolons or line breaks. Let's extract each as list item.
The text:
"Bachelor's degree in Information Technology, Computer Science or related field
1-3 years of experience in IT support, help desk, technical support, or a related role; internship or other relevant hands-on experience will also be considered
Strong proficiency with Apple/macOS and Windows operating systems
Familiarity with cloud-based productivity suites (Google Workspace, Microsoft 365, Slack, Zoom) and common workplace applications
Strong understanding of office networking, Wi-Fi configuration, VPNs, and device management
Exceptional customer service orientation with the ability to communicate technical information clearly and empathetically to non-technical users
Highly organized with rigorous attention to detail and strong follow-through
Strong interest in technology with an eagerness to learn and develop across a broad range of IT functions
Strong problem-solving skills with the self-motivation to troubleshoot common hardware, software, connectivity, and user-access issues independently and know when to escalate
Comfortable working in a fast-paced, growing environment where priorities may shift quickly
Ability to work a flexible part-time schedule on-site at our NYC headquarters as required"
Note the last item about schedule is also in Requirements but we already have Schedule section; but it's also a requirement. We could keep it in Requirements as well, but schedule is also a separate section. The instruction: do not repeat info? It didn't forbid duplication but better to avoid duplication. However the schedule info appears also in Requirements; we could keep it in Requirements and also have Schedule section? Might be duplication. Better to keep schedule only in Schedule section, and maybe remove from Requirements list. But the requirement list includes that as a requirement; we could keep it there as it's a requirement. But then Schedule section would be duplicate. The instruction says preserve ALL substantive information; we can keep it in both places? That would be duplication but not losing info. However they said "Prefer a few substantive sections over many thin ones." Duplication might be considered thin? Not sure. Safer to keep schedule only in Schedule section and omit from Requirements list. But then we lose that requirement info. However the schedule requirement is also a requirement; but we still have it in Schedule section, so it's preserved. So we can omit from Requirements.
Thus Requirements list items (excluding the schedule line). We'll keep the rest.
Now Pay: "The base pay for this position will range from $25-$35/hour. Exact compensation may vary based on job related skills, experience, and location."
Schedule: "Ability to work a flexible part-time schedule on-site at our NYC headquarters as required"
Now we need to output HTML.
We'll start with a
containing company description and founder bio. Ensure proper spacing.
Let's craft:
About Westman Atelier A new standard of clean luxury. Founded by world-renowned editorial makeup artist Gucci Westman, Westman Atelier is a curated edit of skin-loving, performance-first makeup that is always effortless, never overdone. A mother, makeup artist, and champion of holistic living, Gucci believes passionately that ‘luxury’, ‘efficacy’ and ‘clean’ can be synonymous with exceptional makeup. A skincare approach to high performance make-up formulated with clean ingredients
for prose. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Include only sections with real specific content. We have content: About Westman Atelier (company description) and About Our Founder (founder bio). Those are not required sections but could be considered "About the role"? Actually "About the role" is a heading we could use for the position summary. The posting includes "Position Summary" paragraph. So we can put that under
About the role
withcontaining the position summary. Responsibilities: we have bullet-like paragraphs under "Responsibilities:" with subheadings: IT Support & Troubleshooting, User & Device Management, IT Operations & Vendor Coordination. Those are subheadings but we can treat each as list items? The instruction: Use
- for any list of duties/requirements/benefits. So we can create a
- with each duty as
- . We could keep subheadings inside
- maybe as strong text. But we can just list each bullet.
Requirements: list of requirements after "Requirements:" with many bullet-like sentences. We'll put them in
- .
Qualifications: Not separate; maybe we can combine with Requirements? The instruction says use sections only when posting has real specific content. There's no separate Qualifications section distinct from Requirements. So we skip Qualifications.
Skills: Not separate; maybe we can treat some as skills but we already have Requirements. Could create Skills section if there is explicit list of skills. The posting includes "Strong proficiency with Apple/macOS and Windows operating systems", etc. Those are skills. But we can keep them under Requirements. The instruction: Prefer a few substantive sections over many thin ones. So we can combine Requirements and Skills into one section maybe called Requirements (or Skills). But we have to use allowed headings; we can choose either Requirements or Skills. Since the posting has a "Requirements:" heading, we should use that. So we will have
Requirements
with list. Benefits: Not mentioned. No benefits specifics. So we skip Benefits. Pay: The posting includes "The base pay for this position will range from $25-$35/hour. Exact compensation may vary based on job related skills, experience, and location." That's specific pay info. So we need a Pay section with that info. Use. Schedule: The posting includes "Ability to work a flexible part-time schedule on-site at our NYC headquarters as required". That's schedule info. So we need Schedule section with that info. We also have "About Westman Atelier" and "About Our Founder". Those are company description; not required sections but could be considered "About the role"? Probably not. 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 those sections. It doesn't say we cannot add other headings, but we should follow the pattern. Probably we should include an "About the company" maybe not needed. The instruction: "Prefer a few substantive sections over many thin ones." So we could include a brief intro paragraph before sections, maybe as a
without heading. That is allowed. The job title is not repeated as heading. So we can start with a
containing the company description and founder bio? That might be too much but it's substantive. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info. We can include it as a
before sections, maybe under a heading like "About Westman Atelier"? But that's not in the allowed list. Could we still use it? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but it's implied to use those for those sections. Safer to stick to allowed headings only. So we can put the company description as a
without heading before the sections. That's acceptable. Thus output:
About Westman Atelier ... About Our Founder ...
ThenAbout the role
withcontaining Position Summary. Then
Responsibilities
with- ... each duty.
Then
Requirements
with- ... each requirement.
Then
Pay
withpay range. Then
Schedule
withschedule info. We must not include sections with filler like "commensurate with experience". Not present. Now we need to extract the exact text. Let's copy the relevant parts. Company description: "About Westman Atelier A new standard of clean luxury. Founded by world-renowned editorial makeup artist Gucci Westman, Westman Atelier is a curated edit of skin-loving, performance-first makeup that is always effortless, never overdone. A mother, makeup artist, and champion of holistic living, Gucci believes passionately that ‘luxury’, ‘efficacy’ and ‘clean’ can be synonymous with exceptional makeup. A skincare approach to high performance make-up formulated with clean ingredients and no-compromise integrityBalancing perfect shades and buttery textures that melt into the skin with plant-based actives and cutting-edge science About Our Founder Gucci Westman has more than 20 years of professional experience as a major editorial makeup artist, contributing to publications like Vogue and Harper’s Bazaar. Gucci is known for creating dewy, supernaturally glowy looks and her highly coveted “second-skin approach” to makeup, resulting in naturally beautiful, radiantly amplified skin." Note there is a missing space between "integrityBalancing". We'll keep as is. Position Summary: "In this role, based in NYC, you will provide day-to-day technical support to employees across our corporate and retail environments, ensuring our teams have the technology, access, and tools required to work effectively. Reporting to the VP, People, you will troubleshoot hardware and software issues, support onboarding and offboarding tech logistics, oversee IT inventory, and partner with external IT vendors on complex escalations. This is a dynamic, highly collaborative role ideal for an entry-to-junior level IT professional looking to build a strong foundation across IT support, systems administration, asset management, security, and technology operations within a fast-growing prestige brand environment" Now Responsibilities: The text after "Responsibilities:" includes three sub-sections. We need to capture each duty as list items. Let's extract: IT Support & Troubleshooting - Serve as the primary first-line technical support to corporate and retail employees, resolving hardware, software, network connectivity, and user access issues across Mac and PC environments - Provide dedicated, hands-on on-site support in our NYC office for hardware setups, printer/Wi-Fi troubleshooting, and any other employee tech needs - Respond to and prioritize IT support tickets and requests in a timely, service-oriented manner based on business impact and urgency - Set up, configure, deploy, and troubleshoot workplace hardware, including laptops, monitors, mobile devices, printers, conference room AV equipment, and other workplace technology - Escalate more complex technical issues to external IT partners or appropriate internal resources while maintaining ownership through resolution - Document recurring IT issues, solutions, standard operating procedures, equipment inventory, and system information to streamline internal IT operations User & Device Management - Manage the IT lifecycle for employee onboarding and offboarding, including account setup/deprovisioning (Google Workspace, Slack, etc.), device preparation, access provisioning, and equipment collection - Maintain complete and accurate records of company IT assets, including laptops, iPads, mobile devices, monitors, and accessories using inventory management tools - Perform routine software installations, operating system updates, and device configuration - Coordinate user access permissions across core business applications, enforcing established security, password and access standards IT Operations & Vendor Coordination - Partner closely with external IT providers, consultants, and technology vendors to escalate and resolve complex network or technical infrastructure issues - Assist with IT projects, system implementations, technology rollouts, and hardware upgrades as needed - Stay current on new tools and technology, and proactively identify opportunities to improve the employee technology experience and streamline or automate repetitive administrative workflows We'll combine into a single list. Now Requirements: after "Requirements:" we have a paragraph with many items separated by semicolons or line breaks. Let's extract each as list item. The text: "Bachelor's degree in Information Technology, Computer Science or related field 1-3 years of experience in IT support, help desk, technical support, or a related role; internship or other relevant hands-on experience will also be considered Strong proficiency with Apple/macOS and Windows operating systems Familiarity with cloud-based productivity suites (Google Workspace, Microsoft 365, Slack, Zoom) and common workplace applications Strong understanding of office networking, Wi-Fi configuration, VPNs, and device management Exceptional customer service orientation with the ability to communicate technical information clearly and empathetically to non-technical users Highly organized with rigorous attention to detail and strong follow-through Strong interest in technology with an eagerness to learn and develop across a broad range of IT functions Strong problem-solving skills with the self-motivation to troubleshoot common hardware, software, connectivity, and user-access issues independently and know when to escalate Comfortable working in a fast-paced, growing environment where priorities may shift quickly Ability to work a flexible part-time schedule on-site at our NYC headquarters as required" Note the last item about schedule is also in Requirements but we already have Schedule section; but it's also a requirement. We could keep it in Requirements as well, but schedule is also a separate section. The instruction: do not repeat info? It didn't forbid duplication but better to avoid duplication. However the schedule info appears also in Requirements; we could keep it in Requirements and also have Schedule section? Might be duplication. Better to keep schedule only in Schedule section, and maybe remove from Requirements list. But the requirement list includes that as a requirement; we could keep it there as it's a requirement. But then Schedule section would be duplicate. The instruction says preserve ALL substantive information; we can keep it in both places? That would be duplication but not losing info. However they said "Prefer a few substantive sections over many thin ones." Duplication might be considered thin? Not sure. Safer to keep schedule only in Schedule section and omit from Requirements list. But then we lose that requirement info. However the schedule requirement is also a requirement; but we still have it in Schedule section, so it's preserved. So we can omit from Requirements. Thus Requirements list items (excluding the schedule line). We'll keep the rest. Now Pay: "The base pay for this position will range from $25-$35/hour. Exact compensation may vary based on job related skills, experience, and location." Schedule: "Ability to work a flexible part-time schedule on-site at our NYC headquarters as required" Now we need to output HTML. We'll start with a
containing company description and founder bio. Ensure proper spacing. Let's craft:
About Westman Atelier A new standard of clean luxury. Founded by world-renowned editorial makeup artist Gucci Westman, Westman Atelier is a curated edit of skin-loving, performance-first makeup that is always effortless, never overdone. A mother, makeup artist, and champion of holistic living, Gucci believes passionately that ‘luxury’, ‘efficacy’ and ‘clean’ can be synonymous with exceptional makeup. A skincare approach to high performance make-up formulated with clean ingredients
- ... each requirement.
Then
- ... each duty.
Then
- .
Qualifications: Not separate; maybe we can combine with Requirements? The instruction says use sections only when posting has real specific content. There's no separate Qualifications section distinct from Requirements. So we skip Qualifications.
Skills: Not separate; maybe we can treat some as skills but we already have Requirements. Could create Skills section if there is explicit list of skills. The posting includes "Strong proficiency with Apple/macOS and Windows operating systems", etc. Those are skills. But we can keep them under Requirements. The instruction: Prefer a few substantive sections over many thin ones. So we can combine Requirements and Skills into one section maybe called Requirements (or Skills). But we have to use allowed headings; we can choose either Requirements or Skills. Since the posting has a "Requirements:" heading, we should use that. So we will have