Business Operations

Role Overview

BizOps at FSH owns the problems that nobody else owns yet. In practice, some examples may include:

Growth - We sell to local governments, and public procurement is a specific and learnable process. You'll own the machinery and experimentation of this workflow end-to-end, including RFP bid responses, new pipeline development, pricing, and anything else that is critical to our ongoing distribution.

Systems - We are a small team often serving institutions far larger than us. That only works if our internal systems are excellent and scalable. You'll own these systems, working closely with our engineers and leadership to not only establish processes but also to build the tools that enable them.

This role is deliberately open-ended and fit for a generalist. When something important is unowned and on fire, you’ll be one of the first people we ask. You will work directly with the leadership team and see the whole business, and the ceiling on what you can do/own is set by what you demonstrate day-to-day.

What You'll Do

• Own our government growth engine end-to-end, including market research, pipeline development, etc.
• Write and assemble bid responses alongside our capture team, constantly identifying areas for improvement and efficiency
• Build internal tools and automations that give a small team outsized reach
• Own the data and run the analyses that drives team decision-making (e.g. pipeline, delivery metrics, market sizing, expansion, etc.)
• Take on high-priority ambiguous projects with little prescription for how to solve them
• Ideally, in any project you own, you make yourself unnecessary. Every process you build should end up running without you so you can go tackle the next problem.

What You'll Need

• 1-4 years of experience in a role that demanded high output: management consulting, investment banking, private equity, a founder or early-employee role, or something comparable.
• Technical ability. You should be able to pull your own data, write your own SQL, script your way out of a repetitive problem, and read enough code to have a useful conversation with an engineer. You will not be expected to write production code but you should be able to build tools by yourself.
• Strong analytical instincts. You think in numbers and data models, and you can produce a defensible answer fast when the situation calls for it.
• Excellent writing and communication skills
• Comfort with ambiguity and a strong bias toward action

Nice to Have

• A CS, engineering, math, or other technical degree - or a self-taught equivalent
• A history of building tools or products for your own use. Side projects, internal tools you built at a job, open source contributions, etc.
• Experience founding or working in an early-stage startup or other fast-moving environment.
• Familiarity with state and local government, public procurement, or other complex institutional buyers.

Employees are expected to live in New York City or Philadelphia and work out of our office in either location.