[Hiring] Business Operations Manager @IREN

Role Description

We are hiring a Business Operations Manager to run the business of Cloud Operations and SRE, and to work 1:1 with the VP who leads it. One role, two halves that reinforce each other: you own how the org plans, reports and follows through, and you own the executive’s time, attention and follow-through as a system you design and continuously improve.

What This Role Actually Is:

• A business operations owner: You run the planning and reporting spine of the org: goals and OKRs, the roadmap, the cross-functional programs, and the metrics that say whether Cloud Operations and SRE are healthy. You know the numbers before anyone asks for them, and you chase down the ones that do not make sense.
• A program driver: For initiatives that cross teams, you own the plan, the dependencies, the risks and the uncomfortable status update. Nobody should have to ask “what happened with that?”
• An operator: You will run the operating cadence: staff meetings, business reviews, planning cycles, offsites. You will run these end to end: agenda, pre-reads, decisions captured, owners assigned, follow-ups driven to closure.
• A force multiplier to the executive: The executive support half of this job is a core part of it, not a legacy attachment. You will own the VP’s calendar, inbox, travel and follow-through, and you will make decisions on their behalf inside clearly defined boundaries widening those boundaries as trust compounds.
• An org operations partner: Headcount and requisition tracking, hiring loops, onboarding that does not depend on tribal knowledge, team communications, and offsites you own outright.
• An automation builder: Every recurring task you touch is a candidate for an agent. Weekly reports, status roll-ups, meeting prep briefs, inbox triage and drafting, travel logistics, expense reconciliation, doc hygiene — you build it once, monitor it, and move on to the next thing.
• A judgment layer: Automation is cheap; taste is not. You will know which emails only the executive can answer, which meeting genuinely needs 60 minutes, which “urgent” request can wait until Thursday, and which agent output is subtly wrong and must never go out the door.

Qualifications

• 5 or more years in business operations, program management, chief-of-staff or senior executive support roles, including direct experience supporting a senior executive, and at least some of it in a fast-moving, high-ambiguity environment (startup, scale-up, or a team inside a larger company operating like one).
• Genuinely AI-native. You use AI assistants and agentic tools every day, not occasionally. You can describe — in specifics — a workflow you automated, what broke, and how you fixed it.
• Hands-on with agentic tooling. Personal AI agents and assistants for calendar, inbox and scheduling; general-purpose assistants (Claude, ChatGPT, Gemini) as daily drivers; and connective tissue between systems.
• The ability to run a cadence and a program. Agendas, pre-reads, decision logs, status that is honest when it is bad.
• Comfort with numbers. You can build a reporting roll-up, spot the metric that is lying, and explain a trend to leadership without dressing it up.
• Judgment under incomplete information, or with swinging-door outcomes.
• Instinctive discretion. You will sit close to board material, compensation, org changes and unannounced strategy.

Requirements

• Nice to have: You have built something small and useful with low-code tools — a script, a dashboard, a bot — because it was faster than asking.
• You have run a planning or OKR cycle for a technical org and lived with the result.
• You have been given scope beyond a traditional remit: a project, a budget, a vendor relationship, a team offsite you owned outright.
• Experience in an org where AI adoption was a stated strategy, not a pilot.
• Comfort with data infrastructure, energy, or high-growth technical businesses.
• You have opinions about which tools are overrated.
• You know how to speak clanker.

Benefits

• You want a stable, predictable week.
• You prefer to be told exactly what to do.
• You expect the executive-support half of this role to disappear once the operations half gets interesting. Both are the job.
• “That’s not my job” is in your vocabulary.