Downloads
Aug 20, 2026
Avionté is the operating system for staffing, housing two decades of comprehensive front and back-office data for our 800+ customers. We're building a new analytics platform that empowers agencies to self-service and turn that data into decisions that grow their business.
The role
You own the roadmap for analytics: what gets built, in what order, and why. You turn "customers want better reports" into specific, sequenced problems worth solving. You partner with engineering on trade-offs closely enough to make good calls without implementing them. You translate ambiguous customer signal into real problems worth solving.
We're less interested in BI tool experience than in whether you can walk into unfamiliar technical terrain, learn fast, and drive productive customer and business outcomes.
What you'll do
- Own and sequence the roadmap for analytics capabilities. Defend it to clients, sales, and customer-facing teams with reasoning they follow. You advocate for outcomes not features.
- Turn ambiguous customer signal into problem definitions. Requests are commonly expressed as solutions. Your job is to dig deeper, identify the jobs to be done, and clarify a specific problem statement by staying close to how staffing leaders and recruiters work.
- Partner with engineering on architecture trade-offs (pipeline latency, data modeling, platform choices) closely enough to make good calls without being the implementer.
- Work across boundaries (data engineering, front-end, customer success, sales). Pull in the right specialist instead of guessing or waiting.
What we're looking for
- You've built and delivered embedded data products sold to customers. You were the PM or primary builder. Your analytics are in production today, customers check them before decisions, and you know what it took to get there.
- Genuinely close to customers. You spend time with staffing leaders and recruiters—not collecting wish lists, but understanding their jobs to be done. You come back with a clear picture of what's broken, not a feature list. You kill your own ideas if they don't serve what customers need.
- Meaningful empathy grounded in specificity. You understand staffing: fill rates, margin math, velocity vs. quality, why redeployment matters. Staffing experience preferred. If not, you've shipped products into operationally-chaotic domains (logistics, supply chain, field services) where you drove efficiency. You see the gap between what customers need and what's built as your problem.
- Willing to get hands dirty as a co-builder. You build dashboards and prototype solutions yourself, not just spec them. You understand effective data visualization—making complexity clear, guiding the eye to what matters. You validate with real usage, fast. You hand off when it's time; hands-on because it's the fastest way to validate, not because you need to do everything.
- You own outcomes collaboratively. You drive results by bringing together the right people and holding space for good decisions. You're the connector who makes things move, and you do it with people, not around them.
Bonus, not gates
- Real depth in one or two technical areas (data modeling, semantic layers, BI architecture, API design, SQL reasoning). Not credentials—a track record of using depth to make better calls. You'll move faster in architecture conversations from day one.
- Hands-on experience with agentic coding tools (Claude Code, similar). You've used AI-assisted development to move fast and prototype. This signals you're comfortable with how we ship.
What this role is not
Though both are involved, this is not a pure strategy role and not a pure technical role. You build and prototype, not just plan and cast vision. You won't design the pipeline or create production views yourself, but you'll know enough to partner effectively with the people who do. You don't commission work and watch from the sidelines, you validate real customer problems and collaborate to ship solutions that deliver outcomes.
