We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also must not include sections with filler like "commensurate with experience". Pay: we have pay ranges for zones. The posting includes pay ranges: Zone A: ($155,445 - $233,168) etc. It says "Amounts listed above include target variable compensation." So we have pay info. Should we include Pay section? Yes, because posting states pay ranges. However we need to consider that we need to map location: Baltimore, MD. Need to determine zone? Not given directly; we could infer but we shouldn't guess. The posting includes zone table but not which zone Baltimore falls under. We could still include Pay section with the zone table? But that might be considered not specific to the role? It says "Block takes a market-based approach to pay, and pay may vary depending on your location. U.S. locations are categorized into one of four zones based on a cost of labor index for that geographic area. The successful candidate's starting pay will be determined based on job-related skills, experience, qualifications, work location, and market conditions. These ranges may be modified in the future. To find a location's zone designation, please refer to this resource. If a location of interest is not listed, please speak with a recruiter for additional information. Zone A: ($155,445 - $233,168) Zone B: ($144,560 - $216,874) Zone C: ($136,794 - $205,226) Zone D: ($128,960 - $193,440) Amounts listed above include target variable compensation."
Thus we have pay ranges but not specific to Baltimore. However it's still substantive pay info. We can include Pay section with that info. It's not filler. It's specific numbers.
Schedule: Not mentioned explicitly. There's mention of spending ~80% of week in field, but not schedule like full-time, etc. Not explicit schedule. So we should not create Schedule section.
Benefits: The posting includes a paragraph: "Every benefit we offer is designed with one goal: empowering you to do the best work of your career while building the life you want. Remote work, medical insurance, flexible time off, retirement savings plans, and modern family planning are just some of our offering. Check out our other benefits at Block." That's benefits info. So we can include Benefits section with that list.
Now we need sections: About the role (intro paragraph), Responsibilities (the "You will:" list), Requirements (the "You have:" list), Qualifications? Might be overlapping with Requirements. The posting includes "You have:" which are requirements. Also "Even better:" which are preferred qualifications. Could treat "You have:" as Requirements, and "Even better:" as Qualifications or Skills? The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content.
We have:
- About the role: introductory paragraphs before "You will:" maybe the first few paragraphs describing role, mission, etc.
- Responsibilities: the "You will:" bullet list.
- Requirements: the "You have:" list (mandatory).
- Qualifications: maybe the "Even better:" list (preferred). Could also be Skills: but we have some skill-like items: payment processing experience, audience experience. Those could be Skills.
Better to split: Requirements = mandatory (3+ years sales experience, etc). Qualifications = preferred (2+ years payment processing OR related tech, 1+ years relevant audience experience). Skills could be things like Salesforce experience, collaborative mentality, reliable transportation, etc. But those are also in Requirements. Actually "You have:" includes: 3+ years sales experience, experience exceeding targets, ability to drive deals independently, business development experience, reliable transportation, collaborative mentality, prior Salesforce experience. Those are requirements/qualifications. The "Even better:" are preferred qualifications.
We could treat:
- Requirements: mandatory items.
- Qualifications: preferred items.
- Skills: maybe we could list specific skills like "Salesforce", "payment processing", "loyalty, time management", "restaurants, retailers, services". But those are already in qualifications.
Given instruction to prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one "Requirements" section, but we need to follow headings list; we can omit Qualifications if not needed. However we have content for both mandatory and preferred; we could put all under Requirements, but then we lose distinction. Might be okay.
Alternatively we could have Requirements (mandatory) and Skills (preferred). But the "Even better:" includes payment processing, audience experience - those are skills/experience.
Let's decide:
- About the role: intro paragraphs.
- Responsibilities: "You will:" list.
- Requirements: "You have:" list (mandatory).
- Skills: "Even better:" list (preferred).
- Benefits: benefits paragraph.
- Pay: pay zone table.
We should not include Schedule.
Now we need to format lists as
- . For prose, use
.
We must not repeat job title as heading. So no heading for Territory Account Executive.
We must not include Job ID etc.
We must remove boilerplate: the opening paragraphs about Square history etc. That's actually part of About the role? It's generic company description. Might be considered boilerplate but it's substantive about Square's mission. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The opening company description is not necessarily boilerplate; it's about Square's mission and could be relevant to About the role. We'll keep it as part of About the role.
We also need to remove duplicated lines: there may be duplicated sentences? Not seeing.
Now produce HTML fragment.
Structure:
About the role
... (intro paragraphs)
Responsibilities
- Lead your market with disciplined, in-person execution
- Spend ~80% of your week in the field — walking your territory, engaging local businesses, and driving 50–60 targeted business visits each week.
- Run a full-cycle, self-sourced sales motion: generate leads, identify needs, deliver compelling demos, and close deals across Square’s full product suite.
- Establish yourself as the go-to Square expert in your city
- Build strong, trust-based relationships with local sellers by being present, reliable, and value-driven.
- Partner cross-functionally to ensure a seamless onboarding experience and fast time-to-value for new sellers.
- Implement a disciplined referral strategy to turn every new customer into future opportunities.
- Build a high-velocity pipeline from the ground up
- Develop a repeatable top-of-funnel engine through door-to-door outreach, community engagement, events, networking, and targeted partnerships.
- Work with channel partners to generate a consistent, high-quality referral stream that grows over time.
- Master your verticals and sell with precision
- Build deep expertise in key verticals — including restaurants, retail, and services — to diagnose challenges and position the right Square solutions.
- Sell consultatively and competitively, staying proactive and strategic throughout the sales cycle.
- Achieve exceptional results in a high-accountability environment
- Maintain strong operational rigor in Salesforce: track activity, manage pipeline, and forecast accurately.
- Measure performance frequently and improve continuously.
- Consistently exceed quota within a culture where high standards are the norm.
But note some items are duplicated or overlapping; we need to preserve all substantive info but not duplicate lines. The "You will:" list includes bullet points each starting with a bold phrase? Actually the text: "You will:Lead your market with disciplined, in-person executionSpend ~80% of your week in the field — walking your territory, engaging local businesses, and driving 50–60 targeted business visits each week.Run a full-cycle, self-sourced sales motion: generate leads, identify needs, deliver compelling demos, and close deals across Square’s full product suite.Establish yourself as the go-to Square expert in your cityBuild strong, trust-based relationships with local sellers by being present, reliable, and value-driven.Partner cross-functionally to ensure a seamless onboarding experience and fast time-to-value for new sellers.Implement a disciplined referral strategy to turn every new customer into future opportunities.Build a high-velocity pipeline from the ground upDevelop a repeatable top-of-funnel engine through door-to-door outreach, community engagement, events, networking, and targeted partnerships.Work with channel partners to generate a consistent, high-quality referral stream that grows over time.Master your verticals and sell with precisionBuild deep expertise in key verticals — including restaurants, retail, and services — to diagnose challenges and position the right Square solutions.Sell consultatively and competitively, staying proactive and strategic throughout the sales cycle.Achieve exceptional results in a high-accountability environmentMaintain strong operational rigor in Salesforce: track activity, manage pipeline, and forecast accurately.Measure performance frequently and improve continuously.Consistently exceed quota within a culture where high standards are the norm."
We need to split into logical bullets. The above splitting is okay but we may have some redundancy: "Build a high-velocity pipeline from the ground up" and then "Develop a repeatable top-of-funnel engine..." are separate bullet points. That's fine.
Now Requirements:
Requirements
- 3+ years of sales experience in a full cycle closing role with field sales experience
- Experience exceeding sales targets, selling a diverse ecosystem of products, and closing complex deals
- Ability to drive deals independently in a fast-paced, dynamic environment
- Business development experience (e.g. hunting and cold calling)
- Since this is a field position, you must have reliable transportation and live in the market you are serving
- A collaborative and team player mentality
- Prior Salesforce experience or equivalent
Now Skills (preferred):
Skills
- 2+ years of payment processing OR related technology (i.e. payroll, loyalty, time management)
- 1+ years of relevant audience experience (experience working in/selling to restaurants, retailers or services based businesses)
Now Benefits:
Benefits
Every benefit we offer is designed with one goal: empowering you to do the best work of your career while building the life you want. Remote work, medical insurance, flexible time off, retirement savings plans, and modern family planning are just some of our offering.
Now Pay:
Pay
Block takes a market-based approach to pay, and pay may vary depending on your location. U.S. locations are categorized into one of four zones based on a cost of labor index for that geographic area. The successful candidate's starting pay will be determined based on job-related skills, experience, qualifications, work location, and market conditions. These ranges may be modified in the future. To find a location's zone designation, please refer to this resource. If a location of interest is not listed, please speak with a recruiter for additional information. Zone A: ($155,445 - $233,168) Zone B: ($144,560 - $216,874)