Time since we first saw it
Day 3
Similar jobs usually come down between day 3 and day 42.
From 633 similar postings that came down. Coming down is not always a hire.
Listed location: RemoteRead the full posting
Employment type in the employer’s posting: Permanent employeeFrom the employer’s posting
Own and evolve pipelines that connect supply-chain data to OpenSC
Investigate data-quality issues at source and work with suppliers to fix them
Turn messy ERP exports, spreadsheets and handwritten records into reliable data
Build customer-facing data-quality tools and reusable onboarding components
Act as the technical contact translating customer requirements into solutions
You own and evolve the pipelines that connect supply-chain data to OpenSC.
You investigate data-quality issues at their source, collaborate with suppliers to resolve them
You work with varied and imperfect source material, including ERP exports, spreadsheets and handwritten records, and turn it into data customers can rely on.
This includes customer-facing data-quality tools, reusable onboarding components and automations that reduce manual work.
You are the technical person customers and their suppliers talk to. You translate operational requirements into practical technical solutions.
Our Tech Stack Day to day, you'll work with: Dagster for pipeline orchestration; PostgreSQL and dbt for data transformation; Python for automation, APIs and tooling; AWS (S3 and RDS) for cloud storage; Docker for development environments; Claude Code for AI-assisted development; and a fleet of background agents that handle recurring work like data standardisation and ticket triage, which you'll use, extend and build new ones. Used similar tools rather than these exact ones? We still want to hear from you.
You use AI throughout your daily work and keep pushing to learn industry best practices. You've built data pipelines, or something pipeline-shaped, in Python and SQL, and had to deal with what happens when they break. You've run things in production on a cloud platform (AWS or similar) and understand what keeps them reliable: how services fit together, what to monitor, and what it costs.
You've built data pipelines, or something pipeline-shaped, in Python and SQL, and had to deal with what happens when they break. You've run things in production on a cloud platform (AWS or similar) and understand what keeps them reliable: how services fit together, what to monitor, and what it costs. You've built something that significantly changed how others work, such as a tool, framework or automation a team came to rely on.
Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 3
Similar jobs usually come down between day 3 and day 42.
From 633 similar postings that came down. Coming down is not always a hire.
1 open job
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordCheck the employer’s posting for the current role and application details.
Already applied? Track this application
New Forward Deployed Engineer postings at the employers we follow are up 225% over the last 6 weeks compared with the 6 before.
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.
We file this job under Forward Deployed Engineer, by the work the posting describes.
Forward deployed engineers are placed with their employer's customers: they learn a customer's problem and write the code that makes the employer's product solve it inside the customer's own systems.
Postings ask for strong software engineering, most often in Python, ease with customers and their executives, often travel, and in about three of four cases work with large language models or AI agents.
An AI engineer or data engineer builds for their own employer's product team; a forward deployed engineer does similar work inside a customer. We give this role to every posting whose title says forward deployed.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Remote
Why us? Remote, CET ±2 hours | Building Tech for Sustainable Impact Why We Exist
Small, agile team. Priorities shift as we learn, so ownership matters. You'll decide how to tackle problems, not just pick up the next ticket. Open, informal communication. We live on Slack, love a quick huddle and are always on the hunt for new custom emojis. Because we're remote-first, we'd rather you over-communicate than leave people guessing. Pairing and review. We pair program regularly and review each other's code.
No clear work-authorization passage found. Eligibility is unconfirmed.
We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting