For CoAnalyst, our AI-powered analytics platform for the aviation industry

Location:

EU/UK (Hybrid), with travel to customer sites up to 40% of the time . Established core working hours to maximise overlap with the team.

Team:

CoAnalyst, part of the Safety group at Comply365

Reporting to

Director of Product, CoAnalyst

The one-liner:

You own every new customer from the day they sign to the day they are live. Not coordinate it. Own it.

About CoAnalyst

CoAnalyst helps airlines find the risks hiding in their data. Our customers generate enormous volumes of operational data, and CoAnalyst uses AI to surface patterns, recurrences, and emerging risks that no human team human team could realistically uncover manually. We are part of Comply365, working with some of the largest airlines and flag carriers in the world, while operating with the pace of a startup inside a scale-up: a small team, fast feedback loops, and real customers solving real-world challenges.

Why this role exists

Every customer we sign needs to go from a signed contract to a live, data-flowing, users-logged-in deployment. That journey involves genuine engineering: REST API and file-based integrations with their existing enterprise systems, historical data migrations at serious scale, SSO federation between our platform and their identity provider, data mapping nobody has done before, and privacy and redaction workflows, because our customers' data is about as sensitive as data gets. Today, that work is divided between engineers who should be building the product and PMs who should be shaping it. We want one person with end-to-end ownership. Fair warning: This is not a pure engineering role, and it is not a project management role with an engineer on speed dial. You will lead the project, own the customer relationship for the onboarding phase, and complete the technical work yourself.



If any one of those three makes you wince, this is not your role. If all three make you grin, keep reading.

What you WILL be doing -

- Owning the sign-to-live journey, end to end. From the kick-off call to the go-live announcement: implementation plan, integration build, data loads, SSO, UAT, launch. When something is blocked, you unblock it or elevate it. Nothing about the onboarding is somebody else's problem.
- Building the integrations yourself. REST API and S3-based data pipelines from customer systems into CoAnalyst, field mapping and data validation, scripting, debugging malformed payloads before go-live.
- Handling identity and access. SSO federation between our platform (AWS Cognito) and enterprise identity providers (Entra ID, OIDC, SAML), user groups, access models, and the security questions that come with them.
- Running the project like a professional. Scope, timeline, risks, dependencies, and steering calls where the customer's business lead and their IT security lead are in the same room asking very different questions. You will answer both.
- Being the customer's single human. For the onboarding phase you are the face of CoAnalyst: their point of contact, their escalation path, and the person they trust to tell them the truth about timelines.
- Making onboarding number five easier than number four. Playbooks, reusable tooling, documentation, welcome packages. Every implementation should leave the machine better than you found it.
- Feeding reality back into the product. You will see exactly where customers struggle before anyone else does. Product and engineering will want that signal, and you will be expected to deliver it with opinions attached.

What you WON'T be doing -
- Pre-sales. You start when the ink is dry. No demos to prospects, no RFP theatre.
- Handing “the technical bits” to an engineer. You are the engineer. Core product engineers stay focused on the product.
- Owning the

📌 Onboarding Engineer (Barcelona)
🏢 Comply365
📍 Barcelona