Senior Analyst, GTM (Hybrid)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Content: Intro: "Hi, Future Homie! At Homebase, you’ll join a team that’s bold, fast-moving, and obsessed with helping small businesses thrive. We build with empathy, act with urgency, and take big swings that drive real-world impact. Here, every Homie shows up to raise the bar, support one another, and celebrate wins as a team. We’re not just building an app—we’re building unstoppable teams. So what do you say, are you in? 📍Your Impact Starts Here We are looking for a Senior Analyst to help our Go-to-Market teams make better decisions with data. This is a broad GTM analytics role spanning Sales, Marketing, RevOps, and Customer Support. You will connect systems and data sources together, run analyses that drive business decisions, and build self-serve tools that let teams answer their own questions instead of waiting on one-off requests. Just as important as how you build is knowing what's worth building. You will help decide which questions actually matter and define the metrics that answer them. In this role, you will spend time with GTM teams to understand what enables them to grow and excel, and use that understanding to decide what's worth building. You won't just be an analyst; you'll be a builder of AI-powered systems and tools that solve those problems, moving at a speed that wouldn't be possible the traditional way. If you're energized by answering the most important business questions, owning complex analytical systems, and building tools that scale beyond individual requests, this role is for you." Then bullet list of key ways you’ll contribute and create impact: (list items). Then "The Foundation for Success - These are the experiences and strengths that will set you up for success in this role:" then bullet list. Then "🤝 The Homie Way - These principles guide everything we do—from how we work and make decisions to how we show up for each other." then bullet list of principles. Then "What we offer (United States)" with bullet list of benefits. Then "What we offer (Canada)" similar. Then "What To Expect During The Interview Process" (list steps). Then "Welcome to the team, Homie 🎉 💜 Belonging at Homebase - We're committed to fostering a welcoming space..." then EEO etc. Then "Compensation Range: $107K - $126K" We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove interview process? The instruction says remove application instructions. The interview process steps might be considered application instructions? Possibly yes. It says "What To Expect During The Interview Process Meet the Talent Acquisition team, Ryan H. Meet the Hiring Manager, Nelson T. Participate in a Case Study & Panel Interview Background Check + Offer StageWelcome to the team, Homie 🎉". That's basically interview process details; might be considered application instructions. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the interview process section. Also remove "Welcome to the team, Homie 🎉 💜 Belonging at Homebase..." and EEO statements. We need to preserve all substantive information: role description, responsibilities (the bullet list), foundation for success (experiences and strengths), the Homie Way principles, benefits (US and Canada), compensation range. We need to structure into sections: About the role (maybe the introductory paragraph describing role), Responsibilities (the bullet list of key ways you’ll contribute), Requirements (maybe the foundation for success?), Qualifications (maybe overlapping?), Skills (maybe technical skills?), Benefits (US and Canada combined?), Pay (compensation range), Schedule (maybe hybrid rhythm? The posting mentions "Our Hybrid Rhythm: We believe collaboration drives impact. That’s why Tuesdays and Wednesdays are our required in-office days—a time to move faster as a team, build deeper connections, make better decisions, and build together." That's schedule info. So we can include Schedule section with that. We must not create sections with filler like "commensurate with experience". We have actual content. We need to decide which sections to include: About the role (intro paragraph), Responsibilities (bullet list of contributions), Requirements (maybe the foundation for success bullet list), Qualifications (maybe we could split foundation into qualifications and skills? But we have "The Foundation for Success - These are the experiences and strengths that will set you up for success in this role:" which includes experiences and strengths. Could treat as Requirements. Then Skills: maybe we can extract technical skills from that list: "3–5 years of experience in analytics, with demonstrated ability to model and measure business impact", "Proven ability to build and maintain an AI-powered reporting and insights system...", "Strong technical foundation with an AI-native mindset...", "Advanced SQL skills, AI-assisted proficiency in Python and R, and experience with modern analytics and data stacks (Salesforce, dbt, Databricks/Snowflake, Looker, Tableau, or similar)", "Experience working cross-functionally with Sales, Marketing, RevOps, and Finance in a high-growth SaaS or subscription environment", "Exceptional communication and storytelling...". Those could be considered qualifications/skills. We could put them under Requirements or Qualifications. Since we need to avoid thin sections, maybe combine Requirements and Qualifications into one? But the instruction says use headings for those specific headings if we have content. We could have both Requirements and Qualifications if we have distinct content. However we might not have clear separation; we could put all under Requirements and skip Qualifications. Or we could put under Requirements the experiences and strengths, and under Skills the technical skills list. Let's see: The foundation list includes both experiences and technical skills. Could split: Requirements: experiences (3-5 years, ability to model impact, proven ability to build AI-powered system, experience cross-functionally, exceptional communication). Skills: technical foundation (AI-native mindset, advanced SQL, AI-assisted Python/R, experience with stacks). That seems reasonable. Benefits: we have US and Canada lists. Could combine into one Benefits section with both US and Canada bullet points, maybe note differences. But we should preserve all substantive info. Could create Benefits section with subpoints? But we only allowed

• for list. Could have two separate
  under Benefits? That's okay. Or we could have Benefits and then note US vs Canada within same list with clarification. Probably easiest: Benefits section with two paragraphs: one for US, one for Canada, each with
  • . That preserves info. Pay: compensation range. Schedule: hybrid rhythm (Tue/Wed required in-office days). Also maybe mention Work From Anywhere Month + meeting-free weeks yearly (that's also under benefits? Actually it's under What we offer (US) and (Canada) as "Work Your Way: Work From Anywhere Month + meeting-free weeks yearly". That's a benefit, not schedule. So schedule is just the required in-office days. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Check if any section would be empty or filler: All have content. Now we need to strip out any boilerplate like emojis? We can keep emojis? Probably okay but not required. We'll keep text. We must not include markdown code fences. Output only HTML fragment. Let's craft. About the role:

    About the role

    ...

    We need to include the introductory paragraph up to "This role is for you." That's the description. Let's extract: "Hi, Future Homie! At Homebase, you’ll join a team that’s bold, fast-moving, and obsessed with helping small businesses thrive. We build with empathy, act with urgency, and take big swings that drive real-world impact. Here, every Homie shows up to raise the bar, support one another, and celebrate wins as a team. We’re not just building an app—we’re building unstoppable teams. So what do you say, are you in? 📍Your Impact Starts Here We are looking for a Senior Analyst to help our Go-to-Market teams make better decisions with data. This is a broad GTM analytics role spanning Sales, Marketing, RevOps, and Customer Support. You will connect systems and data sources together, run analyses that drive business decisions, and build self-serve tools that let teams answer their own questions instead of waiting on one-off requests. Just as important as how you build is knowing what's worth building. You will help decide which questions actually matter and define the metrics that answer them. In this role, you will spend time with GTM teams to understand what enables them to grow and excel, and use that understanding to decide what's worth building. You won't just be an analyst; you'll be a builder of AI-powered systems and tools that solve those problems, moving at a speed that wouldn't be possible the traditional way. If you're energized by answering the most important business questions, owning complex analytical systems, and building tools that scale beyond individual requests, this role is for you." We can keep that as a single paragraph. Responsibilities: bullet list of key ways you’ll contribute and create impact. The list items: - Architect and maintain the data and reporting system that connects our entire GTM funnel (marketing, product, sales, and CX) into a single, trusted view of the business, covering everything from pipeline health to campaign performance to customer support metrics - Define and maintain a clear, consistent metric framework, partnering with GTM leadership to evaluate ROI by motion and channel and identify which programs are driving results - Build scalable self-serve tools (agentic BI tools, natural language interactions, agent skills, etc.) that empower teams, managers, and executives to track performance without relying on ad hoc requests - Proactively surface risks and opportunities, spotting gaps, trends, and quality signals before they become surprises for leadership - Translate complex analyses into clear, executive-ready insight that drives decisions on headcount, investment, and strategy - Work closely with data engineering to ensure data integrity, tracking accuracy, and instrumentation completeness as new GTM motions launch We'll put each as
  • . Requirements: experiences and strengths that will set you up for success: bullet list: - 3–5 years of experience in analytics, with demonstrated ability to model and measure business impact - Proven ability to build and maintain an AI-powered reporting and insights system, meaning you can define instrumentation, structure data, and keep a body of context for AI agents to reason over reliably - Experience working cross-functionally with Sales, Marketing, RevOps, and Finance in a high-growth SaaS or subscription environment - Exceptional communication and storytelling. Able to translate complex pipeline and revenue data into clear, executive-ready narratives that drive decisions. We could also include "Strong technical foundation with an AI-native mindset..." but that's more skill. We'll keep that under Skills. Skills: technical foundation: - Strong technical foundation with an AI-native mindset. You build agents, automate workflows, and use AI tools like Claude Code in both your work and personal life, and you keep a close eye on the latest AI productivity tools - Advanced SQL skills, AI-assisted proficiency in Python and R, and experience with modern analytics and data stacks (Salesforce, dbt, Databricks/Snowflake, Looker, Tableau, or similar) We could also include "Proven ability to build and maintain an AI-powered reporting and insights system" but that's already in Requirements; maybe we keep it there. It's okay. Benefits: we need to include US and Canada offerings. Let's create a Benefits section with two subheadings? But we cannot add extra headings beyond the allowed list? The instruction only