We're creating a new role to drive automation and AI adoption across the company. This isn't a developer position. It's a low-code and RPA-first role about solving business problems. You'll work across departments to find repetitive work, evaluate tools, build solutions yourself, and help people actually use them.
We care about the outcome, not the tool. Some problems are best solved with an API-driven workflow. Others live in systems with no API at all, where a well-built bot that works through the user interface is the right answer. We want someone who can tell the difference and who is comfortable delivering both.
You might come from either direction:
Integration and workflow background: you build in Make, n8n, Zapier, Power Automate or similar, and you're comfortable with APIs, webhooks and data structures.
RPA background: you've built and run bots in UiPath, Automation Anywhere, Blue Prism, Power Automate Desktop or similar, and you understand selectors, exception handling, queues, unattended runs and bot maintenance.
If you're strong in one and curious about the other, we want to hear from you.
Coding is not a requirement. Technical understanding is. You need to be genuinely comfortable with how systems talk to each other and how LLMs behave: reading vendor documentation, handling authentication, wiring systems together, deciding between API and UI automation, and knowing why a model gives you inconsistent output and what to do about it. You write a bit of script only when you have to. You will build, not just spec.
This is a key role for us with a big impact on the whole organization. You will have access to engineering resources when you need them. The goal: find the 20% of changes that deliver 80% of the gains. We have a strong preference for buying proven tools over building custom ones.
You might be right for this if you:
Enjoy eliminating tedious manual work
Can sit in on a finance team's reconciliation meeting and spot three things to automate
Have watched someone copy data between two screens all day and thought "an automation or bot should be doing that"
Know when a simple workflow tool does the job, when a UI bot is the pragmatic answer, and when you need something heavier
Can train someone in compliance who's never touched automation before
Understand that the best automation is the one people actually use
This probably isn't for you if you're looking to write software from scratch, or if your first move on spotting a problem is to document it and hand it off.
Key Responsibilities
Discovery & Analysis (35%)
Run structured workflow audits across departments
Talk to staff to understand their pain points and where they're doing things manually
Map processes and identify what's worth automating
Assess each opportunity for the right approach: API integration, UI automation (RPA), AI, or a mix
Evaluate build vs. buy decisions (with a bias toward buying)
Research automation tools and AI solutions relevant to iGaming
Implementation (35%)
Configure and deploy workflows using low-code/no-code platforms
Design and build attended and unattended bots for systems without usable APIs (back offices, payment provider portals, legacy tools, desktop applications)
Combine workflows with AI where it adds value, such as document processing, data extraction, classification and chatbots
Connect systems through APIs and webhooks, and know when an integration is beyond what you should be doing alone
Coordinate with engineering for complex integrations that need code
Manage vendor relationships for automation tooling
Document everything with runbooks and clear ownership
Optimization & Evaluation (15%)
Set a baseline before you change anything, so the improvement is arguable in numbers
Monitor what you've deployed to ensure it's working and being used
Track metrics: time saved, error reduction, adoption rates
Iterate based on feedback, discontinuing what isn't working and expanding what is
Run periodic reviews of existing automations to…