Back to jobs

AI Automation Engineer

Pay
Pay not listed
Work setting
Not stated
Employment
Not stated
Apply at Onespan

Posting record

Report an error
Status in our records
Live
First seen by us
Oct 14, 202638 days ago
Recorded sightings
38
Last seen by us
Nov 21, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 38

Up longer than most. Similar jobs usually come down between day 1 and day 15.

From 1,376 similar postings that came down. Coming down is not always a hire.

Onespan is hiring

4 open jobs

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume to compare the role’s scope, tools and requirements with your experience.

Your next step

Complete your application on www.onespan.com. The employer’s form will show what is required.

Applying through Greenhouse

  • No account needed: the form is one page, with an “Autofill my application” option that reads your resume.
  • Greenhouse doesn’t read resumes over 2.5 MB, or details placed in a header, footer, text box, table or second column. The file still attaches, but a recruiter has to type you in by hand.

Already applied? Track this application

Job description

View original posting ↗

At OneSpan, we specialize in digital identity and anti-fraud solutions that create exceptional and secure experiences.

We’re looking for an engineer who has spent years making professional software teams faster – automating builds, tests, releases and the glue between them – and who now wants to take whole teams agentic, not just themselves. You believe agents can take over work that today ties up whole people, and you can prove it inside real engineering teams. This is a founding role. You’ll embed with our R&D teams, find the manual, repetitive work that slows them down, and build the automations – agentic where that’s the right tool, plain scripting where it isn’t – that give them their time back. Our engineers are strong and overloaded; your job is to make them much more productive without adding to their plate. Do this well and you’ll grow it into a small team you lead.

Here is a little taste of your challenge:

  • Embed and find the work worth removing: Shadow our R&D teams to learn how work really flows, and find the bottlenecks and repetitive manual work hiding in plain sight. Rank opportunities by how often they happen and how much they cost – not by how interesting they are to build. Testing, QA, build and release processes are often the richest place to start.
  • Prioritise with each team’s manager: The managers want this help – you’ll agree with each of them what to tackle first and the time to protect for it, so the highest-value work gets done.
  • Build it – agent-first, but not agent-only: Design and ship the solution end-to-end. Reach for agents where judgment and language are in the loop; reach for a script, pipeline or bit of tooling where that’s simply more reliable. A simple, dependable solution is worth more than a clever one that breaks.
  • Move teams to agentic ways of working: Beyond one-off automations, you change how teams work every day: agents reviewing every PR, taking the first pass at bug fixes, writing tests and release notes – with engineers in the loop where judgment matters. You set up the shared skills, guardrails and workflows that make this the default for a team, not an experiment one engineer runs on their own laptop.
  • Build for handover, so the team can own it: You build with the team, not for them – and because each team owns its automations after handover, you design them to be owned: documented, monitored where it matters, and maintainable by a normal engineer on that team. A handover isn’t “here’s a tool,” it’s “here’s something your team can run and improve without me.” That’s also how automations earn trust – they have to be robust enough that teams rely on them and make fewer manual mistakes, not more.
  • Set the standard, then grow the team: You’re the first hire and the template for everyone who follows. As the work justifies it, you’ll have the chance to lead a small (2–3 person) team focused entirely on AI adoption across R&D.

Who are you?

There is no set route into this role. But to be successful, this is the kind of profile we have in mind:

  • 5–10 years making software teams faster: As a DevOps or platform engineer, CI/CD or build/release engineer, developer productivity engineer, SRE or test automation engineer – the title matters less than the track record. You’ve built and maintained automation that other teams rely on every day (pipelines, release tooling, test infrastructure, internal tools), not just tools for yourself.
  • Agentic by default – for whole teams: It hurts to watch a team still reviewing every PR by hand, or fixing bugs an agent could have taken a first pass at. You use agents every day yourself, but what drives you is getting teams to work that way – and you’ve done it before. You know the tools, the patterns and the limits, and you genuinely believe agents can absorb work that’s done by hand today.
  • Empirical about what actually works: And precisely because you believe in agents, you’re honest about when something is just a script. You choose the simplest thing that reliably works. This pairing – conviction plus sober judgment – is the whole job.
  • A strong generalist who ships: You build and deliver, not just design. You’re fluent enough across scripting, CI/CD systems (e.g. Jenkins, GitHub Actions), build tooling, containers and backend to automate almost anything you find.
  • Allergic to manual work: Watching someone do the same thing by hand twice bothers you, and you have a track record of automating away work nobody else had questioned. You still ask “how often, and how costly?” before deciding what’s worth automating.
  • You earn trust and build alongside people: You embed, listen, and build with a team rather than dropping finished tools on them. Collaborative, not lone-wolf. You’ve rolled out a tool or practice across teams before and got people to actually adopt it.
  • Fresh eyes, no baggage: You do NOT need mobile or security experience. We want someone who looks at entrenched workflows and questions them – not someone who has already accepted them as normal.
  • Product / platform mindset: Your users are our engineers; the time you give back to them is your product.
  • Leadership is upside, not a requirement: If you want to grow into leading the team, great. If you’d rather stay hands-on and deep, also great.
  • Fluent in English (essential); Spanish is highly valued for working day-to-day with our Barcelona-based teams.

Practically speaking, what’s in it for you:

  • A rare greenfield mandate – you define how a whole organisation adopts agentic AI, starting from a blank page.
  • Freedom to bring the right tools – you’ll start from our current stack (Claude, our core languages and tooling) and have real latitude to introduce whatever works better.
  • Teams who want this – the managers are asking for the help and are ready to work with you.
  • Simplicity – because we like to make things easy and practical.
  • Beautiful office in the heart of Barcelona – with regular team events (breakfast, lunch, beers…).
  • Good transport connections – easy to reach by public transport.
  • Flexible working hours & hybrid working.

Please include a brief cover letter describing an automation or process improvement you built that is still actively used today. We'd like to understand the problem it solved, the impact it had (e.g., time saved, errors reduced, efficiency gained), who uses or owns it now, and what approach you would take to identify similar opportunities here.

 

 

 

About Onespan

People
About 602 in 2025, up 5% from the year before.Annual report (SEC Form 10-K)
Company
Listed as OSPN.

Demand for AI Engineer roles

New AI Engineer postings at the employers we follow are up 340% over the last 6 weeks compared with the 6 before.

Weekly new AI Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 78, the most 803, and the latest week had 438.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under AI Engineer, by the work the posting describes.

AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.

Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.

An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Barcelona

- Good transport connections – easy to reach by public transport. - Flexible working hours & hybrid working. Please include a brief cover letter describing an automation or process improvement you built that is still actively used today. We'd like to understand the problem it solved, the impact it had (e.g., time saved, errors reduced, efficiency gained), who uses or owns it now, and what approach you would take to identify similar opportunities here.
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.