Director, Global Equity
for each heading. Only include sections where there is real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate (EEO, privacy, etc). Must not create sections with filler like "commensurate with experience". Must only include sections if posting has real specific content.
We need to parse the posting.
Key sections:
- About Faire (intro) maybe not needed as heading? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings.
We have "About This Role" which is like About the role. So we can put that under About the role
with paragraph(s).
Responsibilities: The bullet list after "As a Director, Global Equity You Will" includes many responsibilities. So we can put under Responsibilities
with - each.
Requirements: Might be similar to Qualifications? The posting has "Qualifications" section with bullet list. Also there may be "Requirements" separate? Not really. The posting includes "Qualifications" with bullet list. Also there may be "Skills" maybe derived from qualifications? But we should not create thin sections. We have Qualifications content. We could treat that as Qualifications section. Requirements maybe not present distinct; we could omit Requirements if no specific content separate from Qualifications. However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications? But they ask to use headings for those categories if content exists. Since we have Qualifications content, we can output Qualifications. Requirements maybe not present; we could omit.
Skills: Could be derived from qualifications but maybe not separate. The qualifications list includes skills like "Advanced analytical and systems skills; Shareworks (or equivalent) expertise required." That's more skill. But we could still put under Qualifications. To avoid thin sections, we could just have Qualifications and maybe Skills combined? But instruction: Use headings for those categories if posting has real specific content. The posting does not have a separate "Skills" heading; it's embedded in Qualifications. So we could either not create Skills section, or we could create Skills section with content extracted from qualifications. But that might be inventing heading not present. Safer to follow the posting: we have Qualifications section; we can output that. No separate Skills.
Benefits: The posting mentions "This role will also be eligible for equity and benefits." Also later: "Real rewards. Competitive pay, equity, and comprehensive benefits designed to support your life inside and outside of work." Also earlier: "We’re looking for smart..." Not specific benefits list. There's no detailed benefits like health, 401k etc. So we have only generic statement. According to instruction: never create Benefits section unless posting actually states them. It does state eligibility for equity and benefits, but not specific benefits. Is that enough? It says "eligible for equity and benefits." That's a statement but not specific. Might be considered not specific enough? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits exist, but not details. Might be okay to include Benefits section with that statement? However they said "Prefer a few substantive sections over many thin ones." A thin Benefits section with just "eligible for equity and benefits" might be thin. Could combine with Pay? But Pay is specific with salary ranges. So we could have Pay section and maybe Benefits omitted. However the instruction says never create Benefits section unless posting actually states them. It does state them (eligible for equity and benefits). So we could include Benefits with that sentence. But we need to avoid filler like "not specified". This is not filler; it's a statement. So we can include Benefits.
Pay: Salary ranges given for zones. So we include Pay section with that info.
Schedule: The posting mentions hybrid work: "Hybrid Faire employees currently go into the office 3 days per week on Tuesdays, Thursdays, and a third flex day of their choosing (Monday, Wednesday, or Friday). Additionally, hybrid in-office roles will have the flexibility to work remotely up to 4 weeks per year. Specific Workplace and Information Technology positions may require onsite attendance 5 days per week as will be indicated in the job posting." This is schedule info. So we can include Schedule section with that.
Now we need to output HTML fragment only, no /. Use
headings,
for prose,
- for lists.
We must not repeat job title. The job title is "Director, Global Equity". Not to be used as heading.
We must not include Job ID etc.
We must remove boilerplate: EEO, privacy, accommodation request, etc. Also remove "About Faire" intro? That's not under headings but we could include as part of About the role? Actually "About Faire" is company description; not needed per headings. Could we include it under About the role? The About the role section should contain the role description. The "About This Role" paragraph is appropriate. The earlier "About Faire" is company overview; could be omitted or maybe included in About the role as context? But instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company overview? It's substantive but not under any heading. Where to put? Could put as a
before any heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having plain paragraphs outside headings. So we can include a
with the company overview before the headings. That preserves info.
Similarly, the "Why you’ll love working at Faire" section is also substantive; we could include as a
maybe under Benefits? Or as its own section? Not a defined heading. Could include as a
after Benefits or before. It's about culture; could be included as a
maybe under a generic section? But we don't have a heading for culture. We could just add a
after Benefits heading? But that would be under Benefits? Better to add a separate
after Benefits heading but before closing? Actually we can just add a
after the Benefits
maybe. But we need to keep it.
Also the "Faire was founded in 2017..." etc is also substantive; we could include as a after the Why you love working at Faire paragraph.
Also the "To learn more about Faire..." etc is maybe boilerplate? It's a link to blog; could be considered navigation? Might be considered optional but it's substantive? It's a link to blog; maybe we keep as
. However it's not under any heading; we can include as a
.
But we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "To learn more about Faire and our customers, you can read more on our blog." is not boilerplate; it's a referral. Keep.
The "Faire provides equal employment opportunities (EEO)..." is EEO boilerplate; remove.
The "Privacy For information about the type of personal data..." is privacy boilerplate; remove.
Now we need to ensure we don't repeat content.
Let's extract sections:
Company overview (About Faire): "Faire is a technology wholesale platform built on the belief that the future is local. Independent retailers around the globe collectively represent a multi-hundred-billion-dollar wholesale market that has historically been fragmented and offline. At Faire, we're using the power of tech, data, and machine learning to connect this thriving community of entrepreneurs across the globe. Picture your favorite boutique in town — we help them discover the best products from around the world to sell in their stores. With the right tools and insights, we believe that we can level the playing field so businesses can grow and local communities can thrive. We’re looking for smart, resourceful and passionate people to join us as we power the shop local movement. If you believe in community, come join ours."
That's substantive.
About the role: "About This Role Faire is revolutionizing wholesale and helping local retailers and their suppliers succeed in a technology-enabled era. As a Director, Global Equity, you will own and continue to evolve Faire’s global equity programs, building on an existing foundation while enhancing the structure, rigor, and scalability required to support public company readiness. This is a high-impact role for someone who thrives in fast-paced environments, brings strong judgment, and wants to shape how equity operates with true end-to-end ownership."
We could combine with the following bullet list? Actually the bullet list starts after "As a Director, Global Equity You Will". That's part of responsibilities. So About the role is the paragraph above.
Responsibilities: bullet list:
- Own and scale Faire’s global equity programs end-to-end, spanning plan design, administration, accounting, compliance, and employee experience across all equity award types and jurisdictions.
- Serve as the senior owner of equity operations, partnering with Finance, Accounting, Payroll, Legal, and People to build durable, audit-ready processes that scale with company growth.
- Lead public company equity responsibilities, including SEC reporting support, insider trading programs, audit readiness, and the design and operation of equity-related internal controls.
- Oversee the full equity lifecycle, including grant issuance, vesting, exercises, releases, share pool management, and reconciliations between the equity platform and general ledger.
- Design, implement, and optimize equity systems and workflows, including Shareworks (or equivalent) integrations with payroll, HRIS, and financial reporting systems.
- Act as a trusted advisor and escalation point for complex employee, executive, and stakeholder equity matters, exercising sound judgment and discretion.
- Proactively manage global regulatory, tax, and compliance risk, partnering with Legal and external advisors to ensure equity programs remain compliant as Faire scales internationally.
We need to preserve all.
Qualifications: bullet list:
- Bachelor’s degree in Economics, Finance, Accounting, Law or equivalent practical experience
- 10+ years of experience in stock plan administration, including leadership in complex or high-growth environments
- CEP certification strongly preferred
- Deep expertise in global equity programs, with hands-on knowledge of legal, tax, and payroll considerations across multiple jurisdictions.
- Experience with designing and implementing an Employee Stock Purchase Plan
- Proven experience scaling equity programs through private-to-public readiness or public company operations.
- Advanced analytical and systems skills; Shareworks (or equivalent) expertise required.
- Demonstrated ability to influence cross-functionally without authority, including working with senior leaders.
- You are resourceful and not afraid to roll up your sleeves.
We could treat that as Qualifications.
Pay: Salary ranges:
- California & New York: the pay range for this role is $184,000 to $253,000 per year.
- Zone B: the pay range for this role is $165,500 to $227,500 per year.
- Zone C: the pay range for this role is $147,000 to $202,500 per year.
- Note: This is a remote role open to candidates located in [list of states].
- This role will also be eligible for equity and benefits.
- Actual base pay will be determined based on permissible factors such as transferable skills, work experience, market demands, and primary work location.
- The base pay range provided is subject to change and may be modified in the future.
We need to include all that. The list of states is long; we should keep it.
Schedule: Hybrid work info:
- Hybrid Faire employees currently go into the office 3 days per week on Tuesdays, Thurs
About the role
with paragraph(s). Responsibilities: The bullet list after "As a Director, Global Equity You Will" includes many responsibilities. So we can put underResponsibilities
with- each.
Requirements: Might be similar to Qualifications? The posting has "Qualifications" section with bullet list. Also there may be "Requirements" separate? Not really. The posting includes "Qualifications" with bullet list. Also there may be "Skills" maybe derived from qualifications? But we should not create thin sections. We have Qualifications content. We could treat that as Qualifications section. Requirements maybe not present distinct; we could omit Requirements if no specific content separate from Qualifications. However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications? But they ask to use headings for those categories if content exists. Since we have Qualifications content, we can output Qualifications. Requirements maybe not present; we could omit.
Skills: Could be derived from qualifications but maybe not separate. The qualifications list includes skills like "Advanced analytical and systems skills; Shareworks (or equivalent) expertise required." That's more skill. But we could still put under Qualifications. To avoid thin sections, we could just have Qualifications and maybe Skills combined? But instruction: Use headings for those categories if posting has real specific content. The posting does not have a separate "Skills" heading; it's embedded in Qualifications. So we could either not create Skills section, or we could create Skills section with content extracted from qualifications. But that might be inventing heading not present. Safer to follow the posting: we have Qualifications section; we can output that. No separate Skills.
Benefits: The posting mentions "This role will also be eligible for equity and benefits." Also later: "Real rewards. Competitive pay, equity, and comprehensive benefits designed to support your life inside and outside of work." Also earlier: "We’re looking for smart..." Not specific benefits list. There's no detailed benefits like health, 401k etc. So we have only generic statement. According to instruction: never create Benefits section unless posting actually states them. It does state eligibility for equity and benefits, but not specific benefits. Is that enough? It says "eligible for equity and benefits." That's a statement but not specific. Might be considered not specific enough? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits exist, but not details. Might be okay to include Benefits section with that statement? However they said "Prefer a few substantive sections over many thin ones." A thin Benefits section with just "eligible for equity and benefits" might be thin. Could combine with Pay? But Pay is specific with salary ranges. So we could have Pay section and maybe Benefits omitted. However the instruction says never create Benefits section unless posting actually states them. It does state them (eligible for equity and benefits). So we could include Benefits with that sentence. But we need to avoid filler like "not specified". This is not filler; it's a statement. So we can include Benefits.
Pay: Salary ranges given for zones. So we include Pay section with that info.
Schedule: The posting mentions hybrid work: "Hybrid Faire employees currently go into the office 3 days per week on Tuesdays, Thursdays, and a third flex day of their choosing (Monday, Wednesday, or Friday). Additionally, hybrid in-office roles will have the flexibility to work remotely up to 4 weeks per year. Specific Workplace and Information Technology positions may require onsite attendance 5 days per week as will be indicated in the job posting." This is schedule info. So we can include Schedule section with that.
Now we need to output HTML fragment only, no /. Use
headings,
for prose,
- for lists.
We must not repeat job title. The job title is "Director, Global Equity". Not to be used as heading.
We must not include Job ID etc.
We must remove boilerplate: EEO, privacy, accommodation request, etc. Also remove "About Faire" intro? That's not under headings but we could include as part of About the role? Actually "About Faire" is company description; not needed per headings. Could we include it under About the role? The About the role section should contain the role description. The "About This Role" paragraph is appropriate. The earlier "About Faire" is company overview; could be omitted or maybe included in About the role as context? But instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company overview? It's substantive but not under any heading. Where to put? Could put as a
before any heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having plain paragraphs outside headings. So we can include a
with the company overview before the headings. That preserves info. Similarly, the "Why you’ll love working at Faire" section is also substantive; we could include as a
maybe under Benefits? Or as its own section? Not a defined heading. Could include as a
after Benefits or before. It's about culture; could be included as a
maybe under a generic section? But we don't have a heading for culture. We could just add a
after Benefits heading? But that would be under Benefits? Better to add a separate
after Benefits heading but before closing? Actually we can just add a
after the Benefits
- maybe. But we need to keep it.
Also the "Faire was founded in 2017..." etc is also substantive; we could include as a
after the Why you love working at Faire paragraph. Also the "To learn more about Faire..." etc is maybe boilerplate? It's a link to blog; could be considered navigation? Might be considered optional but it's substantive? It's a link to blog; maybe we keep as
. However it's not under any heading; we can include as a
. But we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "To learn more about Faire and our customers, you can read more on our blog." is not boilerplate; it's a referral. Keep. The "Faire provides equal employment opportunities (EEO)..." is EEO boilerplate; remove. The "Privacy For information about the type of personal data..." is privacy boilerplate; remove. Now we need to ensure we don't repeat content. Let's extract sections: Company overview (About Faire): "Faire is a technology wholesale platform built on the belief that the future is local. Independent retailers around the globe collectively represent a multi-hundred-billion-dollar wholesale market that has historically been fragmented and offline. At Faire, we're using the power of tech, data, and machine learning to connect this thriving community of entrepreneurs across the globe. Picture your favorite boutique in town — we help them discover the best products from around the world to sell in their stores. With the right tools and insights, we believe that we can level the playing field so businesses can grow and local communities can thrive. We’re looking for smart, resourceful and passionate people to join us as we power the shop local movement. If you believe in community, come join ours." That's substantive. About the role: "About This Role Faire is revolutionizing wholesale and helping local retailers and their suppliers succeed in a technology-enabled era. As a Director, Global Equity, you will own and continue to evolve Faire’s global equity programs, building on an existing foundation while enhancing the structure, rigor, and scalability required to support public company readiness. This is a high-impact role for someone who thrives in fast-paced environments, brings strong judgment, and wants to shape how equity operates with true end-to-end ownership." We could combine with the following bullet list? Actually the bullet list starts after "As a Director, Global Equity You Will". That's part of responsibilities. So About the role is the paragraph above. Responsibilities: bullet list: - Own and scale Faire’s global equity programs end-to-end, spanning plan design, administration, accounting, compliance, and employee experience across all equity award types and jurisdictions. - Serve as the senior owner of equity operations, partnering with Finance, Accounting, Payroll, Legal, and People to build durable, audit-ready processes that scale with company growth. - Lead public company equity responsibilities, including SEC reporting support, insider trading programs, audit readiness, and the design and operation of equity-related internal controls. - Oversee the full equity lifecycle, including grant issuance, vesting, exercises, releases, share pool management, and reconciliations between the equity platform and general ledger. - Design, implement, and optimize equity systems and workflows, including Shareworks (or equivalent) integrations with payroll, HRIS, and financial reporting systems. - Act as a trusted advisor and escalation point for complex employee, executive, and stakeholder equity matters, exercising sound judgment and discretion. - Proactively manage global regulatory, tax, and compliance risk, partnering with Legal and external advisors to ensure equity programs remain compliant as Faire scales internationally. We need to preserve all. Qualifications: bullet list: - Bachelor’s degree in Economics, Finance, Accounting, Law or equivalent practical experience - 10+ years of experience in stock plan administration, including leadership in complex or high-growth environments - CEP certification strongly preferred - Deep expertise in global equity programs, with hands-on knowledge of legal, tax, and payroll considerations across multiple jurisdictions. - Experience with designing and implementing an Employee Stock Purchase Plan - Proven experience scaling equity programs through private-to-public readiness or public company operations. - Advanced analytical and systems skills; Shareworks (or equivalent) expertise required. - Demonstrated ability to influence cross-functionally without authority, including working with senior leaders. - You are resourceful and not afraid to roll up your sleeves. We could treat that as Qualifications. Pay: Salary ranges: - California & New York: the pay range for this role is $184,000 to $253,000 per year. - Zone B: the pay range for this role is $165,500 to $227,500 per year. - Zone C: the pay range for this role is $147,000 to $202,500 per year. - Note: This is a remote role open to candidates located in [list of states]. - This role will also be eligible for equity and benefits. - Actual base pay will be determined based on permissible factors such as transferable skills, work experience, market demands, and primary work location. - The base pay range provided is subject to change and may be modified in the future. We need to include all that. The list of states is long; we should keep it. Schedule: Hybrid work info: - Hybrid Faire employees currently go into the office 3 days per week on Tuesdays, Thurs
- for lists.
We must not repeat job title. The job title is "Director, Global Equity". Not to be used as heading.
We must not include Job ID etc.
We must remove boilerplate: EEO, privacy, accommodation request, etc. Also remove "About Faire" intro? That's not under headings but we could include as part of About the role? Actually "About Faire" is company description; not needed per headings. Could we include it under About the role? The About the role section should contain the role description. The "About This Role" paragraph is appropriate. The earlier "About Faire" is company overview; could be omitted or maybe included in About the role as context? But instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company overview? It's substantive but not under any heading. Where to put? Could put as a