Jobs · OTHR · Missouri

VP of Strategy and Operations

Kanbrick · Springfield, MO · 3 wk ago
On-siteOTHRFull-time
We need to produce HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes description of role, responsibilities, requirements, benefits. No explicit Pay or Schedule. So we include sections: About the role (maybe from "The Role" paragraph), Responsibilities (the "What You'll Do" bullet list), Requirements (the "How You'll Lead" and "Requirements" sections), Benefits (the "Benefits" paragraph). Possibly also "Qualifications" but we can merge with Requirements. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need sections: About the role (the paragraph after "The Role"), Responsibilities (the "What You'll Do" list), Requirements (the "How You'll Lead" and "Requirements" paragraphs), Benefits (the "Benefits" paragraph). Possibly also "Qualifications" but we can combine with Requirements. The instruction says we can use those headings; we can choose to not duplicate. We'll include About the role, Responsibilities, Requirements, Benefits. We need to preserve all substantive information. Must not invent or summarize away detail. So we need to keep the text exactly? Probably we can paraphrase but must preserve meaning. Safer to copy the substantive sentences as is, but we can break into

    and

    • . Must not include boilerplate like EEO etc. Also remove duplicated lines. Let's extract content. First paragraph: "At Keep Supply, we're in the business of solving problems — fast. Based in Springfield, Missouri, we're a growing team of people who supply industrial refrigeration parts to customers across the country. When someone's system goes down at 2 AM, we're the ones picking up the phone. When a hard-to-find part seems impossible to track down, we figure it out. That's just what we do. We're rapidly growing — and the reason our customers stick with us comes down to something pretty simple: we genuinely care, and it shows. We operate using Open-Book Management through the Great Game of Business®. That means our team understands how the business is performing, how their work contributes to the results, and how we all share in the success. We are a fast-moving, operationally sharp team built on the belief that great work speaks for itself. We're in the business of supply — and we take that seriously, from the products we source to the people we put on the floor. Our culture runs on six principles: be a pro, give your best, be humble, assume the best, be part of the solution, and best to deal with it. No corporate fluff. No half-measures. Just a team that shows up, does the work, and holds each other to a high standard. At the heart of Keep are a simple Why and Mission that guide how we think about our business, our customers, and our people: Our Why: We believe Keep can be an impactful platform that makes lives better. Our Mission: Be the best part." That's about company overview. Could be "About the role"? Actually "About the role" is supposed to describe the role, not company. But we have a section "The Role" after that. The instruction says use

      for section headings (e.g. About the role, Responsibilities...). So we need an "About the role" section that describes the role. The posting has a section "The Role" with paragraphs: "You'll help the CEO and the leadership team determine where to focus, bring structure to ambiguous opportunities and problems, and translate the highest-value priorities into action. You'll ask the questions that sharpen strategy before the organization jumps to a solution: What are we really trying to accomplish? What assumptions are we making? What are the trade-offs? What should we test before we go big? Your job is to improve the quality of decisions and execution as Keep grows. You'll serve as a strategic thought partner across the leadership team, help leaders scope and prioritize important work, and take on a small number of high-value initiatives that do not naturally sit within one function. Turn strategy into an operating rhythm. You'll help translate strategic choices into quarterly priorities, clear ownership, measurable outcomes, and the management cadence that keeps the organization focused and learning. The meetings, dashboards, and follow-up matter because they create visibility, strengthen decision-making, and keep the company aligned on what matters most. Raise the bar through influence. Your job is bigger than owning one function. You'll work alongside leaders as a trusted thought partner, helping them frame problems, evaluate options, and build stronger planning and problem-solving muscles over time. You know when to challenge, when to support, and when to simply roll up your sleeves and get something done." That is the role description. So we can put that under

      About the role

      with paragraphs. Then Responsibilities: The "What You'll Do" section with bullet points: "Shape Strategy and Priorities", "Incubate Strategic Initiatives", "Run the Operating System", "Measure and Improve". Each has sub-bullets. We need to output
      • for any list of duties/requirements/benefits. So we can create a top-level
          with each responsibility as
        • and inside each we can have nested
            for subpoints? The instruction didn't forbid nested lists. We'll keep simple: each responsibility as
          • and include its subpoints as separate sentences within the
          • maybe separated by semicolons or
            . But better to keep as
            • with internal
                . That's still valid HTML. We'll do that. Then Requirements: The "How You'll Lead" section (leadership principles) and the "Requirements" section (Who We're Looking For). Also maybe "Why Keep Supply" but that's more about why join. Could be considered "Benefits"? Actually there is a separate Benefits section later. The "Why Keep Supply" is about impact, autonomy, etc. Could be considered part of "Benefits" or "About the role"? But we already have Benefits section for compensation & benefits. The "Why Keep Supply" is more about the role's impact. Could be included under About the role or as a separate section like "Why Join". But instruction only lists certain headings; we can add others? It says use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Safer to stick to those. The "Why Keep Supply" could be considered part of Benefits? Not exactly. Could be omitted? But we must preserve ALL substantive information. So we need to include that info somewhere. Could be placed under About the role as additional paragraph. Or we could create a section "Qualifications" but that's not accurate. Maybe we can incorporate into Requirements as "Leadership expectations". The "How You'll Lead" is basically leadership principles; that's part of requirements. The "Why Keep Supply" is more about the opportunity; could be part of About the role. We'll add it as a paragraph after the role description. Then Requirements: We'll combine "How You'll Lead" and "Who We're Looking For" into a Requirements section with lists. Then Benefits: The paragraph under "Benefits Compensation & Benefits": "We think work should feel good. That means covering 100% of medical, dental, and vision for you and your family, offering unlimited PTO, and building a workplace where people actually want to show up every day. We would love to share more in conversation." Also there is an EEO line after that which we must remove. So we keep only the benefits paragraph. We must not include Pay or Schedule sections because not specified. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role:

                About the role

                You'll help the CEO and the leadership team determine where to focus, bring structure to ambiguous opportunities and problems, and translate the highest‑value priorities into action. You'll ask the questions that sharpen strategy before the organization jumps to a solution: What are we really trying to accomplish? What assumptions are we making? What are the trade‑offs? What should we test before we go big? Your job is to improve the quality of decisions and execution as Keep grows. You'll serve as a strategic thought partner across the leadership team, help leaders scope and prioritize important work, and take on a small number of high‑value initiatives that do not naturally sit within one function. Turn strategy into an operating rhythm. You'll help translate strategic choices into quarterly priorities, clear ownership, measurable outcomes, and the management cadence that keeps the organization focused and learning. The meetings, dashboards, and follow‑up matter because they create visibility, strengthen decision‑making, and keep the company aligned on what matters most. Raise the bar through influence. Your job is bigger than owning one function. You'll work alongside leaders as a trusted thought partner, helping them frame problems, evaluate options, and build stronger planning and problem‑solving muscles over time. You know when to challenge, when to support, and when to simply roll up your sleeves and get something done.

                Why Keep Supply: Help shape what comes next. This isn't about optimizing a mature corporate machine. You'll help Keep decide where to focus, pressure‑test big opportunities, and build the capabilities that support the next decade of growth. Work where decisions happen. You'll partner directly with the President and leadership team, with the trust and autonomy to influence meaningful decisions across the business. Know the score. Through our Great Game of Business® philosophy, everyone understands how the business wins, and everyone has the opportunity to contribute to, and benefit from, that success. Build the leadership bench. You'll help strengthen how leaders across Keep plan, prioritize, solve problems, and execute as the business becomes larger and more complex. Grow alongside exceptional people. Backed by Kanbrick, our long‑term investment partner, you'll join a community of operators who are building enduring businesses, sharing ideas, and helping each other become better leaders.

                Now Responsibilities:

                Responsibilities

                • Shape Strategy and Priorities
                  • Partner with the CEO and functional leaders to frame important strategic questions and translate broad opportunities into clear choices
                  • Help leaders scope problems before jumping to solutions, identifying assumptions, alternatives, trade‑offs, and practical ways to test ideas
                  • Use data, research, and first‑principles thinking to surface insights, prioritize competing opportunities, and improve decision quality
                • Incubate Strategic Initiatives
                  • Take on a small number of high‑value, ambiguous initiatives that do not naturally sit within an existing function
                  • Lead the early discovery, analysis, testing, and business case development required to determine whether and how Keep should pursue an opportunity
                  • Bring emerging ideas to a point of clarity where the business can make an informed go, no‑

Similar jobs