VP of Hardware and Software Development $200,000 USD/year Pay is set based on global value, not the local market.
Most roles = hourly rate x 40 hrs x 50 weeks
Not accepting applications on crossover.com at this time.
Description
You're the person who keeps a launch on the rails when the work is split across engineering, vendors, and a handful of tool owners who don't report to you. You hit the deadline. Then you do it again the next quarter, by hand, because no one ever built the system that would make it repeatable.
Most technical operations roles maintain infrastructure that already exists. This one builds the operating system for a school network that keeps adding campuses. Every new campus needs its devices provisioned, its SaaS access live, and its launch systems configured before day one. Your job is to make that happen across the teams who do the hands-on work, then automate the coordination so each launch runs faster than the last.
At first you get the launch playbook under control: clear owners, dependencies surfaced early, blockers driven to resolution before they threaten a date. As the campus cadence continues, the work changes shape. You turn documented procedures into AI agents, chain them into systems that run intake, handoffs, reporting, and follow-up in the background, and watch a launch that used to take days start taking hours. You aren't just running the launches. You're building the system that runs them.
If you want clear ownership, measured outcomes, and the pace of a growing network, we want to meet you.
What you will be doing
- Coordinating engineering teams, vendors, and SaaS and tool owners against agreed requirements plans, surfacing blockers early, and driving each owner to a clean handoff before the campus launch window
- Building AI agents from documented SOPs and chaining them into autonomous systems that run intake, provisioning, handoffs, reporting, and follow-up with human-in-the-loop checkpoints
- Translating ambiguous campus and business needs into requirements plans with named owners, timelines, and acceptance criteria
- Running the campus technology readiness playbook to confirm owner sign-off, and tightening it after every launch
- Coordinating hardware procurement, delivery timelines, and asset tracking with vendors so devices arrive on schedule and stay accurate
What you will NOT be doing
- Administering MDM (mobile device management), imaging, or enrolling devices yourself — a dedicated engineering team owns that execution
- Babysitting a ticket queue where success is measured by how many you close
- Sitting in coordination meetings that move no technical system and expect no ownership or build from you
- Drawing long-range architecture diagrams while launch dates slip
- Running the same manual launch coordination every quarter — you build the automations that make each one faster
Key responsibilities
Every campus opens and operates on schedule because its technology is provisioned and working before day one.
Candidate requirements
- Located in the United States and authorized to work in the US without visa sponsorship
- Willing and able to travel periodically to US campuses
- Have owned or led technical operations across at least two of these areas: device programs, SaaS and account administration, hardware procurement or asset tracking, site or campus launches, or communications tooling
- Have coordinated delivery across separate engineering, vendor, or business teams that did not report to you
- Have produced requirements or execution plans — with named owners, timelines, and acceptance criteria — that another team or vendor delivered against
- Have used AI tools, automation platforms, scripts, or no-code workflows to reduce manual operational work
- Have authored operational documentation such as SOPs, runbooks, playbooks, or launch checklists that others executed against
Nice to have
- Exposure to MDM or endpoint programs such as Jamf, Intune, Mosyle, or ManageEngine
- Experience running operations across a distributed, multi-site environment where inventory, spares, and repairs span locations
- Experience configuring communication tools such as Google Voice, Zoom Phone, or Zoom Rooms
- A track record of building simple automations that cut manual provisioning or reporting work
Applying for a role? Here’s what to expect.
Crossover's skill assessment process combines innovative AI power with decades of human research, to take the guesswork, human bias, and pointless filters out of recruiting high-performing teams.
Chat-style
screening interview.
Cognitive 
aptitude test.
Prove real-world 
job skills.
Interview with the hiring manager.
Pass
proctored test.
Accept job offer.
Frequently asked questions
Reviews
Meet some people who've landed similar jobs
Recruitment sucks. So we’re fixing it.
The Olympics of work
It’s super hard to qualify—extreme quality standards ensure every single team member is at the top of their game.
Premium pay for premium talent
Over 50% of new hires double or triple their previous pay. Why? Because that’s what the best person in the world is worth.
Shortlist by skills, not bias
We don’t care where you went to school, what color your hair is, or whether we can pronounce your name. Just prove you’ve got the skills.
Join the world's largest community of 
AI-first remote workers.