Senior Forecasting & Planning Analyst
Branch · United States · 3 wk ago
RemoteRemoteBusiness Development$85k–$95k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities (maybe "What You'll Own"), Requirements (maybe "What You Bring"), Skills (Technical Skills), Benefits? Not present. Pay: we have compensation range. Schedule: not present. So include Pay section with the range. Also maybe Benefits not present, so omit. Ensure we don't repeat job title. Use for each section heading. Use
for each section heading. Use - for lists. Use
for prose. Remove boilerplate. Preserve all substantive info.
We need to include About Branch? The posting includes "About Branch" but that's likely boilerplate? It's about company description. Might be considered substantive? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About Branch is company overview, not boilerplate. Should we keep? It's part of the posting. Probably keep as a section? There's no heading for About Branch in the list of allowed headings; but we could treat it as a paragraph under maybe no heading? The instruction says 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. Probably we should only include those headings if content exists. About Branch could be considered "About the role"? No. Could be a separate section but not in list; maybe we should not create a heading for it, just include as a
before the role section? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid other headings, but they gave examples. Safer to include About Branch as a
without heading, or maybe as a
About Branch? Not in list but could be okay. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings; we should stick to them. So we should not create a heading for About Branch; we can include its content as a
before the role section.
Thus structure:
About Branch ...
About the role
...
Then maybe Responsibilities
with list of what you'll own.
Then Requirements
with what you bring (experience). Could also split into Qualifications? But we have "What You Bring" includes experience and skills. We'll treat as Requirements.
Then Skills
with Technical Skills list.
Then Pay
with compensation range.
No Benefits, Schedule.
Make sure to preserve all details.
Let's extract content.
About Branch paragraph: "Branch is shaking up the $46B office products industry to create the best work experience for the 21st century: easy, affordable and adaptable so you can sit down (or stand) and get to work. Most people spend eight hours a day at their workspace. Our mission is creating accessible and inspiring products to help people and teams feel their best at work, wherever that happens. We're based in NYC and Toronto, and backed by the investors behind Quip, Caraway, Eight Sleep and Peloton. Our culture combines strategic clarity with scrappy execution; we think and plan rigorously but ship fast and have fun doing it. We're looking for entrepreneurial teammates who do the same."
About The Role paragraph: "We're growing our Forecasting & Planning team to support the business's increasingly complex channel mix — most notably our rapidly scaling Enterprise/B2B business. This role sits upstream of tactical execution, focused on strategic demand planning, cross-functional partnership, and channel-specific ownership. You'll partner closely with the Senior Manager and a Forecasting Analyst to build the planning function's next chapter. This role is salaried with a compensation range of $85,000-$95,000 based on the candidate's experience, skills, competencies, qualifications and market."
What You'll Own bullet points (list). Need to preserve each line.
Let's list them:
- Enterprise/B2B channel planning: Serve as the primary forecasting and planning owner for the Enterprise channel, partnering directly with Sales and Account Management to translate pipeline and account-level signals into demand forecasts
- Strategic demand planning: Own the higher-level forecasting methodology and assumptions feeding the overall revenue forecast (DTC, Enterprise, Amazon, Wholesale), stepping back from day-to-day tactical placement to focus on scenario planning, risk-flagging, and forecast accuracy improvement
- Tooling & automation: Build and maintain BigQuery-based data pulls, automate recurring reporting/forecasting workflows, and apply AI tools to speed up analysis — reducing manual, spreadsheet-dependent processes over time
- S&OP-style cross-functional partnership: Represent planning in cross-functional forecast reviews with Sales, Finance, and Product; translate business context into planning assumptions and vice versa
- New product introduction (NPI) planning: Partner with Product Development on demand forecasting for new launches, building forecast logic for products with no historical sell-through
- Product lifecycle strategy: Own the strategic view of lifecycle management — discontinuation timing, overstock/understock risk, and recommendations tied to broader merchandising strategy (with room to grow into deeper merch collaboration as the team scales)
- Process & methodology improvement: Identify and implement improvements to forecasting models, planning cadences, and tools as the team's complexity grows
- Strategic analysis: Contribute ad hoc analysis supporting business-wide decisions (assortment, channel investment, inventory strategy)
What Success Looks Like bullet points:
- Shared Accountability With The Team On MAPE: ≤10% across all channels (with specific ownership of Enterprise channel accuracy)
- In-Stock Rate: 95% combined / 98% on Enterprise All-Star SKUs / 98% on Top 5 SKUs
- DIO: contributing to inventory efficiency through better upstream forecast quality
- Average Parcel Zone: supporting network/inventory placement decisions that improve transit speed and cost
What You Bring bullet points:
- 5–7 years of experience in demand planning, merchandising planning, or forecasting, ideally with prior experience in a formal planner-type role
- Experience with B2B/non-DTC planning is a strong asset (account-based, pipeline-driven, or lumpy-demand forecasting)
- Comfort operating strategically and upstream — someone who can build a point of view on "what should the forecast assume" rather than just executing against a set plan
- Strong cross-functional communication skills; comfortable presenting forecasts and recommendations to non-planning stakeholders
- Bonus: experience with NPI forecasting or product lifecycle management
Technical Skills (high priority) bullet points:
- BI tools: Advanced proficiency in Power BI, Tableau, or Looker — building dashboards and reports from scratch, not just consuming them
- SQL / BigQuery: Comfortable writing and optimizing queries to pull and model data directly from the warehouse, reducing dependency on other teams for data access
- Automation: Track record of automating manual, repetitive planning processes (e.g., scripting recurring reports, automating data refreshes, building repeatable forecast pipelines) rather than rebuilding spreadsheets each cycle
- AI/LLM tools: Hands-on experience applying AI tools (e.g., Claude, ChatGPT, Copilot, or similar) to accelerate analysis, generate code/scripts, summarize data, or build forecasting logic
- Advanced Excel: Experience with complex modeling, but not the primary tool for scaled work
- Python or similar scripting experience is a strong asset, particularly for automation or forecast modeling
Pay: "This role is salaried with a compensation range of $85,000-$95,000 based on the candidate's experience, skills, competencies, qualifications and market."
We already mentioned that in About The Role paragraph; but we need to include Pay section with that detail. Avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include the pay info somewhere. It appears in About The Role paragraph already. We could keep it there and also have Pay section? Might duplicate. Better to keep it in Pay section and maybe remove from About The Role paragraph? But that would remove substantive info from that paragraph. However we could keep the sentence about salaried with compensation range in About The Role paragraph and also have Pay section repeating it; that would be duplication, which we should avoid per instruction: "Remove ... duplicated lines". So we should not duplicate. We need to decide where to place it. The About The Role paragraph currently includes that sentence. If we move it to Pay section, we need to remove it from About The Role paragraph to avoid duplication. That's okay as long as we preserve the info elsewhere. So we will edit About The Role paragraph to exclude the compensation sentence, and then add Pay section with that sentence.
Thus About The Role paragraph becomes: "We're growing our Forecasting & Planning team to support the business's increasingly complex channel mix — most notably our rapidly scaling Enterprise/B2B business. This role sits upstream of tactical execution, focused on strategic demand planning, cross-functional partnership, and channel-specific ownership. You'll partner closely with the Senior Manager and a Forecasting Analyst to build the planning function's next chapter."
Now Pay section: "This role is salaried with a compensation range of $85,000-$95,000 based on the candidate's experience, skills, competencies, qualifications and market.
"
Now ensure we keep all other details.
Now produce HTML.
We'll wrap sections in appropriate tags.
Let's craft:
About Branch ...
About the role
We're growing our Forecasting & Planning team to support the business's increasingly complex channel mix — most notably our rapidly scaling Enterprise/B2B business. This role sits upstream of tactical execution, focused on strategic demand planning, cross-functional partnership, and channel-specific ownership. You'll partner closely with the Senior Manager and a Forecasting Analyst to build the planning function's next chapter.
Responsibilities
- Enterprise/B2B channel planning: Serve as the primary forecasting and planning owner for the Enterprise channel, partnering directly with Sales and Account Management to translate pipeline and account-level signals into demand forecasts
- Strategic demand planning: Own the higher-level forecasting methodology and assumptions feeding the overall revenue forecast (DTC, Enterprise, Amazon, Wholesale), stepping back from day-to-day tactical placement to focus on scenario planning, risk-flagging, and forecast accuracy improvement
- Tooling & automation: Build and maintain BigQuery-based data pulls, automate recurring reporting/forecasting workflows, and apply AI tools to speed up analysis — reducing manual, spreadsheet-dependent processes over time
- S&OP-style cross-functional partnership: Represent planning in cross-functional forecast reviews with Sales, Finance, and Product; translate business context into planning assumptions and vice versa
- New product introduction (NPI) planning: Partner with Product Development on demand forecasting for new launches, building forecast logic for products with no historical sell-through
- Product lifecycle strategy: Own the strategic view of lifecycle management — discontinuation timing, overstock/understock risk, and recommendations tied to broader merchandising strategy (with room to grow into deeper merch collaboration as the team scales)
- Process & methodology improvement: Identify and implement improvements to forecasting models, planning cadences, and tools as the team's complexity grows
- Strategic analysis: Contribute ad hoc analysis supporting business-wide decisions (assortment, channel investment, inventory strategy)
Requirements
- 5–7 years of experience in demand planning, merchandising planning, or forecasting, ideally with prior experience in a formal planner-type role
- Experience with B2B/non-DTC planning is a strong asset (account-based, pipeline-driven, or lumpy-demand forecasting)
- Comfort operating strategically and upstream — someone who can
for prose. Remove boilerplate. Preserve all substantive info. We need to include About Branch? The posting includes "About Branch" but that's likely boilerplate? It's about company description. Might be considered substantive? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About Branch is company overview, not boilerplate. Should we keep? It's part of the posting. Probably keep as a section? There's no heading for About Branch in the list of allowed headings; but we could treat it as a paragraph under maybe no heading? The instruction says 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. Probably we should only include those headings if content exists. About Branch could be considered "About the role"? No. Could be a separate section but not in list; maybe we should not create a heading for it, just include as a
before the role section? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid other headings, but they gave examples. Safer to include About Branch as a
without heading, or maybe as a
About Branch? Not in list but could be okay. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are the expected headings; we should stick to them. So we should not create a heading for About Branch; we can include its content as a
before the role section. Thus structure:
About Branch ...
About the role
...
Then maybeResponsibilities
with list of what you'll own. ThenRequirements
with what you bring (experience). Could also split into Qualifications? But we have "What You Bring" includes experience and skills. We'll treat as Requirements. ThenSkills
with Technical Skills list. ThenPay
with compensation range. No Benefits, Schedule. Make sure to preserve all details. Let's extract content. About Branch paragraph: "Branch is shaking up the $46B office products industry to create the best work experience for the 21st century: easy, affordable and adaptable so you can sit down (or stand) and get to work. Most people spend eight hours a day at their workspace. Our mission is creating accessible and inspiring products to help people and teams feel their best at work, wherever that happens. We're based in NYC and Toronto, and backed by the investors behind Quip, Caraway, Eight Sleep and Peloton. Our culture combines strategic clarity with scrappy execution; we think and plan rigorously but ship fast and have fun doing it. We're looking for entrepreneurial teammates who do the same." About The Role paragraph: "We're growing our Forecasting & Planning team to support the business's increasingly complex channel mix — most notably our rapidly scaling Enterprise/B2B business. This role sits upstream of tactical execution, focused on strategic demand planning, cross-functional partnership, and channel-specific ownership. You'll partner closely with the Senior Manager and a Forecasting Analyst to build the planning function's next chapter. This role is salaried with a compensation range of $85,000-$95,000 based on the candidate's experience, skills, competencies, qualifications and market." What You'll Own bullet points (list). Need to preserve each line. Let's list them: - Enterprise/B2B channel planning: Serve as the primary forecasting and planning owner for the Enterprise channel, partnering directly with Sales and Account Management to translate pipeline and account-level signals into demand forecasts - Strategic demand planning: Own the higher-level forecasting methodology and assumptions feeding the overall revenue forecast (DTC, Enterprise, Amazon, Wholesale), stepping back from day-to-day tactical placement to focus on scenario planning, risk-flagging, and forecast accuracy improvement - Tooling & automation: Build and maintain BigQuery-based data pulls, automate recurring reporting/forecasting workflows, and apply AI tools to speed up analysis — reducing manual, spreadsheet-dependent processes over time - S&OP-style cross-functional partnership: Represent planning in cross-functional forecast reviews with Sales, Finance, and Product; translate business context into planning assumptions and vice versa - New product introduction (NPI) planning: Partner with Product Development on demand forecasting for new launches, building forecast logic for products with no historical sell-through - Product lifecycle strategy: Own the strategic view of lifecycle management — discontinuation timing, overstock/understock risk, and recommendations tied to broader merchandising strategy (with room to grow into deeper merch collaboration as the team scales) - Process & methodology improvement: Identify and implement improvements to forecasting models, planning cadences, and tools as the team's complexity grows - Strategic analysis: Contribute ad hoc analysis supporting business-wide decisions (assortment, channel investment, inventory strategy) What Success Looks Like bullet points: - Shared Accountability With The Team On MAPE: ≤10% across all channels (with specific ownership of Enterprise channel accuracy) - In-Stock Rate: 95% combined / 98% on Enterprise All-Star SKUs / 98% on Top 5 SKUs - DIO: contributing to inventory efficiency through better upstream forecast quality - Average Parcel Zone: supporting network/inventory placement decisions that improve transit speed and cost What You Bring bullet points: - 5–7 years of experience in demand planning, merchandising planning, or forecasting, ideally with prior experience in a formal planner-type role - Experience with B2B/non-DTC planning is a strong asset (account-based, pipeline-driven, or lumpy-demand forecasting) - Comfort operating strategically and upstream — someone who can build a point of view on "what should the forecast assume" rather than just executing against a set plan - Strong cross-functional communication skills; comfortable presenting forecasts and recommendations to non-planning stakeholders - Bonus: experience with NPI forecasting or product lifecycle management Technical Skills (high priority) bullet points: - BI tools: Advanced proficiency in Power BI, Tableau, or Looker — building dashboards and reports from scratch, not just consuming them - SQL / BigQuery: Comfortable writing and optimizing queries to pull and model data directly from the warehouse, reducing dependency on other teams for data access - Automation: Track record of automating manual, repetitive planning processes (e.g., scripting recurring reports, automating data refreshes, building repeatable forecast pipelines) rather than rebuilding spreadsheets each cycle - AI/LLM tools: Hands-on experience applying AI tools (e.g., Claude, ChatGPT, Copilot, or similar) to accelerate analysis, generate code/scripts, summarize data, or build forecasting logic - Advanced Excel: Experience with complex modeling, but not the primary tool for scaled work - Python or similar scripting experience is a strong asset, particularly for automation or forecast modeling Pay: "This role is salaried with a compensation range of $85,000-$95,000 based on the candidate's experience, skills, competencies, qualifications and market." We already mentioned that in About The Role paragraph; but we need to include Pay section with that detail. Avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include the pay info somewhere. It appears in About The Role paragraph already. We could keep it there and also have Pay section? Might duplicate. Better to keep it in Pay section and maybe remove from About The Role paragraph? But that would remove substantive info from that paragraph. However we could keep the sentence about salaried with compensation range in About The Role paragraph and also have Pay section repeating it; that would be duplication, which we should avoid per instruction: "Remove ... duplicated lines". So we should not duplicate. We need to decide where to place it. The About The Role paragraph currently includes that sentence. If we move it to Pay section, we need to remove it from About The Role paragraph to avoid duplication. That's okay as long as we preserve the info elsewhere. So we will edit About The Role paragraph to exclude the compensation sentence, and then add Pay section with that sentence. Thus About The Role paragraph becomes: "We're growing our Forecasting & Planning team to support the business's increasingly complex channel mix — most notably our rapidly scaling Enterprise/B2B business. This role sits upstream of tactical execution, focused on strategic demand planning, cross-functional partnership, and channel-specific ownership. You'll partner closely with the Senior Manager and a Forecasting Analyst to build the planning function's next chapter." Now Pay section: "This role is salaried with a compensation range of $85,000-$95,000 based on the candidate's experience, skills, competencies, qualifications and market.
" Now ensure we keep all other details. Now produce HTML. We'll wrap sections in appropriate tags. Let's craft:About Branch ...
About the role
We're growing our Forecasting & Planning team to support the business's increasingly complex channel mix — most notably our rapidly scaling Enterprise/B2B business. This role sits upstream of tactical execution, focused on strategic demand planning, cross-functional partnership, and channel-specific ownership. You'll partner closely with the Senior Manager and a Forecasting Analyst to build the planning function's next chapter.
Responsibilities
- Enterprise/B2B channel planning: Serve as the primary forecasting and planning owner for the Enterprise channel, partnering directly with Sales and Account Management to translate pipeline and account-level signals into demand forecasts
- Strategic demand planning: Own the higher-level forecasting methodology and assumptions feeding the overall revenue forecast (DTC, Enterprise, Amazon, Wholesale), stepping back from day-to-day tactical placement to focus on scenario planning, risk-flagging, and forecast accuracy improvement
- Tooling & automation: Build and maintain BigQuery-based data pulls, automate recurring reporting/forecasting workflows, and apply AI tools to speed up analysis — reducing manual, spreadsheet-dependent processes over time
- S&OP-style cross-functional partnership: Represent planning in cross-functional forecast reviews with Sales, Finance, and Product; translate business context into planning assumptions and vice versa
- New product introduction (NPI) planning: Partner with Product Development on demand forecasting for new launches, building forecast logic for products with no historical sell-through
- Product lifecycle strategy: Own the strategic view of lifecycle management — discontinuation timing, overstock/understock risk, and recommendations tied to broader merchandising strategy (with room to grow into deeper merch collaboration as the team scales)
- Process & methodology improvement: Identify and implement improvements to forecasting models, planning cadences, and tools as the team's complexity grows
- Strategic analysis: Contribute ad hoc analysis supporting business-wide decisions (assortment, channel investment, inventory strategy)
Requirements
- 5–7 years of experience in demand planning, merchandising planning, or forecasting, ideally with prior experience in a formal planner-type role
- Experience with B2B/non-DTC planning is a strong asset (account-based, pipeline-driven, or lumpy-demand forecasting)
- Comfort operating strategically and upstream — someone who can