Operations System Analyst

WHAT YOU MIGHT BRING TO THE TABLE

You don't need to tick all the boxes to apply for this role. Whether it's your first role or your fifth role, we believe everyone can add value, learn, and grow. However, these might be some of the ways you are currently adding value:

• Experience partnering closely with Product teams — you can translate operational pain points into clear requirements, and product changes into operational impact.
• You're hands-on with AI tools for analysis, scripting, and building automations — not just AI-aware, but someone who's actually shipped something with it.
• Experience administering CRM, ticketing, or workflow systems (e.g., Salesforce, HubSpot, Zendesk, Notion, or similar) in an operations context.
• Experience building reporting and dashboards that non-technical stakeholders can actually use.
• A track record of designing workflow automations that measurably reduce manual work.
• Strong analytical skills, comfortable turning messy operational data into a clear point of view.
• Experience developing training or supporting non-technical users on new systems and tools.
• Comfortable operating independently in a role that spans systems, data, and process, not just one of the three.
• A proactive, detail-oriented approach — you notice when something's off in the data before someone has to tell you.

WHAT YOU WILL ACHIEVE IN THIS ROLE

This role sits within Operations, reporting directly to the SVP of Operations. You'll own the administration of systems and tooling that power operations— CRM and workflow implementation, reporting and dashboards, and the automations that keep operational data accurate and usable across teams. This role is a key bridge between Product and Operations—you'll translate operational needs into system and product requirements, and product changes into operational impact, so the two move in lockstep instead of in parallel. Early on, your priority is collaborating with Product, auditing our current systems and reporting setup, fixing the most urgent data and process gaps, and building a roadmap side by side with Product teams for where automation can remove manual work across Operations. As a scale-up business, you can expect your role to develop over time. Here are some of the types of things you could be getting involved in:

• Own administration of our core operational systems (CRM, ticketing, workflow tools), including configuration, permissions, and data integrity.
• Build and maintain reporting and dashboards that give Service Delivery, Implementation, and leadership an accurate, real-time view of operational performance.
• Design and implement workflow automations that reduce manual work across Service Delivery and Implementation teams.
• Act as the key bridge between Product and Operations — translating operational needs into system and product requirements, and product changes into operational impact, so the two move in lockstep.
• Partner with Product and IT to scope, test, and roll out system changes that affect Operations.
• Troubleshoot system issues raised by ops teams and build a clear process for triaging and resolving them.
• Maintain clean, well-documented data across our operational systems, and own the standards that keep it that way.
• Train and support ops users on new systems, tools, and workflows as they roll out.
• Identify opportunities to apply AI and automation to recurring operational and reporting work, and pilot solutions directly.
• Use AI tools directly to build internal automations, scripts, and reporting logic — treating AI as a core part of how you ship systems work, not an occasional add-on.

AI REQUIREMENTS

At Scan.com, AI isn't a side project; it's how we work. We expect everyone to use AI to think faster, remove drudgery, and multiply their output. What we care about is judgment: knowing when AI makes you sharper, when it doesn't, and how to use it responsibly around patient data. You don't need to be an engineer. You need to be someone who reaches for the best tool and gets more done as a result.

Tier 1 — AI-Native: For this role, the expectation is that you are AI-Native. You build with AI directly, shipping, automating, or prototyping real work with LLMs and agents, and have clear judgment on where humans must stay in the loop. You build with AI, not just alongside it. You've shipped, automated, or prototyped something real using LLMs, agents, or AI tooling. You can explain a workflow you redesigned so a machine does the boring 80%. You have a view on where agentic systems help and where a human must stay in the loop, especially in regulated, PHI-adjacent work.