Creditsafes Data Cloud is a platform most people never see but most businesses worldwide indirectly depended on: billions of records tens of millions of daily updates along with capability of managing customers portfolio over highly scalable APIs.

Were hiring a Staff Software Engineer to own a technical domain that cuts across several teams inside Data Cloud for example our ingestion and transformation platform our API tier or our metadata and lineage layer. Youll set direction raise the engineering bar and remain hands-on enough that Seniors genuinely want your code review.

This is not a management role. Its the technical-leadership rung on our IC ladder with the scope and compensation to match.

What youll own

A technical domain not a single service. Youll be the engineer who knows how a slice of Data Cloud works end-to-end and where its going next.

Architecture and strategy. Drive multi-quarter technical roadmaps: what we build what we retire and what we stop doing. Author the RFCs that matter.

Cross-team decisions. Partner with two or three engineering teams Product and Data Science to make the right technical trade-offs especially the ones no single team can make alone.

Quality of the whole. Reliability performance cost and security for your domain. When an incident touches your area youre part of the postmortem.

Engineering standards. Set the bar for design reviews API contracts testing and operability and teach it so it sticks.

Hands-on work. We expect you to still ship code typically the hard bits the de-risking prototypes and the reference implementations others build on.

Mentorship at scale. Grow Seniors into the next Staff engineers. Coach Engineering Managers on technical direction. Be generous with your time.

What were looking for

We hire Staff engineers on evidence not titles. If youve been doing the work of a Staff engineer even without the label we want to hear from you.

Must-haves

Deep experience building and running production systems in Python on AWS typically 8 years of engineering with at least a couple of those operating at a Staff/Principal scope.

A track record of leading systems not just features. You can point to platforms or services you designed whose decisions still hold up under load change and time.

Strong judgement on trade-offs. Cost vs. latency build vs. buy consistency vs. availability velocity vs. debt and you can explain your reasoning in a room of non-engineers.

Demonstrable technical influence across teams not just within one. RFCs guilds shared libraries architecture forums something that shows your reach.

A mentoring habit. Named engineers whose careers moved because of your input. You already enjoy this work.

Excellent written communication. Your docs RFCs and postmortems teach people things. This matters as much as your code.

Nice to have

Rust in production or experience taking a team on that journey.

Deep AWS data-platform chops: Redshift Glue Athena Iceberg/Parquet lakehouse patterns.

High-throughput serverless design with auditability and exactly-once semantics.

Experience owning a domain that spans 3 teams or 10 engineers.

Financial credit or regulated-data background.

How we work

IC ladder with teeth. Staff is a destination not a waypoint with scope comp and influence that genuinely match the title.

Written design culture. Anything non-trivial gets an RFC. Decisions are recorded. We disagree in documents not in meetings.

Real operability. We run what we build. No hand-offs to a separate ops team.

Pragmatic agile. Teams own their own process. We optimise for shipping not ceremony.

Leadership youll want to work with. Engineering leadership is technical present and will back your calls.

What you get

Staff-level salary a meaningful annual bonus and company pension.

25 days annual leave plus bank holidays.

Private healthcare and wellbeing programme.

Generous learning budget conferences and time for industry contributions (talks OSS writing).

Hybrid working Cycle-to-Work and your choice of hardware.

Visibility with senior leadership; your work lands on the roadmap it deserves.

About Creditsafe

Creditsafe has been making business information accessible since 1997. Today we help companies of every size from sole traders to the FTSE 100 make smarter decisions about who to trust who to sell to and who to work with. Our Data Cloud team is where that data is turned into something the rest of the business and our customers can rely on.

Were an equal opportunities employer and we mean it. If you need any adjustments to the interview process tell us well sort it.

The hiring process

Intro call with the Head of Data Cloud Engineering (30 minutes).

Technical deep-dive with two engineers on a concrete problem from our platform (90 minutes).

System Design discussion: Primarily focused on approach to problem and Trade Offs(60 minutes).

Leadership and influence conversation with an EM and Director (60 minutes).

Typical end-to-end: 34 weeks. Detailed feedback at every stage.