Back to jobs

Software Engineer (Data)

Pay
Pay not listed
Work setting
Remote — work setting source
Location type: Remote
From the employer’s posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
Engineering — team source
Department: Engineering
From the employer’s posting

What you’ll work on

Full posting
  • You'll build them, test them and find out how they break before a banker does.

From the employer’s posting
The signal layer. Spotting when something changes for a client: a customer paying later, cash running tighter, a supplier quietly becoming critical. You'll help build the detection and make it fast and reliable. The tools the assistant calls. MCP (Model Context Protocol) servers and APIs that serve data to agents. You'll build them, test them and find out how they break before a banker does. Keeping the numbers honest. Tests, data checks and observability that prove a number is right, and catch it the moment it isn't.

About Codat

Codat is an advisory intelligence solution purpose-built for modern commercial banking.

In the employer’s words · Read in context · Company website ↗

Apply at Codat

Posting record

Report an error

Actively hiringFirst seen by us 2 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 17, 20262 days ago
Recorded sightings
2
Last seen by us
Nov 18, 2026
Employer says posted
Nov 13, 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 2

Similar jobs usually come down between day 2 and day 14.

From 956 similar postings that came down. Coming down is not always a hire.

Codat 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 and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • C#
  • Python
  • SQL
  • Azure
  • Databricks
  • dbt
  • Docker
  • Spark
Where the posting names them
- Had data be the hard part. A source that sent duplicates, a schema that changed under you, two teams who meant different things by "customer". You fixed it, and you'd design it differently now. - Good engineering habits in Python, C# or another general-purpose language. Tested, modular code the next person can change without fear. - An eye for SQL. You can read a query and tell whether it's right, whoever or whatever wrote it.
- Good engineering habits in Python, C# or another general-purpose language. Tested, modular code the next person can change without fear. - An eye for SQL. You can read a query and tell whether it's right, whoever or whatever wrote it. - Stayed on the hook for something after it went live. You found out why it broke, fixed the cause, and added what would have caught it sooner.
- Stayed on the hook for something after it went live. You found out why it broke, fixed the cause, and added what would have caught it sooner. - Some time with CI/CD, Docker and cloud (we're on Azure). You've changed a pipeline, not just pushed to one. - A habit of asking why. If someone asks for a number the data can't support, you say so.
- Momentum. More ownership with each move, new stacks picked up quickly, things built that nobody asked for. - Useful, not essential: fintech, lending or accounting; Spark, Databricks or dbt; anything that puts data in front of an LLM. Don't tick every box? Apply anyway. We're more interested in what you've built and how fast you're growing than in a perfect match.

Your next step

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

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Has Codat posted this job before?

Yes. We’ve followed one other Software Engineer (Data) job there since November 2026. It is still up.

  1. LondonStill up after 2 days, first seen Nov 17
  2. This jobUp 2 days so far, first seen Nov 17

Job description

View original posting ↗

About Codat

Codat is an advisory intelligence solution purpose-built for modern commercial banking. Through rich, specialized data, forward-looking insights, and integrated workflows, Codat empowers banking teams to deepen their relationships, grow their revenue, and simplify their day-to-day work.

Founded in 2017 and backed by JPMorgan, PayPal, Amex, Plaid, and Shopify, Codat has successfully powered over 350,000 connections to business customers’ financial systems — and is trusted by industry leaders to turn scattered information into actionable, strategic advantages in real time, every time.

The Role

Some of the biggest commercial banks in the world already work with us. Their relationship managers want to spend their time with clients, not digging through the books to find out what's changed. We're building the thing that does the digging for them.

It's called the Advisory Intelligence Platform. It puts Codat's client intelligence inside the assistant a banker already uses, starting with Microsoft Copilot. Ask it anything about a client and it answers from that client's actual books. Don't ask, and it tells you anyway when something important changes.

Every one of those answers sits on data. Someone has to get that data in, shape it, define it and serve it, so the number the assistant quotes is the right one. That's you. You write production software, and you care about the data it moves as much as the code that moves it.

This role is for an engineer who's growing fast and wants room to grow faster. You'll ship from your first weeks, own what you build once it's live, and work alongside data and AI engineers who'll push you. Codat is AI-first, not AI bolted onto SaaS, and we work that way ourselves: agents take the repetitive work, engineers take the interesting problems.

 

What You'll Work On

  • The data behind every answer. Services and pipelines that take raw data from accounting platforms, banks and payment systems and turn it into something a model can trust. When a source sends rubbish, your code notices.

  • The semantic layer. The definitions the model is allowed to use: what counts as revenue, when a month ends, which currency. Get it right and every answer agrees with every other answer.

  • The signal layer. Spotting when something changes for a client: a customer paying later, cash running tighter, a supplier quietly becoming critical. You'll help build the detection and make it fast and reliable.

  • The tools the assistant calls. MCP (Model Context Protocol) servers and APIs that serve data to agents. You'll build them, test them and find out how they break before a banker does.

  • Keeping the numbers honest. Tests, data checks and observability that prove a number is right, and catch it the moment it isn't.

You'll Probably Have

  • Shipped production software that real people depended on, and written most of it yourself. Services, APIs or data systems with tests, not notebooks or config.

  • Had data be the hard part. A source that sent duplicates, a schema that changed under you, two teams who meant different things by "customer". You fixed it, and you'd design it differently now.

  • Good engineering habits in Python, C# or another general-purpose language. Tested, modular code the next person can change without fear.

  • An eye for SQL. You can read a query and tell whether it's right, whoever or whatever wrote it.

  • Stayed on the hook for something after it went live. You found out why it broke, fixed the cause, and added what would have caught it sooner.

  • Some time with CI/CD, Docker and cloud (we're on Azure). You've changed a pipeline, not just pushed to one.

  • A habit of asking why. If someone asks for a number the data can't support, you say so.

  • AI as part of how you work, and you can explain and defend what it helped you build.

  • Momentum. More ownership with each move, new stacks picked up quickly, things built that nobody asked for.

  • Useful, not essential: fintech, lending or accounting; Spark, Databricks or dbt; anything that puts data in front of an LLM.

Don't tick every box? Apply anyway. We're more interested in what you've built and how fast you're growing than in a perfect match.

 

How We Work

We're a small team with plenty to do. Things move fast: we'd rather ship something useful and improve it than polish it in private. What you build is yours from start to finish.

There's no return-to-office mandate, and you can work hybrid or fully remote. We trust you to be around when the team needs you and to deliver what you said you would. What we don't want is anyone staying online late to prove a point.

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

United Kingdom

We're a small team with plenty to do. Things move fast: we'd rather ship something useful and improve it than polish it in private. What you build is yours from start to finish. There's no return-to-office mandate, and you can work hybrid or fully remote. We trust you to be around when the team needs you and to deliver what you said you would. What we don't want is anyone staying online late to prove a point.
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.