Automation Analyst

Overview

Are you looking to do more than just the analytical work, gathering information, and making recommendations? Do you want to also build the tool, systems, process, etc. that you are working so closely with?

If you're an analyst who has spent the last year or two building things you couldn't have built alone before because Claude, Cursor, or Codex closed the gap this role is designed for you!

We have partnered with an client that is truly investing in its technology and teams as they fully believe, with the right people and the right tools, they can shape the future of their business.

Current state:
They have already invested in automated process discovery tooling, so the raw picture of how work flows through this company is being captured for you. They also have a substantial portfolio of RPA automations in production that you'll help inherit. Some are excellent, some are brittle, some probably shouldn't exist.

Your job spans both ends. Discovery software shows what people do; it can't tell you why or which exception matters. That takes someone who will sit with users and ask the third and fourth question. Then you take what you learned and ship the automation yourself.

• Interview and observe the humans doing the work. Run discovery sessions, workshops, and side-by-side walkthroughs. Dig past the first answer and surface the exceptions, workarounds, and edge cases that tooling alone won't reveal
• Build the automations. Workflow orchestration, RPA, scripts, integrations, AI-assisted steps you're expected to deliver working automation, not just specify it. You'll pull in engineering for the genuinely hard problems, not the routine ones
• Turn process discovery output into a prioritized, quantified backlog: what it costs today, what it costs to fix, what's the ROI
• Help own existing RPA portfolio: understand what each automation does and for whom, fix what's brittle, document what's undocumented, and retire what no longer earns its keep
• Write the requirements: user stories, acceptance criteria, exception paths, and the failure modes everyone forgets until go-live
• Own reliability for what you ship: monitoring, error handling, and runbooks
• Manage the change: bring affected teams along, train them, and make sure the new process actually sticks
• Measure what shipped against what you promised, and report it honestly

• You build, not just document. Point to automations, tools, scripts, or workflows that exist and are used.
• Serious hands-on AI tooling experience. You work regularly in tools like Claude, Claude Code, Cursor, or Codex using them to write and debug real working code, not to draft emails. You know how to decompose a problem for a model, when to trust the output, and where it will confidently hand you garbage
• Real analyst chops. You can run a discovery session, elicit requirements from someone who's never written one, and turn a vague complaint into a defined problem with a number attached. You ask the follow-up question
• Technical fluency.
  REST APIs, JSON, webhooks, SQL, and scripting in Python or Java Script . You should be able to read an API doc, authenticate against it, and get data moving without help
• You automate your own work. You've built the script, the macro, the workflow that saved you several hours a week and then you built four more
• Genuine curiosity about how work gets done. The best insight in this job usually comes from watching someone's screen for twenty minutes, not from reading a process doc
• Willingness to maintain, not just build. A meaningful share of year one is understanding and improving someone else's work. If that sounds like a chore rather than a puzzle, this isn't the right fit
• Systems thinking about people. You can talk to finance about their…