Sr. People Tech Analyst
Block · Atlanta, GA · 1 mo ago
RemoteRemoteInformation Technology$164k/yrFull-time
We need to output HTML fragment with sections only when real content. Must not repeat job title. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content.
From posting: There's description about Block, then "The Role" etc. We need sections: About the role (maybe description of role). Responsibilities (list of duties). Requirements/Qualifications (experience). Skills maybe. Benefits (they mention benefits). Pay (they gave pay ranges). Schedule (not mentioned). So we should not include Schedule if no content.
We must not include boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines.
We need to preserve all substantive info.
Let's parse:
Company description: "Block is one company built from many blocks..." That's about company, maybe not needed? Could be part of About the role? Probably not needed; but we can include as part of About the role? The instruction: "Use
items.
From In Your First Year:
1. Start with Talent, build for the portfolio. 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.
2. 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.
3. 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.
From You Will (I'll break each bullet):
- 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.
- 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.
- 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.
- Steward our core People Platform, including systems of record such as Workday and Greenhouse, ensuring reliable, secure, and scalable operations.
That's many items; okay.
Now Requirements (mandatory):
- 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.
Now Qualifications (preferred):
- Built AI-powered workflows, agents, or applications using AI APIs, agent frameworks, or automation platforms — prototypes and side projects count.
- 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.
- Understanding of compliance and security standards relevant to People data (SOX controls, GDPR, data classification frameworks, access controls).
Now Benefits:
- Remote work
- Medical insurance
- Flexible time off
- Retirement savings plans
- Modern family planning
Now Pay:
We need to include the ranges exactly as given:
Zone A:: $163,600 USD - $245,400 USD
Zone B: : $152,200 USD - $228,200 USD
Zone C:: $144,000 USD -
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content.
From posting: There's description about Block, then "The Role" etc. We need sections: About the role (maybe description of role). Responsibilities (list of duties). Requirements/Qualifications (experience). Skills maybe. Benefits (they mention benefits). Pay (they gave pay ranges). Schedule (not mentioned). So we should not include Schedule if no content.
We must not include boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines.
We need to preserve all substantive info.
Let's parse:
Company description: "Block is one company built from many blocks..." That's about company, maybe not needed? Could be part of About the role? Probably not needed; but we can include as part of About the role? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have About the role section describing the role and maybe company context.
We need to avoid repeating job title (not given explicitly but role is People Technology Engineer? Actually title not shown). We'll not put title.
We need to include sections only if real content.
Let's extract:
About the role: The description after "The Role" and maybe first paragraph: "The 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."
That's good.
Responsibilities: The bullet list under "In Your First Year" and "You Will". Those are responsibilities.
Let's list them:
In Your First Year:
- Start with Talent, build for the portfolio. 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.
You Will (list):
- 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 combine these as responsibilities list.
Requirements/Qualifications: The "You Have" section.
List:
- 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.
Preferred:
- Built AI-powered workflows, agents, or applications using AI APIs, agent frameworks, or automation platforms — prototypes and side projects count.
- 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.
- Understanding of compliance and security standards relevant to People data (SOX controls, GDPR, data classification frameworks, access controls).
We could treat Requirements as mandatory, Qualifications as preferred? But headings list includes Requirements, Qualifications, Skills. We could put mandatory under Requirements, preferred under Qualifications, and maybe Skills separate? But we can combine.
Better: Use Requirements for mandatory, Qualifications for preferred, Skills maybe for technical skills (like Python, SQL, etc). But we already have those in preferred. Could split.
But instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section? But headings list separate; we can still include both if we have content.
We'll include Requirements (mandatory) and Qualifications (preferred). Skills maybe we can omit if covered.
Benefits: They have 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."
We can list benefits as bullet list: Remote work, medical insurance, flexible time off, retirement savings plans, modern family planning.
Pay: They gave pay ranges per zone. So we need Pay section with those ranges.
Schedule: Not mentioned, so omit.
We must not include boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines.
Now produce HTML fragment:
About the role
About the role
...
Responsibilities
- ... each responsibility as li
Requirements
- ... mandatory items
Qualifications
- ... preferred items
Benefits
- ... benefits
Pay
... pay ranges
We need to ensure no extra sections like Skills. Now craft content precisely, preserving all substantive info, not inventing. Let's write About the role paragraph: combine the two paragraphs. "The 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." That's fine. Now Responsibilities list items. Need to capture each bullet. I'll list them as separate