Operations Analyst, Cross-Department

UtiliSave LLC

11d•$60,000 - $70,000•Remote

About The Position

We are looking for an Operations Analyst who will own how work moves between departments. You will start by sitting with each department, learning what they really do (which is often not what the org chart says), documenting it, and then fixing it. Some fixes are process changes. Some are just getting two teams to agree on who owns a handoff. You will run those changes as projects, with owners and dates, and you will be the person leadership asks for status. You report to the Technology Lead, and you work directly with the CEO and department leads.

Requirements

4–7 years in business operations, business analysis, process improvement, or project management, with real time spent establishing process rather than administering one that already existed.
Demonstrated experience mapping and documenting business processes, and getting a team to actually change how they work.
Track record running cross-functional projects with stakeholders who do not report to you, and getting them to commit to dates.
Hands-on with work-tracking tools — Jira, Azure DevOps, Asana, or similar — including board and backlog management.
Strong writing. You will produce process documentation, status summaries, and recommendations that a CEO reads closely.
Comfortable across technical and non-technical audiences. You do not need to code, but you need to hold your own with developers and then translate it for an auditor.
Solid with Microsoft 365 — SharePoint, Teams, Excel, Planner or To Do — and willing to learn Power Automate if you have not used it.
Direct, and comfortable with disagreement.

Nice To Haves

Process improvement training or credentials.
Project management certification (PMP, CAPM) or PMO experience.
Experience at a small or mid-sized company where the role spanned several departments rather than one function.
Power Automate, Power Apps, or building workflow automation without a developer.
Experience using AI tools in day-to-day work — drafting documentation, analyzing process data, summarizing meetings. We use Claude and Microsoft Copilot across the company.
Background in utilities, energy, professional services, or another data-heavy service business.

Responsibilities

Sit with each department, map how work actually flows today, and produce documented process for every team — including the handoffs, the exceptions, and the parts nobody has written down.
Find where work stalls between departments, propose the fix, get agreement from the people affected, and see it through to adoption. A documented process nobody follows does not count.
Run cross-functional projects end to end: scope, plan, owners, dates, dependencies, and follow-through. Keep them moving without needing to be chased.
Build the process infrastructure that makes work visible — SharePoint document libraries, shared task lists, intake forms, templates, and checklists. Light-weight tools people actually use, not a bureaucracy.
Facilitate recurring cross-department meetings. Set the agenda, run the discussion, capture decisions and owners, and make sure last week’s commitments get closed before new ones get made.
Track work in Jira and give leadership one reliable source for status — what moved, what is stuck, who owes what, and what is at risk.
Surface risks, blockers, and cross-team dependencies early, and drive them to a decision instead of parking them on a list.
Analyze where time and rework are going, and bring back a recommendation with numbers behind it rather than an impression.
Support change adoption: train teams on the new process, check whether it stuck 30 days later, and adjust it if it did not.
Keep documentation current as processes change, and prompt the owners when it drifts.