Jobs / Spain / Onespan INC

Onespan INC

AI Automation Engineer

Barcelona Posted today

Apply on employer site ↗ Tailor my CV first Source: Company careers site

Optional: we can tailor a CV and cover letter for this job from your real experience first (the first one is free).

Sponsorship verdict

No sponsorship evidence yet

No government record and no wording either way. Not a refusal: ask the recruiter.

  • No government sponsor record hereNo government sponsor record covers this employer in this country.
  • The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
  • Can’t check pay against the visa rulesWe don’t have visa salary rules for this country yet.
  • Confirmed live todayWhen a source last listed this job as open.
Details and sources

A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.

Before you apply

Sponsorship unknown

No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.

These come from the posting’s own wording. Read the original listing to confirm. See better-fit alternatives →

About the role

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

Apply on employer site ↗