Regional Vice President, Ground Operations
Veho · Avenel, NJ · 3 wk ago
On-siteManagement$200k–$210k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay, Schedule maybe. Must include only sections with real content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
First part: "About Veho" is company description; we can maybe include as part of About the role? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content.
We have "About The Role:" paragraph describing role. That's suitable for About the role section.
Responsibilities: list of bullet points after "Responsibilities". We'll put those in
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content.
We have "About The Role:" paragraph describing role. That's suitable for About the role section.
Responsibilities: list of bullet points after "Responsibilities". We'll put those in - .
Requirements/Qualifications: There's "What You Bring" which lists qualifications: Bachelor's degree..., Minimum of 10+ years..., Success..., Deep expertise..., Experience leveraging..., Exceptional analytical..., Excellent communication..., Demonstrated ability... That's qualifications. Also "Preferred Qualifications" separate list. Could combine under Requirements or Qualifications. The instruction says use headings like Requirements, Qualifications, Skills. We can decide to have Requirements (mandatory) and Preferred Qualifications (maybe as Qualifications). But we need to avoid thin sections. Could combine both under "Qualifications". Or have "Requirements" for mandatory and "Preferred Qualifications" as separate but that may be thin? It's okay if content is substantive.
We also have "Compensation" section with pay range and benefits. There's also mention of "The pay range is subject to the discretion of the Company." plus benefits: competitive equity package, comprehensive medical, dental, vision coverage, 401k, unlimited PTO for exempt level roles. Also later repeats. We'll include Pay and Benefits sections.
Schedule: There's "This role requires 50%+ travel." That's schedule/travel requirement. Could be under Schedule section. We'll include Schedule with that line.
We must not include boilerplate like "All California applicants..." etc. Also remove duplicated lines like repeated compensation text.
We must preserve all substantive information. Ensure we don't lose any details.
Let's extract content.
About the role paragraph:
"Veho is seeking a highly experienced, strategic, and results-oriented leader to serve as the Regional VP of Ground Operations. In this pivotal role, you will have comprehensive oversight of Veho's ground operations network, driving strategic direction, operational excellence, and continuous improvement across our warehouse and logistics infrastructure. You will be responsible for both the tactical performance and long-term strategic evolution of our operations and 3PL partners, collaborating closely with cross-functional teams to leverage technology and optimize performance. This role is critical to enabling Veho's strategic growth, enhancing service quality, and achieving key cost objectives within a fast-paced, rapidly scaling environment."
That's the About the role.
Responsibilities list (after "Responsibilities"):
- Define, develop, and execute the long-term strategic vision and tactical operational plan for Veho's ground operations network, ensuring alignment with overall company objectives and enabling rapid scalability as the business expands.
- Provide hands-on leadership and oversight of all facets of ground operations, including warehousing, sortation, logistics, and last-mile delivery processes, focusing on safety, quality, service, and productivity.
- Drive strategic initiatives for network evaluation and expansion, capacity planning, and infrastructure development adeptly managing within ambiguity and developing scalable processes to support hyper-growth.
- Champion a culture of high performance, accountability, ownership, continuous improvement, and innovation, utilizing data and operational methodologies to identify opportunities for efficiency gains, cost reduction, and enhanced performance.
- Collaborate closely with cross-functional teams to identify, evaluate, and implement advanced technology, AI, and automation solutions that optimize operational processes.
- Establish, monitor, and analyze key performance indicators (KPIs) and financial metrics to evaluate operational performance, identify trends, and provide insightful reporting with executive-level communication acumen.
- Lead, mentor, and develop a high-performing team, including managing leaders of leaders, fostering a culture of accountability, collaboration, and excellence.
- Ensure robust risk management practices are in place, overseeing a strong safety culture, security protocols, regulatory compliance, and environmental standards.
- Manage operational budgets effectively, driving cost optimization initiatives while maintaining high levels of service quality and operational reliability.
- This role requires 50%+ travel. (Actually this is under responsibilities but we might move to Schedule.)
We'll keep travel in Schedule.
Now "What You Bring" (mandatory qualifications):
- Bachelor's degree in Business, Logistics, Supply Chain Management, Engineering, or a related analytical field; MBA or Master's degree preferred.
- Minimum of 10+ years of progressive leadership experience in ground operations, warehousing, logistics, or last-mile delivery, with a proven track record of scaling operations in a high-growth or start-up environment.
- Success in developing and executing strategic operational initiatives that resulted in significant improvements in efficiency, cost-effectiveness, and service levels.
- Deep expertise in logistics and supply chain management principles, with specific in-depth knowledge of last-mile delivery operations and network optimization.
- Experience leveraging and implementing advanced logistics technology solutions, including Warehouse Management Systems (WMS), transportation management systems (TMS), automation, and data analytics platforms.
- Exceptional analytical, problem-solving, and decision-making skills, with a strong ability to utilize data and insights to inform strategy and drive action, particularly in ambiguous situations.
- Excellent communication, negotiation, and interpersonal skills, with a demonstrated ability to influence, collaborate, and build relationships at all levels of the organization, including executive leadership.
- Demonstrated ability to thrive and lead effectively in a fast-paced, dynamic, and evolving business environment.
Preferred Qualifications:
- Proven ability to translate complex data into clear, actionable insights for strategic decision-making.
- Experience leveraging Artificial Intelligence (AI) or machine learning concepts to optimize logistics and warehouse operations.
- Proximity or ability to relocate within driving distance to key Veho markets to facilitate frequent site visits and hands-on leadership.
Compensation:
- "$200,000 - $210,000 annually The pay range is subject to the discretion of the Company." Also later "Compensation Range: $185K - $220K". There's some discrepancy. We need to preserve all substantive info; we should include both mentions? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include both ranges as they appear. However they may be considered duplicated? They are not exactly same; first says $200k-$210k, second says $185K-$220K. We should keep both. Could combine as two separate statements.
Benefits:
- "Additionally, Veho offers a competitive equity package, comprehensive medical, dental, and vision coverage as well as other benefits such as 401k and unlimited PTO for exempt level roles."
- Later repeats: "Additionally, Veho offers a competitive equity package, comprehensive medical, dental, and vision coverage, and other benefits such as a 401 (k) and unlimited PTO for exempt-level roles."
We'll include benefits once but preserve details: competitive equity package, comprehensive medical, dental, and vision coverage, 401k, unlimited PTO for exempt-level roles.
Schedule:
- "This role requires 50%+ travel."
We could also mention any other schedule info? Not present.
Now we need to output HTML fragment with headings
and content.
We should not include any extra text outside HTML.
We'll structure:
About the role
...
Responsibilities
- ...
...
Qualifications
Maybe split into Requirements and Preferred Qualifications? But we can have one Qualifications section with two sublists? The instruction says use headings like Requirements, Qualifications, Skills. We could have Requirements
for mandatory, and Preferred Qualifications
for preferred. That's two sections. Both have substantive content.
We'll do:
Requirements
...
Preferred Qualifications
...
We could also have Skills but not needed.
Benefits
...
or ...
. Since it's a list of benefits, we can use .
Pay
... (include both ranges)
Schedule
This role requires 50%+ travel.
Make sure not to include empty sections.
Now we need to ensure we didn't miss any substantive info: The company description "About Veho" maybe not needed as per instruction: we should not repeat job title as heading, but we can include company description as part of About the role? The About the role section already includes role description; we could also include a brief company overview as part of About the role? The instruction says use for section headings (e.g. About the role, Responsibilities...). It didn't forbid including company description in About the role. However the "About Veho" paragraph is generic company mission; it's substantive but not about the role. Could we include it as a separate section like "About the company"? Not in allowed headings list. Could we incorporate it into About the role? Might be okay but could be considered not strictly about the role. However 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 the examples are those. Safer to stick to those headings. We could include company description in About the role as a preamble? Might be considered adding unrelated content but it's still substantive and not prohibited. However the instruction says "Prefer a few substantive sections over many thin ones." Including company description may make About the role longer but still okay.
Alternatively we could omit the About Veho description entirely, as it's not required for the role. The instruction says preserve ALL substantive information; does that include company description? It is substantive information about the company. If we drop it, we lose info. So we should include it somewhere. Since we don't have a heading for company, we could put it in a
before the first heading? The instruction says output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have stray
outside headings. But they likely expect sections with headings. However we could include a
about Veho before the first heading. That would preserve info. Let's do that: a
containing the Veho mission description. Then headings.
Thus output:
Veho’s mission is to power the future of commerce by making shopping, shipping and returns seamless for everyone. We are building a modern, end-to-end logistics infrastructure designed entirely for the ever-evolving needs of ecommerce brands and everyday consumers. Powered by next-generation technology and a vertically integrated supply chain, Veho gives brands and their customers unprecedented control over their deliveries and removes the pain from the ecommerce post-purchase experience. We make delivery the ‘extension of the brand’ and leverage it to create deeper loyalty and trust between brands and their customers, driving customer retention and lifetime value. Our rapidly growing client list includes leading consumer brands like HelloFresh, Zara, Macy’s, Sephora, and more. To truly build an iconic company, we strongly believe that our people and values must be aligned with our mission. As such, we take pride in our championship team, merit-based culture. We seek team players who want to compete, win, make an impact and build a legacy, and we reward performance and impact players with generous equity and incredible career growth opportunities.
Then headings.
Now ensure we don't repeat any boilerplate like
and content.
We should not include any extra text outside HTML.
We'll structure:
About the role
...
Responsibilities
- ... ...
Qualifications
Maybe split into Requirements and Preferred Qualifications? But we can have one Qualifications section with two sublists? The instruction says use headings like Requirements, Qualifications, Skills. We could haveRequirements
for mandatory, andPreferred Qualifications
for preferred. That's two sections. Both have substantive content. We'll do:Requirements
- ...
Preferred Qualifications
- ...
Benefits
- ...
...
. Since it's a list of benefits, we can use- .
Pay
... (include both ranges)
Schedule
This role requires 50%+ travel.
Make sure not to include empty sections. Now we need to ensure we didn't miss any substantive info: The company description "About Veho" maybe not needed as per instruction: we should not repeat job title as heading, but we can include company description as part of About the role? The About the role section already includes role description; we could also include a brief company overview as part of About the role? The instruction says use for section headings (e.g. About the role, Responsibilities...). It didn't forbid including company description in About the role. However the "About Veho" paragraph is generic company mission; it's substantive but not about the role. Could we include it as a separate section like "About the company"? Not in allowed headings list. Could we incorporate it into About the role? Might be okay but could be considered not strictly about the role. However 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 the examples are those. Safer to stick to those headings. We could include company description in About the role as a preamble? Might be considered adding unrelated content but it's still substantive and not prohibited. However the instruction says "Prefer a few substantive sections over many thin ones." Including company description may make About the role longer but still okay.
Alternatively we could omit the About Veho description entirely, as it's not required for the role. The instruction says preserve ALL substantive information; does that include company description? It is substantive information about the company. If we drop it, we lose info. So we should include it somewhere. Since we don't have a heading for company, we could put it in a
before the first heading? The instruction says output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have stray
outside headings. But they likely expect sections with headings. However we could include a
about Veho before the first heading. That would preserve info. Let's do that: a
containing the Veho mission description. Then headings. Thus output:
Veho’s mission is to power the future of commerce by making shopping, shipping and returns seamless for everyone. We are building a modern, end-to-end logistics infrastructure designed entirely for the ever-evolving needs of ecommerce brands and everyday consumers. Powered by next-generation technology and a vertically integrated supply chain, Veho gives brands and their customers unprecedented control over their deliveries and removes the pain from the ecommerce post-purchase experience. We make delivery the ‘extension of the brand’ and leverage it to create deeper loyalty and trust between brands and their customers, driving customer retention and lifetime value. Our rapidly growing client list includes leading consumer brands like HelloFresh, Zara, Macy’s, Sephora, and more. To truly build an iconic company, we strongly believe that our people and values must be aligned with our mission. As such, we take pride in our championship team, merit-based culture. We seek team players who want to compete, win, make an impact and build a legacy, and we reward performance and impact players with generous equity and incredible career growth opportunities.
Then headings. Now ensure we don't repeat any boilerplate like