Sr. People Tech Analyst

We need to output HTML fragment with sections: headings

for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We need to parse the job posting. First, identify content: The posting includes a description about Block, then "The Role", then "In Your First Year", then bullet points under "You Will" (these are responsibilities), then "You Have" (requirements/qualifications), then "Preferred:" (skills/preferred qualifications), then benefits description, pay ranges, schedule? There's no explicit schedule. There's mention of remote work maybe? It says "Remote work, medical insurance, flexible time off, retirement savings plans, and modern family planning are just some of our offering." So benefits include remote work etc. Pay: they gave zone ranges. So we can include Pay section with those ranges. Benefits section: list benefits. Schedule: not mentioned explicitly; maybe not include. We need to avoid repeating job title as heading. No Job ID. We need to remove boilerplate: EEO, equal opportunity, scam warning, application instructions, privacy policy, etc. Also remove "While there is no specific deadline..." etc? That's maybe metadata but could be considered not substantive? It's about application timeline; maybe we can drop as it's not core. Also "Block takes a market-based approach to pay..." that's part of pay description; we can keep pay ranges. We need to preserve all substantive information. So we need to include the description about Block, the role description, responsibilities, requirements, qualifications, preferred skills, benefits, pay. We need to format using

headings and

• for lists,

  for prose. We need to decide sections: About the role (maybe includes the introductory paragraphs about Block and The Role). Responsibilities (the "You Will" bullet list). Requirements (the "You Have" minimum qualifications). Qualifications maybe same as Requirements? Could combine? But we need separate sections only if content. Could have Requirements and Qualifications separate? The posting lumps minimum qualifications under "You Have". Preferred qualifications under "Preferred:". Could treat "Requirements" as minimum qualifications, "Qualifications" as preferred? Or we could have "Requirements" for minimum, "Qualifications" for preferred. Or we could have "Skills" for preferred technical skills. Let's map: - About the role: introductory narrative (Block description, The Role, In Your First Year). Could be prose. - Responsibilities: bullet list under "You Will". - Requirements: minimum qualifications under "You Have" (the bullet list starting with Minimum of 5 years... etc). Could be list. - Qualifications: maybe the "Preferred:" bullet list (preferred qualifications). Could be list. - Skills: maybe we could extract specific skills from preferred list: AI-powered workflows, code queries, compliance/security understanding. Could be list but we already have Qualifications. - Benefits: list of benefits mentioned: Remote work, medical insurance, flexible time off, retirement savings plans, modern family planning, plus maybe other benefits? Also "Every benefit we offer is designed..." but we can list those. - Pay: the zone ranges. - Schedule: not present, omit. We must not create sections with filler like "commensurate with experience". We have actual pay ranges. We need to ensure we don't repeat content unnecessarily. Let's extract prose for About the role: From posting: "Block is one company built from many blocks, all united by the same purpose of economic empowerment. The blocks that form our foundational teams — People, Finance, Counsel, Hardware, Information Security, Platform Infrastructure Engineering, and more — provide support and guidance at the corporate level. They work across business groups and around the globe, spanning time zones and disciplines to develop inclusive People policies, forecast finances, give legal counsel, safeguard systems, nurture new initiatives, and more. Every challenge creates possibilities, and we need different perspectives to see them all. Bring yours to Block.The RoleThe People Technology team, part of the People Automation and Operations organization, manages the infrastructure powering Block's employee lifecycle from recruiting to off boarding. We're shifting from standard SaaS solutions to building scalable, secure platform infrastructure — data APIs, AI agents, and integration frameworks — so our People teams can build more.Reporting to the Head of People Technology, you'll start with Talent Acquisition as your first customer and broaden across the People portfolio from there.In Your First YearStart with Talent, build for the portfolio. You'll partner closely with Talent Acquisition on their most pressing technology needs while their strategy and org design come together — building solutions that hold up beyond that first customer.Automate recurring operational work, sustainably. A meaningful share of the work supporting our People stack repeats. You'll replace it with automation built to last — documented, maintainable, and designed as shared capability rather than one-off fixes.Make other builders faster. As teams across People build their own AI-enabled solutions, you'll give them the underpinnings: trusted data access, integration patterns, reusable tools and agents, and clear guidance on what's safe to build and what isn't." We need to format that as prose

  . Could split into paragraphs but one

  is fine. Now Responsibilities: bullet list under "You Will". Let's extract each bullet: - Talent Acquisition Partnership & Platform Strategy - Partner with Talent Acquisition and other People teams to understand business challenges and identify opportunities to improve work through technology and AI. - Advise teams as they evaluate and design AI-enabled solutions that are scalable, secure, and grounded in trusted People data. - Balance near-term delivery with longer-term platform investments that reduce duplication and speed up future development. - Platform Architecture & Integration Design - Build and enable shared integrations, data services, and platform automations that accelerate AI-powered solutions across the People organization. - Evaluate and manage People Technology vendors, weighing build, buy, and integration decisions. - Evolve People Technology toward consistent, shared platform capabilities and architectural patterns that empower builders across the organization. - AI, Automation & Innovation - Use AI and modern development tools to prototype, automate, and deliver technology solutions that improve the employee and candidate experience. - Partner with builders across the People organization so solutions draw on trusted data, follow governance standards, and are designed for maintainability and scale. - Evaluate emerging technologies and identify opportunities to improve productivity, employee experiences, and operational effectiveness. - Platform Operations & Governance - Steward our core People Platform, including systems of record such as Workday and Greenhouse, ensuring reliable, secure, and scalable operations. We can flatten into a single

  • list, each bullet as a sentence. Could keep subheadings but not needed. We'll just list each responsibility as
  • . Now Requirements (minimum qualifications) under "You Have": - Minimum of 5 years of related experience with a Bachelor's degree; or 3 years and a Master's degree; or a PhD without experience; or equivalent work experience. - Experience managing enterprise People platforms such as Workday, Greenhouse, or similar systems, including hands-on work designing or implementing integrations between them using APIs, middleware, ETL tools, or integration platforms. - Supported Recruiting or Talent Acquisition through technology, with working knowledge of how hiring runs — offer approvals, requisition and application flows, and the sourcing or assessment tools behind them. - Experimented with AI tools to automate work or build solutions, and can talk through what you tried, what you learned, and how you'd apply it to People Technology challenges. We're all learning, but you need to have started. - Led technology initiatives end-to-end — from discovery and requirements through implementation, change management, and adoption — simplifying complex business processes along the way. - Translate technical concepts for business stakeholders and business needs for technical audiences, and influence decisions across People, Security, Data, and Engineering teams. We'll list each as
  • . Now Qualifications (preferred): - Preferred: Built AI-powered workflows, agents, or applications using AI APIs, agent frameworks, or automation platforms — prototypes and side projects count. - Preferred: Written code or queries (Python, SQL, JavaScript) to automate workflows, manipulate data, or build integrations, using practices like source control, CI/CD, or Agile delivery. - Preferred: Understanding of compliance and security standards relevant to People data (SOX controls, GDPR, data classification frameworks, access controls). We'll list as
  • . Now Benefits: The 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." We can list benefits as
    • Remote work
    • Medical insurance
    • Flexible time off
    • Retirement savings plans
    • Modern family planning
    . Could also mention "Check out our other benefits at Block" but that's not a benefit; we can ignore. Now Pay: The zone ranges: Zone A:: $163,600 USD - $245,400 USD Zone B: : $152,200 USD - $228,200 USD Zone C:: $144,000 USD - $216,000 USD Zone D:: $135,800 USD - $203,600 USD We need to present as maybe a

    describing that pay varies by location, and list ranges. Could do

    • Zone A: $163,600 - $245,400 USD
    etc. We should not include the "Block takes a market-based approach to pay..." but we can keep a short sentence: "Pay is market-based and varies by location." That's substantive. Now ensure we don't include boilerplate: EEO, equal opportunity, arrest/conviction records, accommodations, I+D page, application guidelines, AI in hiring process, privacy policy, etc. Also remove "While there is no specific deadline to apply for this role, U.S. roles are typically open for an average of 55 days before being filled..." etc. That's not substantive? Could be considered metadata but maybe we drop. Also remove "Block, Inc. (NYSE: XYZ) builds technology..." that's boilerplate about company description; but we already used some of that in About the role? Actually the initial paragraph about Block is part of the posting; we kept that. The later paragraph about brands etc is extra; we can drop as it's not specific to role. Now produce HTML fragment:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    ...

    Qualifications

    ...

    Benefits

    ...

    Pay

    Pay is market-based and varies by location. The starting pay ranges are:

    • Zone A: $163,600 - $245,400 USD
    • Zone B: $152,200 - $228,200 USD
    • Zone C: $144,000 - $216,000 USD
    • Zone D: $135,800 - $203,600 USD
    We should not include Schedule. Check that we didn't repeat job title. Good. Now ensure we preserved all substantive information: Did we miss any? The "In Your First Year" bullet points we incorporated into responsibilities? Actually those are under "In Your First Year" which are more specific early-year goals. They could be considered responsibilities as well. We should include them. The "In Your First Year" includes three bullet points: Start with Talent..., Autom