Jobs · Information Technology · California

Senior Data Analyst, People

Fivetran · Oakland, CA · 1 mo ago
HybridInformation Technology$156k–$195k/yrFull-time
We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We need to extract content. Let's parse the posting. We have: - About Us (but we should not repeat job title as heading; we can have "About the role"? Actually "About This Role" is present. So we can have heading "About the role" with content from "About This Role". That includes description of role. - Responsibilities: The bullet list under "What You’ll Do". That's responsibilities. - Requirements: Not explicitly labeled but there is "Skills We’re Looking For" which includes required skills/experience. Could treat as Requirements or Skills. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have "Skills We’re Looking For" which is a list of required skills. That could be under Skills heading. Also there is "Bonus Skills". Could be part of Skills or separate but we can include under Skills. We have "Technologies You’ll Use" which could be under Skills or maybe Qualifications. But we can include under Skills. We have "Pay": compensation range details: Oakland Pay Range $156,082—$195,102.50 USD. Also mention compensation range generally. So we can include Pay section. We have "Benefits": list under "Perks And Benefits". So Benefits section. We have "Schedule": mention "This is a full-time, flexible hybrid position based out of our Oakland, CA or NYC, NY office. Our hybrid work model offers a blend of remote flexibility and in-person collaboration. There is no mandate on the number of days required but we encourage employees to come in every week to collaborate." That's schedule info. So we can include Schedule. We have "Qualifications": maybe not separate; we could combine with Skills. But we could create a Qualifications heading for education/experience? The posting mentions "5+ years of experience in analytics, data science, business intelligence, or a related analytical role". That's a qualification. Could be under Qualifications. However we already have Skills heading for skill list. Might be okay to have both Qualifications and Skills. But we need to avoid thin sections. Let's see if we have enough content for each. Qualifications: could include education? Not explicitly. Only experience years. Could be minimal. Might be better to merge into Skills or Requirements. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one? But headings are prescribed; we can omit sections if no real specific content. So we could have: About the role, Responsibilities, Skills, Benefits, Pay, Schedule. Omit Requirements and Qualifications if we think content is covered elsewhere. But we need to ensure we preserve all substantive information. If we omit Requirements heading, we must still include the content somewhere else, perhaps under Skills or About the role. The "Skills We’re Looking For" includes experience requirement; that's substantive. So we can put that under Skills. Thus sections: - About the role: content from About This Role paragraph(s). Possibly also include the mission paragraph? The "About Us" is not about the role; but we could include under About the role? The instruction: About the role heading for section about the role. The "About This Role" is appropriate. We'll include that. - Responsibilities: list from "What You’ll Do". Use
  • . - Skills: include "Technologies You’ll Use", "Skills We’re Looking For", "Bonus Skills". Could be a combined list. - Benefits: list from "Perks And Benefits". - Pay: include compensation range details. - Schedule: include hybrid work model description. We must not include boilerplate like EEO, navigation, legal, etc. Remove duplicated lines. Now craft HTML. We need to use

    for each heading. Use

    for prose. Use

    • for lists. Let's extract precise text. About This Role: "We’re hiring a Senior Data Analyst to support our People organization, using data to help Fivetran attract, develop, engage, and retain exceptional talent as we scale. You’ll work across the employee lifecycle — from recruiting and workforce planning to employee experience, learning and development, performance, and retention — turning complex people data into insights that shape how we build and support our teams. This is a high-impact, highly cross-functional role for someone who enjoys operating at the intersection of data, people, and strategy. You’ll partner closely with leaders across People, Recruiting, Finance, and the broader business to answer important organizational questions, develop scalable analytical frameworks, and improve how decisions are made. This is a full-time, flexible hybrid position based out of our Oakland, CA or NYC, NY office. Our hybrid work model offers a blend of remote flexibility and in-person collaboration. There is no mandate on the number of days required but we encourage employees to come in every week to collaborate." Note: The last two sentences about hybrid position could be moved to Schedule section, but they are also part of About This Role. However we might want to avoid duplication. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we move hybrid details to Schedule, we still preserve them. It's okay to relocate content as long as we keep it. But we must not duplicate. We'll keep hybrid details in Schedule section, and maybe keep a brief mention in About the role? To avoid duplication, we could keep only the role description without the hybrid details, and put hybrid details in Schedule. However the About This Role paragraph includes that sentence; if we remove it, we are omitting that detail unless we put it elsewhere. We'll put it in Schedule. So About the role will exclude the hybrid sentences. Thus About the role paragraph: "We’re hiring a Senior Data Analyst to support our People organization, using data to help Fivetran attract, develop, engage, and retain exceptional talent as we scale. You’ll work across the employee lifecycle — from recruiting and workforce planning to employee experience, learning and development, performance, and retention — turning complex people data into insights that shape how we build and support our teams. This is a high-impact, highly cross-functional role for someone who enjoys operating at the intersection of data, people, and strategy. You’ll partner closely with leaders across People, Recruiting, Finance, and the broader business to answer important organizational questions, develop scalable analytical frameworks, and improve how decisions are made." Now Responsibilities: list from "What You’ll Do". Let's extract each bullet: - Define and own our core People metrics. Establish clear definitions and reporting across areas such as headcount, hiring, retention, organizational health, employee experience, and talent development. - Build scalable analytical products. Create canonical datasets, models, and self-service tools and dashboards that enable People teams and leaders to answer important questions quickly and consistently. - Serve as a trusted thought partner. Translate analyses into clear narratives and recommendations for audiences ranging from functional operators to senior executive leadership. - Work closely with our Engineers to improve Fivetran's own HRIS and ATS connectors. - Set a high bar for responsible People Analytics. Help establish strong practices around data quality, integrity, governance, privacy, appropriate access, and the responsible use of sensitive employee data. - Turn people data into decisions. Analyze complex and disparate datasets to identify trends, surface opportunities, and provide actionable recommendations to People leaders and business stakeholders. - Shape our analytics culture. Mentor other analysts and partners, establish analytical best practices, and help People teams develop stronger data fluency and decision-making habits. We'll put each as
    • . Skills: combine Technologies You’ll Use, Skills We’re Looking For, Bonus Skills. Technologies You’ll Use: list: SQL (BigQuery / Snowflake), dbt / dbt State, Looker / LookML, Sigma / Hex / Google Sheets, Claude Code / Codex, HRIS, ATS, and other People systems and data sources. We need to keep as list items. Skills We’re Looking For: list: - 5+ years of experience in analytics, data science, business intelligence, or a related analytical role - Advanced proficiency in SQL and data modeling, with experience working across large, complex datasets - Experience using Looker, Tableau, Sigma, or similar business intelligence and visualization tools - Strong analytical judgment and a track record of translating ambiguous business questions into structured analyses and actionable recommendations - Exceptional attention to detail and a high bar for data quality, analytical rigor, and reproducibility - Excellent communication and data storytelling skills; you can make complex findings intuitive and help decision-makers understand not just what is happening, but why it matters and what to do next - Comfort operating in ambiguity, developing hypotheses, and owning analytical problems end-to-end - Strong cross-functional instincts and the ability to build trusted relationships with both technical and non-technical partners - A builder mindset: you look beyond answering one-off questions and create frameworks, datasets, and tools that make future decisions faster and better - Passion for using data to improve how organizations attract, develop, and support their people - Experience using analytics to support key business decisions, preferably at a high-growth, SaaS, or B2B product company Bonus Skills: - Experience in People Analytics, workforce analytics, recruiting analytics, HR strategy, or another People-related analytical function - Familiarity with HRIS, ATS, performance management, engagement, or learning systems We'll combine all into a single
        under Skills heading. Benefits: list from "Perks And Benefits". Let's extract: - 100% employer-paid medical insurance - Generous paid time-off policy (PTO), plus paid sick time, inclusive parental leave policy, holidays (including a year end Global Week of Rest), and volunteer days off - RSU stock grants* - Professional development and training opportunities - Company virtual happy hours, free food, and fun team-building activities - Monthly cell phone stipend - Access to an innovative mental health support platform that offers personalized care and resources in areas such as: therapy, coaching, and self-guided mindfulness exercises for all covered employees and their covered dependents. - *May vary by country and worker type - please reach out to your recruiter for more information We should keep the note about RSU stock grants* and the footnote. Keep as list items. Pay: include compensation range details: "Oakland Pay Range $156,082—$195,102.50 USD". Also earlier generic statement about compensation range. We'll include both maybe as a paragraph. Schedule: include hybrid work model description: "This is a full-time, flexible hybrid position based out of our Oakland, CA or NYC, NY office. Our hybrid work model offers a blend of remote flexibility and in-person collaboration. There is no mandate on the number of days required but we encourage employees to come in every week to collaborate." We should ensure we didn't miss any other substantive info: The "About Us" paragraph about mission and dbt labs etc. That's not about the role; but could be considered "About the company". Not required heading. We could omit as not requested. The instruction: use headings only for those sections; we can omit About Us. It's not required to include. So we can leave it out. Also there is statement about valuation, core values, diversity etc. That's boilerplate/EEO? It's not EEO but could be considered culture. Might be considered not required. We can omit as not under headings. Now produce HTML. We need to output only HTML fragment, no /, no markdown. Let's craft:

        About the role

        ...

        Responsibilities

        • ...
        • ...

        Skills

        • ...
        • ...

        Benefits

        • ...
        • ...

        Pay

        O

Similar jobs

Senior Data Engineer

RemoteHunterUnited States· 1 mo ago
RemoteEngineering$165k/yrapply on remotehunter.com

Senior Data Engineer

ParamountLos Angeles, CA· 1 mo ago
RemoteInformation Technology$110k–$166k/yrapply on careers.paramount.com

Senior Data Engineer

SpyCloudAustin, TX· 3 mo ago
Information Technology$144k–$187k/yrapply on grnh.se

Senior Data Engineer

ChartmetricNew York, NY· 3 mo ago
Information Technologyapply on ats.rippling.com