Analytics ManagerNew New York, NY
Abelardo Gotay-Registered Dietitian/Nutritionist · New York, NY · 4 wk ago
Analyst$100/hrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), maybe Skills, Benefits, Pay, Schedule only if present. The posting includes "About The Role" heading, then description. Then "Key Responsibilities". Then "We’d Love To Hear From You If" which is requirements/qualifications. There's no explicit Benefits, Pay, Schedule. So we should not include those sections. Also we need to include About Us? The instruction: "use About Us? Not in list). Safer to just output paragraphs for that content, then sections for About the role, Responsibilities, Requirements (or Qualifications). The "We’d Love To Hear From You If" is qualifications. We'll make a section with heading
. The bullet list lines:
- Lead and develop a team of Analytics Engineers: lead planning and prioritization; provide technical and analytical guidance; hold the bar on execution; help hire new team members.
- Define and deliver the analytics roadmap across data modeling, business intelligence, and AI-enabled analytics. Establish technical standards that help the team scale.
- Deliver high-impact insights: lead analyses of ambiguous problems; proactively identify opportunities; partner with leadership on solving complex and impactful analytics questions.
- Build and maintain a robust data foundation: Partner with Engineering to validate and optimize pipelines, ensuring our data infrastructure is accurate, scalable, and supports a trusted single source of truth.
- Champion a data-first culture: Guide teams to interpret and act on data, write clear documentation, and lead by example in driving evidence-based decisions.
We'll put under
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says include a section ONLY when the posting has real, specific content for it. The posting includes "About Us" at top, but that's not one of the listed headings. Should we include an About Us section? The list of example headings includes "About the role" not "About Us". The instruction says use those headings for section headings. It doesn't forbid other headings, but likely we should stick to those. The "About Us" is descriptive but maybe we can treat as a paragraph before sections. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't say we cannot include an About Us paragraph. We can include it as a
before sections. Probably we should include the "About Us" content as a paragraph (maybe preceded by an
About Us? Not in list). Safer to just output paragraphs for that content, then sections for About the role, Responsibilities, Requirements (or Qualifications). The "We’d Love To Hear From You If" is qualifications. We'll make a section with heading Requirements
(or Qualifications). The list includes both Requirements and Qualifications; we can choose Requirements. Provide bullet list for each bullet.
We need to preserve all substantive information; do not invent or summarize away detail. Must not include boilerplate like cookie/navigation/legal/EEO etc. There's none.
We need to output only HTML fragment.
Let's extract content.
About Us paragraph: "Health is the most important thing in life, and the American healthcare system is completely broken - poor outcomes, high cost, bad patient experience. We're building a new system from the ground up. Our mission is to improve people’s health by making it easy to live a healthy lifestyle. Nourish is the country's largest dietitian-led metabolic health clinic. We’re an AI-native digital health system matching patients with 10,000+ Registered Dietitians, physicians, medications, lab testing, and AI agents to deliver insurance-covered care across all 50 states. Founded four years ago, we've completed millions of appointments, tripled year-over-year, and partnered with health plans covering 200M+ Americans across 250+ health systems. In 2026 we raised a $100M Series C, bringing total funding to $215M. The round was led by Menlo Ventures, with participation from Thrive Capital, Index Ventures, J.P. Morgan Growth Equity Partners, Maverick Ventures, Y Combinator, BoxGroup, Atomico, Daybreak, and Operator Partners. Learn more about our Series C here: Nourish Blog, Bloomberg, Fierce Healthcare, Digital Native, The Pulse Podcast. This is not a job for everyone. We hold an extremely high bar because we believe talent density is our biggest competitive advantage. We're looking for people who actively choose hard, ambiguous problems, who run toward unglamorous work, give and receive candid feedback, and bring relentless resilience without the ego. Our work is important, but we are not self-important. We do this because we’re solving one of the hardest problems in the world, and the problem matters. If that's you, we disproportionately reward it."
That's a lot; we keep as paragraph(s). Could split into multiple
for readability but not required. About The Role: after "About The Role" heading. Content: "We're scaling quickly, and data is a critical lever to growing our business and improving patient outcomes. As Analytics Manager, you'll lead the strategy and execution of a team of analytics engineers working across a multitude of domains, partner with leadership on critical business questions, and drive the vision for the future of Analytics at Nourish. This role combines analytics engineering, business insights, and people management to support domains ranging from supply and demand to marketing, and operations. You'll work closely with Operations, Engineering, and Product to build reliable data foundations and help teams answer their most important questions. You'll define and execute Nourish's analytics roadmap alongside other Data leads. Our Data team is based in NYC and goes into the office 2-3 days a week. While this isn't a strict requirement, we are looking for people who would be excited to be part of that culture." Key Responsibilities: bullet list. We need to convert each bullet into
Responsibilities
then- .
We’d Love To Hear From You If: list of qualifications.
We need to capture each bullet:
- Have 5+ years of relevant experience owning analytics end to end at a fast-paced, high-growth company.
- Have 2+ years of leadership experience leading not only your team day to to day, but also setting and driving the technical vision to support business growth.
- Are an unstoppable problem-solver taking complex and highly ambiguous asks and turning them into structured and thoughtful roadmaps to be rolled out to a lean team.
- Have deep domain expertise in analytics engineering: You write clean, performant SQL, have hands-on experience with tools like dbt and Fivetran, and have a strong grasp of the fundamentals of data modeling, ETLs, and infrastructure.
- Are curious, strategic, and outcome-oriented: You proactively shape the right questions, translate complex data into clear, actionable insights, and balance speed with depth to drive clear, high-impact decisions across the business
- Are a builder who thrives on ownership and impact: You take pride in designing clean, scalable systems from scratch, and are excited to take end-to-end ownership - filling gaps, creating structure, and becoming the go-to person others rely on for clarity.
- Communicate complex ideas with clarity: You distill deep analysis into crisp, actionable takeaways, whether writing a Notion doc or presenting to leadership, and you earn trust across cross-functional teams by speaking the language of both operations and engineering
- Are motivated by impact and mission: You believe in the power of food as medicine to transform healthcare and are excited to improve lives at scale by contributing to Nourish’s mission.
We'll put under
Requirements
(or Qualifications). Choose Requirements. We should not include Benefits, Pay, Schedule. Now produce HTML. We need to ensure no extra text. Just HTML. Let's craft:About Us paragraph(s). Could be one big p. Then
About the role
...
ThenResponsibilities
- ...
Requirements
- ...