Senior Data Analyst, Strategic Finance
Vanta · United States · 1 mo ago
RemoteRemoteInformation TechnologyFull-time
We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID. Must remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Content:
- Intro paragraph about Vanta mission, team, role description: "As a Senior Data Analyst on the Finance team, you’ll play a pivotal role..." This is about the role. Could go under About the role.
- Then "What you’ll do as a Senior Data Analyst at Vanta:" bullet list of duties.
- Then "How to be successful in this role:" with subheadings: Experience, Technical Skills, Analytical Thinking, Collaboration, Communication, Education, Must be authorized to work in the U.S., Open to using AI...
These are requirements/qualifications/skills. We need to map to sections: Requirements, Qualifications, Skills. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which content goes where.
We have:
- About the role: description of role, mission, impact.
- Responsibilities: the bullet list under "What you’ll do..."
- Requirements: maybe experience, education, work authorization.
- Qualifications: maybe technical skills, analytical thinking, collaboration, communication.
- Skills: maybe specific technical skills (SQL, Tableau, etc.) but we already have technical skills.
But we need to avoid duplication. Could combine.
Better: Use sections:
- About the role: intro paragraph.
- Responsibilities: bullet list of duties.
- Requirements: Experience (4+ years), Education (Bachelor’s degree), Work authorization (must be authorized to work in US), Open to using AI (maybe as a trait).
- Qualifications: Technical Skills (SQL, data visualization, DBT, Python), Analytical Thinking, Collaboration, Communication.
- Skills: maybe we could combine technical skills into Skills, but we already have Qualifications. The instruction says we can have both Qualifications and Skills sections if content exists. We could put technical skills under Skills, and analytical thinking etc under Qualifications. Or we could put all under Qualifications and leave Skills empty (but we must not emit empty sections). So we need to decide.
Let's assign:
- Skills: Technical Skills (SQL, Tableau/Sigma, DBT, Python).
- Qualifications: Analytical Thinking, Collaboration, Communication, Experience, Education, Work authorization, AI usage.
But Experience and Education are more like requirements. Could put them under Requirements.
Thus:
- Requirements: Experience (4+ years), Education (Bachelor’s degree in related field), Must be authorized to work in the U.S., Open to using AI to amplify their skills.
- Qualifications: Analytical Thinking, Collaboration, Communication.
- Skills: Technical Skills (SQL, data visualization tools, DBT, Python).
Now Benefits: The posting lists benefits under "What you can expect as a Vanta’n:" includes many bullet points: Industry-competitive salary and equity, Comprehensive medical..., 16 weeks paid Parental Leave, Health & wellness stipend, Remote workspace stipend, Commuter benefits, Family planning benefits, Matching 401(k) contribution, Flexible PTO policy plus 80 hours Sick Time, 11 company-paid holidays, Virtual team building activities, Offices list.
Pay: The posting includes a paragraph about base pay ranges: "To provide greater transparency to candidates, we share base pay ranges for all US-based job postings regardless of state. We set standard base pay ranges for all roles based on function, level, and country location, benchmarked against similar-stage growth companies. Final offer amounts are determined by multiple factors and may vary based on candidate location, skills, depth of work experience, and relevant licenses/credentials."
That's about pay but not specific numbers. It says they share base pay ranges but not give numbers. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state they share base pay ranges, but does not give actual numbers. Is that considered filler? It says they share base pay ranges but not give them. It's somewhat vague but still states they provide ranges. However the instruction says avoid placeholder like "varies". The text says "Final offer amounts are determined by multiple factors and may vary based on candidate location, skills, depth of work experience, and relevant licenses/credentials." That's somewhat generic. But they also say they share base pay ranges for all US-based job postings regardless of state. That is a statement about practice, not a specific range. It's not a specific number, but it's not "varies" exactly. It's more like they have a policy. I think we can include a Pay section with that paragraph, as it's substantive info about pay transparency. It's not a placeholder like "commensurate with experience". It's a statement about policy. So include Pay.
Schedule: No mention of schedule (full-time, part-time, remote?). There's mention of remote workspace stipend, offices, but not explicit schedule. So we should not create Schedule section.
Now we need to remove boilerplate: The "Referral Instructions", "About Vanta" paragraph after benefits, "To provide greater transparency..." we already used for Pay. The "About Vanta" section after that is about company history; could be considered About the role? Actually it's about Vanta company, not role. Might be considered boilerplate? It's substantive about company but not role. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info? It's about Vanta mission and history. Could be placed under About the role? But About the role already has mission intro. The "About Vanta" section is more detailed company background. Could be included as part of About the role or maybe a separate section? Not listed in allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit all substantive info into those sections. The About Vanta history could go under About the role (expanding). That seems okay.
We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. The posting includes: "As an equal opportunity employer, we encourage and welcome people of all backgrounds to apply." That's EEO boilerplate; remove. Also "Referral Instructions" is application instruction; remove. Also "To provide greater transparency..." we kept for Pay. Also "About Vanta" we keep as part of About the role.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which content goes where.
We have:
- About the role: description of role, mission, impact.
- Responsibilities: the bullet list under "What you’ll do..."
- Requirements: maybe experience, education, work authorization.
- Qualifications: maybe technical skills, analytical thinking, collaboration, communication.
- Skills: maybe specific technical skills (SQL, Tableau, etc.) but we already have technical skills.
But we need to avoid duplication. Could combine.
Better: Use sections:
- About the role: intro paragraph.
- Responsibilities: bullet list of duties.
- Requirements: Experience (4+ years), Education (Bachelor’s degree), Work authorization (must be authorized to work in US), Open to using AI (maybe as a trait).
- Qualifications: Technical Skills (SQL, data visualization, DBT, Python), Analytical Thinking, Collaboration, Communication.
- Skills: maybe we could combine technical skills into Skills, but we already have Qualifications. The instruction says we can have both Qualifications and Skills sections if content exists. We could put technical skills under Skills, and analytical thinking etc under Qualifications. Or we could put all under Qualifications and leave Skills empty (but we must not emit empty sections). So we need to decide.
Let's assign:
- Skills: Technical Skills (SQL, Tableau/Sigma, DBT, Python).
- Qualifications: Analytical Thinking, Collaboration, Communication, Experience, Education, Work authorization, AI usage.
But Experience and Education are more like requirements. Could put them under Requirements.
Thus:
- Requirements: Experience (4+ years), Education (Bachelor’s degree in related field), Must be authorized to work in the U.S., Open to using AI to amplify their skills.
- Qualifications: Analytical Thinking, Collaboration, Communication.
- Skills: Technical Skills (SQL, data visualization tools, DBT, Python).
Now Benefits: The posting lists benefits under "What you can expect as a Vanta’n:" includes many bullet points: Industry-competitive salary and equity, Comprehensive medical..., 16 weeks paid Parental Leave, Health & wellness stipend, Remote workspace stipend, Commuter benefits, Family planning benefits, Matching 401(k) contribution, Flexible PTO policy plus 80 hours Sick Time, 11 company-paid holidays, Virtual team building activities, Offices list.
Pay: The posting includes a paragraph about base pay ranges: "To provide greater transparency to candidates, we share base pay ranges for all US-based job postings regardless of state. We set standard base pay ranges for all roles based on function, level, and country location, benchmarked against similar-stage growth companies. Final offer amounts are determined by multiple factors and may vary based on candidate location, skills, depth of work experience, and relevant licenses/credentials."
That's about pay but not specific numbers. It says they share base pay ranges but not give numbers. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state they share base pay ranges, but does not give actual numbers. Is that considered filler? It says they share base pay ranges but not give them. It's somewhat vague but still states they provide ranges. However the instruction says avoid placeholder like "varies". The text says "Final offer amounts are determined by multiple factors and may vary based on candidate location, skills, depth of work experience, and relevant licenses/credentials." That's somewhat generic. But they also say they share base pay ranges for all US-based job postings regardless of state. That is a statement about practice, not a specific range. It's not a specific number, but it's not "varies" exactly. It's more like they have a policy. I think we can include a Pay section with that paragraph, as it's substantive info about pay transparency. It's not a placeholder like "commensurate with experience". It's a statement about policy. So include Pay.
Schedule: No mention of schedule (full-time, part-time, remote?). There's mention of remote workspace stipend, offices, but not explicit schedule. So we should not create Schedule section.
Now we need to remove boilerplate: The "Referral Instructions", "About Vanta" paragraph after benefits, "To provide greater transparency..." we already used for Pay. The "About Vanta" section after that is about company history; could be considered About the role? Actually it's about Vanta company, not role. Might be considered boilerplate? It's substantive about company but not role. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info? It's about Vanta mission and history. Could be placed under About the role? But About the role already has mission intro. The "About Vanta" section is more detailed company background. Could be included as part of About the role or maybe a separate section? Not listed in allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit all substantive info into those sections. The About Vanta history could go under About the role (expanding). That seems okay.
We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. The posting includes: "As an equal opportunity employer, we encourage and welcome people of all backgrounds to apply." That's EEO boilerplate; remove. Also "Referral Instructions" is application instruction; remove. Also "To provide greater transparency..." we kept for Pay. Also "About Vanta" we keep as part of About the role.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce:
About the role
... (combined intro and About Vanta)
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Skills
- ...
Benefits
- ...
Pay
...
No Schedule. Now we need to extract exact sentences. Let's copy relevant text. Intro: "At Vanta, our mission is to help businesses earn and prove trust. We believe that security should be monitored and verified continuously, and we empower companies to practice better security and prove it with ease. Vanta has a kind and talented team, and while some have prior security experience, many have been successful at Vanta without it. As a Senior Data Analyst on the Finance team, you’ll play a pivotal role in uncovering the insights that shape company-wide planning, forecasting, and strategic decision-making. This high-impact role blends analytical rigor, technical fluency, and business acumen to steer strategy and identify opportunities for scalable growth. The Finance Data team partners with both Finance and other teams across Vanta. You’ll collaborate closely with stakeholders to build trust and deliver data-driven recommendations; your work will influence everything from operating plans and investment decisions to self-serve reporting and process automation. This is a unique opportunity to deepen your analytics expertise in a dynamic, high-growth environment, with visibility into executive-level priorities and the ability to shape them with data." That's the About the role content. Now About Vanta history: "We started in 2018, in the wake of several high-profile data breaches. Online security was only becoming more important, but we knew firsthand how hard it could be for fast-growing companies to invest the time and manpower it takes to build a solid security foundation. Vanta was inspired by a vision to restore trust in internet businesses by enabling companies to improve and prove their security. From our early days automating security monitoring for compliance standards like SOC 2, HIPAA and ISO 27001 to creating the world's leading Trust Management Platform, our vision remains unchanged. Now more than ever, making security continuous—not just a point-in-time check— is essential. Thousands of companies rely on Vanta to build, maintain and demonstrate their trust— all in a way that's real-time and transparent." We can append that to About the role paragraph. Now Responsibilities bullet list: - Deliver strategic insights by conducting deep, prioritized analyses that inform high-impact financial decisions. - Act as a technical partner to teams across FP&A, Accounting, RevOps, Product, Marketing, and more. - Increase team efficiency by automating recurring deliverables and helping scale workflows as the company grows. - Empower decision-makers with self-service dashboards and data assets that surface trends and drive informed choices across the business. - Advance our analytics infrastructure by partnering with Data Engineering and other analytics teams to democratize access to high quality data and insights. Now Requirements: - Experience: 4+ years of experience in data analysis or equivalent function. Exposure to FP&A, Accounting, or SaaS metrics is a plus. - Education: Bachelor’s degree in Data Analytics, Statistics, Informatics, Finance, Economics, Business, or a related field. - Must be authorized to work in the U.S. - Open to using AI to amplify their skills and strengthen their work - demonstrating curiosity, a willingness to learn, and sound judgment in applying AI responsibly to improve efficiency and impact. We could combine "Experience" and "Education" as separate list items. Now Qualifications: - Analytical Thinking: Proven ability to analyze complex data sets, uncover key insights, and translate findings into actionable strategies that drive financial outcomes. - Collaboration: Demonstrated success working cross-functionally and building relationships across business teams. Comfortable engaging stakeholders with varying levels of data fluency. - Communication: Clear and effective communicator, both written and verbal. Skilled at presenting complex data insights to non-technical audiences. Now Skills: - Technical Skills: Strong proficiency in SQL and data visualization tools (e.g., Tableau, Sigma), with experience handling large and complex data sets. Familiarity with DBT is preferred. Bonus points for skill in Python for advanced analysis. Now Benefits list: - Industry-competitive salary and equity - Comprehensive medical, dental, and vision coverage, with 100% of employee-only benefit premiums covered for most medical plans - 16 weeks paid Parental Leave for all new parents - Health & wellness stipend - Remote workspace, internet, and cellphone stipend - Commuter benefits for team members who report to the SF and NYC office - Family planning benefits - Matching 401(k) contribution with immediate vesting - Flexible PTO policy, plus 80 hours of Sick Time - 11 company-paid holidays - Virtual team building activities, lunch and learns, and other company