You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Be the first to open itNo views yet
Kpler

Engineer II (AI Enablement)

  • Hybrid
  • 3-6 years

Salary

Not stated

Similar roles pay €70K - 115K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

As an Engineer II on Kpler's new AI Enablement crew, you will build the tools, agents, and integrations that help every function in the company work with AI at scale.

As a strong individual contributor, you will be responsible for the entire lifecycle of features and projects - breaking down problems, owning them from design through production operation, and coordinating with others where the work spans more than one person.

The work is varied and hands-on: building and tailoring AI agents and assistants for internal teams, curating the knowledge bases they rely on, integrating them safely with company systems, and building the interfaces and tooling around them.

You will work alongside a senior engineer and a lead who will support your growth in a fast-moving, high-visibility area of the company. To begin with, the emphasis will be on delivering Kpler's company-wide AI adoption plan; your areas of focus will shift over time with the crew's priorities

Responsibilities

  • Build, tailor, and operate AI agents and assistants for internal functions, owning features end-to-end from design through deployment and production operation (including testing and CI/CD).
  • Build and maintain knowledge-base pipelines: collecting, structuring, and keeping current the content that AI systems rely on to be accurate and useful.
  • Integrate AI systems with company tools and data sources through well-structured, safe APIs and connectors.
  • Apply the crew's security guardrails and responsible-AI practices: access control, data privacy, and human-in-the-loop safeguards.
  • Build user-facing tooling and interfaces where the work calls for it, spanning UIs and the backend services behind them.
  • Instrument what you ship: adoption, quality, and cost metrics that show whether a solution is working.
  • Gather feedback from internal users, identify friction points, and turn them into concrete improvements.
  • Keep owned systems reliable, observable, and maintainable; participate in incident response and RCA for owned services.
  • Provide context and clarity through documentation and runbooks so others understand what's built and why.
  • Contribute to the crew's shared frameworks and to AI-assisted engineering practices a
  • Experience & Background
  • Essential:
  • 3+ years of professional engineering experience.
  • Experience building and operating production systems end-to-end (services, APIs, or tooling).
  • Hands-on experience building with LLMs (features, agents, automations, or serious side projects with production-quality practices).
  • Understanding of system design, databases/data modelling, and application architecture.
  • Familiarity with cloud infrastructure and CI/CD pipelines.
  • Strong problem-solving and collaboration skills, with a user-centric mindset.
  • Proficiency in Python and/or TypeScript.
  • LLM application development: model APIs, prompt/context engineering, basic RAG patterns.
  • API design and data integration across multiple systems and sources.
  • Database design, SQL, and data modelling.
  • Familiarity with cloud services (AWS preferred), containerisation (Docker/Kubernetes), and CI/CD practices.
  • Desirable:
  • Experience with agent frameworks, MCP-style tool interfaces, RAG, or knowledge-base systems.
  • Experience integrating third-party SaaS APIs.
  • Full-stack experience — building web UIs as well as their supporting backend services.
  • Experience building internal or developer-facing tools.
  • Exposure to LLM evaluation, observability, or prompt/context engineering.

Where you’d work

Part of the week in the office

About the company

Kpler

Offices in Paris, France, Athens, Greece

Also hiring in Greece, United Kingdom, France and 2 more places

3 of their 23 open roles are remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 19 checks run
  • 2 red flags

Still hiring?

13 checks

1 red flag

How crowded?

6 checks

1 red flag

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details9 facts · Role, Location, Compensation
Tech stack
  • TypeScript
  • Python
  • SQL
  • AWS
  • Kubernetes
  • Docker
  • CI/CD
  • LLMs
  • RAG
Specialty
Backend
Region
Europe
Pay period
Annual
Show 5 more factsShow less

Role

Category
Development
Specialty
Backend
Experience
3+ years
Tech stack
  • TypeScript
  • Python
  • SQL
  • AWS
  • Kubernetes
  • Docker
  • CI/CD
  • LLMs
  • RAG

Location

Work model
Hybrid
Region
Europe
Offices
  • Paris, France
  • Athens, Greece

Compensation

Salary
Salary by agreement
Pay period
Annual

Something wrong with this vacancy?

Similar vacancies

  • Early Window: Be the first to open itNo views yetCloses in
    Company hidden

    Staff Software Engineer

    Salary by agreement

    • Remote · Europe, Portugal
    • Senior
  • Early Window: Be the first to open itNo views yetCloses in
    Company hidden

    Senior Software Engineer

    Salary by agreement

    • Remote
    • Senior
  • Early Window: Be the first to open itNo views yetCloses in
    Company hidden

    Software Engineer

    Salary by agreement

    • Hybrid · Toronto
    • Junior
  • Early Window: Be the first to open itNo views yetCloses in
    Company hidden

    Senior Software Engineer

    €85,000 - 140,000 / year

    • Office · Ireland
    • Senior
    Direct apply

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason