Financial Analyst

We need to output HTML fragment with sections: About the role, Responsibilities (What You'll Do), Requirements (What We Are Looking For), maybe Qualifications? The posting includes "About The Role", "What You'll Do", "What We Are Looking For", "You’ll Likely Stand Out If You Have", "How We Work", "How We Invest In You", "Come Work With Us!". We need to include sections only when there is real specific content. We must not include Pay, Schedule, Benefits unless stated. There's no explicit pay, schedule, benefits. There's mention of "Equity Compensation: ownership aligned with your impact and the company's growth" and "We offer an L&D budget". That's benefits? It's compensation & ownership. Could be considered Benefits? The rule: include Pay/Schedule/Benefits sections only if posting actually states them. It does mention equity compensation and L&D budget, which are benefits/compensation. So we could include a Benefits section with that content. However we need to see if we should treat "Compensation & Ownership" as a Benefits section. The rule says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Benefits heading if there is content. The posting includes "How We Invest In You" which includes "Compensation & Ownership Equity Compensation: ownership aligned with your impact and the company's growth We offer an L&D budget to support your growth and real internal mobility". That's benefits. So we can include a Benefits section. We also have "How We Work" describing culture; could be considered "About the role"? Already have About the role. Could be a separate section like "Culture" but not in allowed headings. Probably we should not create extra headings not listed. So we should incorporate that content into existing sections maybe under About the role or maybe under Responsibilities? But we must preserve all substantive information; we cannot drop it. We could include it under a section like "About the role" or maybe under a generic

after sections? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It implies we should use those headings when appropriate. It doesn't say we cannot add other headings, but better to stick to those. However we have substantive content about "How We Work" and "How We Invest In You" and "Come Work With Us!". Could we treat them as part of "About the role"? Might be okay to add a section like "Culture" but not in list. Safer to incorporate them into existing sections: maybe under "About the role" we can include description of role and also how we work? But that might mix. Alternatively we could create sections: About the role, Responsibilities, Requirements, Benefits, and then include extra paragraphs after those sections without headings? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It doesn't forbid stray

elements not under headings. So we could output:

About the role

... (the About The Role paragraph)

Responsibilities

• ... each bullet from What You'll Do

Requirements

• ... each bullet from What We Are Looking For

Benefits

... (Compensation & Ownership, L&D budget)

Then we could add extra paragraphs for How We Work, Come Work With Us, etc. But those are substantive; we need to preserve them. Could we add them under a generic

after Benefits? That would preserve info. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can combine How We Work and Come Work With Us into a section like "About the company" but not allowed heading. Could we put them under About the role? Might be okay to extend About the role paragraph to include those details. However About the role currently is a short paragraph; we could expand it with the culture description. That would preserve all info. Let's extract the content: About The Role paragraph: "The FP&A Analyst is an individual contributor on Hiya's Finance team, owning the forecasting models, OPEX budgeting and actuals reporting, and company-wide dashboards that leadership uses to make decisions. You'll partner closely with department leads across GTM, Product, Engineering, and People to keep planning accurate and aligned, and you'll help set the standard for how Finance uses AI to work faster and think more clearly." We could add after that: "Hiya is not a passive environment. We expect people to take ownership, form opinions, and engage directly with hard problems. We work with a high degree of transparency and autonomy. Context is shared openly, and decisions are discussed, challenged, and then made. Once a call is made, we commit and move forward. You'll be expected to work through ambiguity, weigh tradeoffs, and take responsibility for results, while keeping a high bar for quality and customer trust. Every team member at Hiya is expected to live our core values: Serve, our customers and partners by holding a high bar for trust and quality; Own, share in success and open up to failures; Lead, listen, show up with a point of view but commit entirely once a decision has been made; Improve, even if it means changing course or contradicting ourselves; Do, rather than observe." Then "How We Invest In You" paragraph: "Compensation & Ownership Equity Compensation: ownership aligned with your impact and the company's growth We offer an L&D budget to support your growth and real internal mobility so career pathing isn't just a talking point — because we're building this with people who own the outcome." Then "Come Work With Us!" paragraph: "We're building a team with diverse perspectives, identities, and professional experiences. We evaluate candidates through a business lens and believe that diversity and unique viewpoints make our company stronger, more dynamic, and a great place to build a career. We've been recognized by Built In, GeekWire, Comparably, G2, Forbes, and Deloitte Technology Fast 500 for our culture, innovation, leadership, compensation, and more. At Hiya, we're a people-centric company focused on helping each employee grow both personally and professionally. We create a culture of support and empowerment that challenges the status quo, resulting in an energized team that's passionate about their work. You'll love working here if you're looking for an innovative challenge that's disrupting an industry. Come join us!" We could combine these into About the role or maybe a separate section like "About Hiya" but we already have an initial "About Hiya" paragraph at top. Actually the posting starts with "About Hiya" paragraph describing the company. That could be used as About the company section. But we are not supposed to repeat job title as heading; we can have About Hiya as a section? The allowed headings include About the role, not About Hiya. But we could treat that as part of About the role? Might be weird. Better to keep About Hiya as a

before the headings, as introductory content. That's allowed: we can have prose

not under heading. Then we have headings for About the role, Responsibilities, Requirements, Benefits. Thus we will output:

About Hiya: ... (the About Hiya paragraph)

About the role

The FP&A Analyst is an individual contributor on Hiya's Finance team, owning the forecasting models, OPEX budgeting and actuals reporting, and company-wide dashboards that leadership uses to make decisions. You'll partner closely with department leads across GTM, Product, Engineering, and People to keep planning accurate and aligned, and you'll help set the standard for how Finance uses AI to work faster and think more clearly. Hiya is not a passive environment. We expect people to take ownership, form opinions, and engage directly with hard problems. We work with a high degree of transparency and autonomy. Context is shared openly, and decisions are discussed, challenged, and then made. Once a call is made, we commit and move forward. You'll be expected to work through ambiguity, weigh tradeoffs, and take responsibility for results, while keeping a high bar for quality and customer trust. Every team member at Hiya is expected to live our core values: Serve, our customers and partners by holding a high bar for trust and quality; Own, share in success and open up to failures; Lead, listen, show up with a point of view but commit entirely once a decision has been made; Improve, even if it means changing course or contradicting ourselves; Do, rather than observe.

Responsibilities

• Build and maintain financial models for forecasting and scenario analysis, using AI tools to speed up model-building and QA
• Own OPEX budgeting and actuals reporting, including monthly variance reviews and cross-functional partnering with business leaders
• Own company-wide dashboards, including key SaaS metrics, AI adoption/ROI, and GTM ROI analysis
• Support headcount planning with People and department leads
• Conduct ad hoc analysis for strategic initiatives and leadership decisions
• Identify opportunities to apply AI and automation across reporting, forecasting, and analysis, helping build a culture of thoughtful AI adoption in Finance

Requirements

• Bachelor's degree in Finance, Economics, Business, Math, or related field
• 1-2 years in an analytical role (internships and strong academic projects count)
• Strong Excel/Google Sheets skills, with hands-on financial modeling and dashboard experience
• Daily user of AI tools (e.g. Claude, ChatGPT), with the judgment to know when to trust AI output and when to double-check it
• Solid grasp of budgeting, forecasting, and variance analysis
• Ability to synthesize large data sets into clear, actionable insights and communicate them to non-finance stakeholders

Benefits

Compensation & Ownership: Equity compensation aligned with your impact and the company's growth. We offer an L&D budget to support your growth and real internal mobility so career pathing isn't just a talking point — because we're building this with people who own the outcome.

We also need to include the "Come Work With Us!" content. Could add another

after Benefits: maybe under a heading like "About the company"? Not allowed. Could add another

without heading. That would preserve info. The instruction: "Prefer a few substantive sections over many thin ones." Adding a stray paragraph may be okay. But we could incorporate that content into Benefits or About the role. Perhaps we can add it to Benefits paragraph as extra sentences. Let's append to Benefits paragraph: after the L&D budget sentence, add: "We're building a team with diverse perspectives, identities, and professional experiences. We evaluate candidates through a business lens and believe that diversity and unique viewpoints make our company stronger, more dynamic, and a great place to build a career. We've been recognized by Built In, GeekWire, Comparably, G2, Forbes, and Deloitte Technology Fast 500 for our culture, innovation, leadership, compensation, and more. At Hiya, we're a people-centric company focused on helping each employee grow both personally and professionally. We create a culture of support and empowerment that challenges the status quo, resulting in an energized team that's passionate about their work. You'll love working here if you're looking for an innovative challenge that's disrupting an industry. Come join us!" That preserves all. Now check for any boilerplate to remove: The posting includes "Hiya is an equal opportunity employer.