Senior Analytics Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: "What's happening at Vay", "Why this role is exciting", "What you'll be driving", "What are we looking for", "Nice to have", "Why choose Vay". Also maybe "About the role"? Not present. We must use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We can map content to these headings: "What you'll be driving" corresponds to Responsibilities. "What are we looking for" corresponds to Requirements/Qualifications/Skills. "Nice to have" could be additional qualifications but maybe we can include under Requirements as separate list? Could create a "Qualifications" section for required, and maybe "Skills" for nice-to-have? But we must not create sections with filler. We have content for Responsibilities, Requirements, Benefits. Also we have Pay? Not mentioned. Schedule? Not mentioned. So we should not include Pay or Schedule sections. Benefits: we have benefits listed under "Why choose Vay": stock options, flexible paid vacation, 30% off rides, external discounts, $350 home office set-up, relocation assistance, regular team events. So we can create Benefits section. We also have "About the role" maybe we can use the introductory paragraph: "Ever imagined saying..." etc. That's about the company and role. Could map to About the role. But we must not repeat job title as heading. It's okay. We need to preserve all substantive information, remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes: "For more information on Vay's physical demands, working environments and safety requirements, you can review this link." That's boilerplate? Might be considered minor metadata; we can drop. Also "We'd love to stay connected..." etc. That's application instruction? Might be considered boilerplate; we should drop application instructions. Also "We welcome applications from all backgrounds..." is EEO; drop. Also "If you're excited..." maybe keep? It's motivational but could be considered boilerplate. Safer to drop generic EEO lines. Keep substantive content: company description, mission, achievements, role excitement, responsibilities, requirements, nice-to-have, benefits. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need
  . For requirements list, also
  . For benefits list, also
  . For nice-to-have maybe also list but could be under Requirements? Might be separate "Qualifications" but we can include as part of Requirements with a note? Better to have separate "Qualifications" for required and "Skills" for nice-to-have? But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: company intro/mission. - Responsibilities: "What you'll be driving" bullet list. - Requirements: "What are we looking for" bullet list (required). - Qualifications: maybe we could put "Nice to have" as Qualifications? But Qualifications usually required. However we have no separate qualifications beyond requirements. Could treat "Nice to have" as Skills. So: - Skills: "Nice to have" bullet list. - Benefits: "Why choose Vay" bullet list. We must not create sections with filler. All have content. We need to preserve all substantive information: include details like "End-to-end analytics solutions, from data modeling (SQL, dbt) through to dashboards and insight delivery (Superset, Grafana, Dekart)." etc. We need to format as HTML fragment only. Let's extract content. Company intro: "Ever imagined saying, 'I helped launch the future of transportation'? We're rewriting the rules of urban mobility. At Vay, customers tap a button and a car arrives - with no one inside - powered by our world-first Remote Driving technology on real public streets. We're live in Las Vegas and scaling fast, powered by a strategic investment of up to $410 million from Grab. Our mission is simple: replace private car ownership with a faster, cleaner, door-to-door mobility model. If you want to build something real, visible, and genuinely transformative, you'll feel right at home here. Curious to experience Vay yourself? Use the code VAYCANDIDATE for $10 off your first trip in Las Vegas! Download the 'Vay' app from the Apple or Google Play store & off you go!" But the instruction says remove application instructions? The code VAYCANDIDATE and download app might be considered promotional but still substantive? It's not boilerplate; it's part of company description. Might keep. Next: "What's happening at Vay First to roll out vehicles in both Europe and the USA on public roads without a human being inside & currently the 2nd largest commercial, driverless car fleet in the Western World.We've partnered with Kodiak to bring remote-driving technology to autonomous trucks in the US, showcasing our ability to integrate our system into heavy-duty commercial vehicles and expand the applications of our tech across the US.We've completed 10's of thousands of trips so far and are busy multiplying our Las Vegas fleet just to meet demand!...And soon we'll be expanding across the US & Europe 🚀" We need to keep that. Next: "Why this role is exciting As a Senior Analytics Engineer, you'l be sitting at the core of our Operations team, where data drives day-to-day decisions. You'll work directly with onsite operational leaders to identify opportunities, solve real-world problems, and build analytics products that materially improve performance, efficiency, and customer experience. This is a high-impact, hybrid analytics engineering / business intelligence role. You won't be buried in dashboards no one uses. You'll shape how our customer-facing services operate and scale, with a direct line between your work and operational outcomes. If you want ownership, visibility, and impact, this role delivers all three." Next: "What you'll be driving Own end-to-end analytics solutions, from data modeling (SQL, dbt) through to dashboards and insight delivery (Superset, Grafana, Dekart).Act as the primary data partner for Operations and Mobility Product, working closely with Ops and Product leaders to:Identify opportunitiesDefine and refine KPIsDrive continuous performance improvementDeliver measurable impact across critical operational areas including:Fleet readinessMaintenance performanceCharging and vehicle positioning optimizationOverall operational efficiencyDesign and maintain self-serve dashboards, alerts, and reporting interfaces that give Ops teams real-time visibility and decision-making power.Translate business and operational questions into actionable, data-driven solutions using strong domain context and product thinking.Collaborate with Data Science teams to align on data practices, tooling, and standards across Vay.Move fast, iterate often, and take ownership, balancing pragmatic delivery with building scalable, long-term data foundations." We need to split into bullet list items. Next: "What are we looking for Strong end-to-end analytics ownership: you've taken data products from concept through to production.Proven track record of impact: your work has directly improved business or operational outcomes.Expert-level SQL skills: complex, performant queries are second nature.Strong experience with dbt: including designing sustainable, reusable data models.Proficiency with BI tools such as Superset, Looker, or similar, and a sharp eye for clear, actionable dashboards.Comfortable working autonomouslyExperience with cloud data warehouses (e.g. Snowflake, BigQuery).Familiarity with modern data tooling, including:ETL / reverse ETL tools (Airbyte, Hightouch)Data flow / integration tools (NiFi, OpenFlow)Comfortable handling light engineering work, such as:Working with APIsConfiguring visualization toolsSetting up integrationsSolid understanding of time-series data and operational metrics, ideally with exposure to observability or real-time monitoring." Next: "Nice to have Experience in fast-paced environments such as startups, scale-ups, or operations-heavy businesses.Familiarity with scripting (Python, JavaScript, etc.) for automation or lightweight tooling.Exposure to operational domains like mobility, logistics, fleet, or marketplaces.A strong product mindset: you think in terms of users, feedback loops, and delivered value, not just queries and pipelines." Next: "Why choose Vay 💪 A global team of smart, motivated people from 30+ countries who love tackling hard problems and turning bold ideas into reality 🌍 Huge scope for impact in a fast paced environment 💰 EIP stock options: A stake in Vay's future - not just a salary 🌴 Flexible Paid Vacation Days 🚗 All Vay team members receive 30% off their Vay rides 🛍️ Exclusive external discounts 💼 $350 Home Office Set-up ✈️ Relocation financial assistance when relocating to Las Vegas 🎊 Regular team events throughout the year" We need to output HTML with headings

  and paragraphs

  for prose, lists

  • for lists. We need to decide what goes into paragraphs vs lists. For About the role: we can have a paragraph summarizing company intro and mission. Could be multiple paragraphs but we can combine. For Responsibilities: we need a list of duties. The "What you'll be driving" includes several items: Own end-to-end analytics solutions..., Act as primary data partner..., Identify opportunities..., Define and refine KPIs..., Drive continuous performance improvement..., Deliver measurable impact..., Design and maintain self-serve dashboards..., Translate business..., Collaborate with Data Science..., Move fast... We can break each sentence after colon into list items. For Requirements: list each bullet from "What are we looking for". Items: Strong end-to-end analytics ownership..., Proven track record..., Expert-level SQL skills..., Strong experience with dbt..., Proficiency with BI tools..., Comfortable working autonomously, Experience with cloud data warehouses..., Familiarity with modern data tooling (list subitems?), Comfortable handling light engineering work (list subitems?), Solid understanding of time-series data... We could flatten subitems as separate list items or keep as part of parent. Simpler: each main bullet as
  • . Subbullets could be separate
  • indented? Not required but we can include. For Skills (nice to have): list each. For Benefits: list each benefit from "Why choose Vay". Items: A global team..., Huge scope..., EIP stock options..., Flexible Paid Vacation Days..., All Vay team members receive 30% off..., Exclusive external discounts..., $350 Home Office Set-up..., Relocation financial assistance..., Regular team events... We need to preserve emojis? Probably okay to keep but not necessary. We can keep text. We must not include markdown fences. Just raw HTML. Let's craft. Start with

    About the role

    then

    ...

    . Then

    Responsibilities

    • ...
    ...
    Then

    Requirements

    ... Then

    Skills

    ... Then

    Benefits

    ... We must not include Pay or Schedule. Check for any repeated content: ensure we didn't miss any substantive info like "We've completed 10's of thousands of trips..." etc. That is in "What's happening at Vay". Should be included in About the role paragraph maybe. Let's draft About the role paragraph: "Ever imagined saying, 'I helped launch the future of transportation'? We're rewriting the rules of urban mobility. At Vay, customers tap a button and a car arrives - with no one inside - powered by our world-first Remote Driving technology on real public streets. We're live in Las Vegas and scaling fast, powered by a strategic investment of up to $410 million from Grab. Our mission is simple: replace private car ownership with a