Jobs · Information Technology

Risk Data Analyst, Staff

BILL · California, United States · 3 wk ago
RemoteRemoteInformation Technology$159k–$191k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about company, then "Make Your Impact Within a Rapidly Growing Fintech Company" then description. We need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse content: - About the role: likely the paragraph after "Make Your Impact Within a Rapidly Growing Fintech Company" describing the role: "We are seeking an experienced Risk Data Analyst to join the Risk Portfolio Management team. This team develops data-driven strategies and insights that strengthen BILL’s risk operations and protect the integrity of its payment platform. In this role, you will build data models, analyze risk trends, and deliver actionable insights that support the detection and prevention of fraudulent transactions—helping protect BILL’s customers while enabling safe, trusted growth." That's about the role. - Responsibilities: list bullet points under "Responsibilities". The posting shows: Responsibilities Consolidate data from multiple source systems into complete, accurate, and consistent Risk Operations data models Create intuitive, actionable, and automated reports and Tableau dashboards Synthesize and present data into actionable insights and data stories that drive incremental value for BILL, the Risk Operations team, and BILL’s customers Develop strong partnership and collaboration with Risk Operations leaders Gather requirements, prioritize requests, and manage analytics roadmap for Risk Operations team So we need
  • for each. - Requirements: The posting has "We’d Love To Chat If You Have" then bullet list of qualifications: Bachelor's degree..., 8 years experience..., etc. That's requirements. - Qualifications: Might be overlapping with requirements; but we can treat the bullet list as Requirements. Could also have Qualifications separate? The posting includes "Experience working with data generated from fraud and risk platforms..." etc. Those are also qualifications. Might combine into Requirements. But we need to follow instruction: Use headings only when posting has real specific content for it. We have content for Requirements (the bullet list). We could also have Skills (maybe list of specific skills: SQL pipelines, dbt, Tableau, etc). The bullet list includes many skill items. Could separate Skills section. But we need to avoid thin sections. Perhaps combine Requirements and Skills into one Requirements section? However instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose to include Requirements and Skills if content exists. Let's extract: Requirements (education/experience): - Bachelor's degree in Math, Statistics, Economics, or another technical field - 8 years of experience in analytics and/or data science (or 5+ years of experience w/ Master’s Degree) - Extensive experience and advanced knowledge of engineering SQL pipelines (dbt experience a huge plus) - Proficiency in business intelligence tools for dashboard and report creation, preferably Tableau - Proven ability to synthesize data into actionable insights and present data stories to business leaders - Experience working with data generated from fraud and risk platforms (e.g. DataVisor, etc.) as well as CRM platforms (Salesforce, Zendesk, etc.) - Hands-on experience using terminal-based AI tools (specifically Claude Code CLI) to accelerate dbt/Dataform pipeline development for fraud strategy, compliance monitoring, loss forecasting models, and executive KPI reporting. - Leverage Claude Cowork/Code to automate repetitive analytics tasks—from drafting SQL documentation and dbt model summaries to generating first drafts of risk insight narratives—so you spend more time on high-impact analysis and less on documentation overhead That's a mix of skills and experience. Qualifications maybe not separate. Skills: Could list specific technical skills: SQL, dbt, Tableau, etc. But that duplicates. Better to have Requirements (education/experience) and Skills (technical). Let's extract skills: SQL pipelines, dbt, Tableau, business intelligence tools, terminal-based AI tools (Claude Code CLI), etc. But we can also combine. Pay: The posting includes salary ranges per zone. That's specific content. So we need a Pay section with that info. Benefits: The posting includes benefits list under "What’s in it for you?" and also earlier "competitive benefits package that includes: medical, dental, vision, life and disability insurance, 401(k) retirement plan, flexible spending & health savings account, paid holidays, paid time off, and other company benefits." Then later list of benefits: 100% paid employee health, dental, and vision plans (choose HMO, PPO, or HDHP) HSA & FSA accounts Life Insurance, Long & Short-term disability coverage Employee Assistance Program (EAP) 11+ Observed holidays and wellness days and flexible time off Employee Stock Purchase Program with employee discounts Wellness & Fitness initiatives Employee recognition and referral programs And much more Thus we have Benefits content. Schedule: Not mentioned explicitly; remote-first, office spaces in San Jose, CA and Draper, UT — opportunities to connect in person when it counts. That's about work location, not schedule. No explicit schedule (full-time, hours). So we should not create Schedule section. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We need to ensure we don't repeat job title as heading. Not include Job ID. We need to output only HTML fragment. We'll wrap each section in appropriate tags:

    Heading

    then content: either

    for prose or

    • for lists. For About the role: prose

      . Responsibilities:

      • each. Requirements: maybe
        • each bullet. Skills: maybe
          • each skill. Benefits: Could be
            • each benefit. Pay: Could be

              with salary ranges. Let's extract exact text preserving all substantive information, not inventing. We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to copy the text exactly as in posting (maybe minor formatting). Ensure we don't omit any bullet. Let's list responsibilities exactly: - Consolidate data from multiple source systems into complete, accurate, and consistent Risk Operations data models - Create intuitive, actionable, and automated reports and Tableau dashboards - Synthesize and present data into actionable insights and data stories that drive incremental value for BILL, the Risk Operations team, and BILL’s customers - Develop strong partnership and collaboration with Risk Operations leaders - Gather requirements, prioritize requests, and manage analytics roadmap for Risk Operations team Now requirements/experience bullets: - Bachelor's degree in Math, Statistics, Economics, or another technical field - 8 years of experience in analytics and/or data science (or 5+ years of experience w/ Master’s Degree) - Extensive experience and advanced knowledge of engineering SQL pipelines (dbt experience a huge plus) - Proficiency in business intelligence tools for dashboard and report creation, preferably Tableau - Proven ability to synthesize data into actionable insights and present data stories to business leaders - Experience working with data generated from fraud and risk platforms (e.g. DataVisor, etc.) as well as CRM platforms (Salesforce, Zendesk, etc.) - Hands-on experience using terminal-based AI tools (specifically Claude Code CLI) to accelerate dbt/Dataform pipeline development for fraud strategy, compliance monitoring, loss forecasting models, and executive KPI reporting. - Leverage Claude Cowork/Code to automate repetitive analytics tasks—from drafting SQL documentation and dbt model summaries to generating first drafts of risk insight narratives—so you spend more time on high-impact analysis and less on documentation overhead Now skills: maybe we can extract distinct technical skills: SQL pipelines, dbt, Tableau, business intelligence tools, terminal-based AI tools (Claude Code CLI), etc. But to avoid duplication, maybe we don't need Skills section; we could put all under Requirements. However instruction says prefer a few substantive sections over many thin ones. Having both Requirements and Skills may be thin if we split. Better to have one Requirements section covering education, experience, and skills. That seems acceptable. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. Now Benefits: need to list all benefits mentioned. First paragraph: "competitive benefits package that includes: medical, dental, vision, life and disability insurance, 401(k) retirement plan, flexible spending & health savings account, paid holidays, paid time off, and other company benefits." Then later list: "100% paid employee health, dental, and vision plans (choose HMO, PPO, or HDHP) HSA & FSA accounts Life Insurance, Long & Short-term disability coverage Employee Assistance Program (EAP) 11+ Observed holidays and wellness days and flexible time off Employee Stock Purchase Program with employee discounts Wellness & Fitness initiatives Employee recognition and referral programs And much more" We need to preserve all substantive information; we can combine into a list without duplication. Let's create a list of benefits: - Medical, dental, vision insurance - Life and disability insurance - 401(k) retirement plan - Flexible spending & health savings account (FSA & HSA) - Paid holidays - Paid time off - 100% paid employee health, dental, and vision plans (choose HMO, PPO, or HDHP) (maybe redundant with medical/dental/vision) - HSA & FSA accounts (already) - Life Insurance (already) - Long & Short-term disability coverage (already) - Employee Assistance Program (EAP) - 11+ Observed holidays and wellness days and flexible time off (maybe redundant with paid holidays and PTO) - Employee Stock Purchase Program with employee discounts - Wellness & Fitness initiatives - Employee recognition and referral programs - Other company benefits (mentioned) We should avoid duplication but preserve all info. Could list each distinct benefit as separate line, even if some overlap. Let's produce list: - Medical insurance - Dental insurance - Vision insurance - Life insurance - Disability insurance (short-term and long-term) - 401(k) retirement plan - Flexible spending account (FSA) - Health savings account (HSA) - Paid holidays - Paid time off - 100% paid employee health, dental, and vision plans (choose HMO, PPO, or HDHP) (maybe note it's 100% paid) - Employee Assistance Program (EAP) - 11+ Observed holidays and wellness days - Flexible time off (maybe already) - Employee Stock Purchase Program with employee discounts - Wellness & Fitness initiatives - Employee recognition and referral programs - Other company benefits But we may be over-splitting. However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep each piece of info. Overlap may be okay but we should not lose any detail. Simplify: we can keep two paragraphs: one for the competitive benefits package, another for the preview of amazing benefits. That preserves info without splitting. Use

              for prose. That may be acceptable. Thus Benefits section: two

              paragraphs. Pay: we need to include salary ranges per zone. Text: "Our ranges for each role and job level are based on a variety of factors including candidate experience, expertise, and geographic location and may vary from the amounts listed below. The role is also eligible for a competitive benefits package that includes: medical, dental, vision, life and disability insurance, 401(k) retirement plan, flexible spending & health savings account, paid holidays, paid time off, and other company benefits. The estimated salary ranges noted below roles in the specific geographic zones Zone 1: San Francisco Bay Area CA (includes HQ), New York City, Seattle, Los Angeles County $159,200—$191,052 USD Zone 2: CA (Non San Francisco Bay Area and Los Angeles County), Austin TX, Massachusetts $143,300—$171,900 USD Zone 3:

Similar jobs

Risk Data Analyst

RemoteHunterUnited States· 3 mo ago
RemoteFinanceapply on remotehunter.com