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
Company hidden

Staff Software Engineer, Backend

  • Hybrid
  • 6+ years
  • English (B2)
  • Polish (B2)

Salary

Not stated

Similar roles pay €75K - 105K 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

The company is building its own fintech platform from the ground up as a large, international initiative, with AI-native engineering at its core.

You will set the technical direction for one platform area: Payments Core, Merchant, or Consumer.

You will raise the output of the teams around you through clear architecture, engineering standards, and technical leadership across teams, and help improve the agentic engineering harness using data.

The team is lean and highly effective, and the company is hiring engineers comfortable with agentic engineering, from experienced builders of complex systems and tooling to newer engineers who started with AI-driven development.

You will work alongside a senior leader and their leadership team, gaining exposure to the e-commerce and logistics industries.

You will work in a diverse, international, cross-functional environment with leading experts.

The company is growing, with more opportunities across several locations in Europe, and its work supports sustainability, convenient deliveries, and the circular economy.

Responsibilities

  • Define and maintain the backend architecture for your area, including domain boundaries, event contracts, state machine patterns, data consistency models, and API design across services and teams.
  • Write Architecture Decision Records (ADRs) and RFCs that lay out the reasoning and trade-offs, and lead technical decisions across teams.
  • Assess and decide on core technology trade-offs such as database choice, cloud services, message broker topology, and consistency models suited to financial data.
  • Own the agentic development harness: instrument it, measure adoption and friction, and improve it based on data.
  • Lead organisation-wide technical change by identifying patterns to adopt or retire, building the case, and driving adoption across teams without direct authority.
  • Give technical input into product strategy, and mentor Staff-track engineers through design reviews, pairing, and feedback on technical writing.

Requirements

  • 8+ years in software engineering, including 2+ years in cross-team technical leadership or architecture ownership.
  • 3+ years designing distributed payments or fintech systems.
  • Hands-on experience with several tech stacks and deep backend expertise.
  • Solid understanding of distributed systems architecture, including event sourcing, CQRS, domain events, and the saga pattern, plus state machine and financial entity lifecycle design.
  • Experience designing service-boundary APIs across REST, async, and event-based contracts.
  • Ability to reason about database trade-offs (relational, time-series, document, ledger-style) and to evaluate cloud architecture on AWS, GCP, or Azure.
  • Experience designing or evolving an agentic engineering harness, including instrumentation, adoption measurement, and iteration.
  • Working knowledge of LLM tool-use patterns and context management in engineering workflows.
  • Excellent technical writing for ADRs, RFCs, and design docs aimed at different audiences.
  • English at B2 level or above.
  • 2+ years in platform or internal developer tooling engineering.
  • 1+ years of agentic or LLM system design experience.
  • 2+ years in BNPL or lending domain architecture.
  • Experience building PCI DSS and PSD2 compliance into architecture from the design phase.
  • Kafka or equivalent streaming architecture experience at scale.
  • Open-source contributions or technical publishing.
  • Polish language skills.

Conditions

Hybrid working, preferably 1 day per week in the Warsaw or Cracow office.

Flexible hours.

B2B contract.

Benefits

  • A range of benefits, plus investment in training and development opportunities.

Where you’d work

Hybrid, 1 to 2 days a week in the office

About the company

Company hidden

  • Industry: Logistics

Office in Warsaw, Poland

Your chances

Likely still hiring, not crowded yet, and you'd be among the first.

  • 16 checks run
  • 6 good signs
  • 1 red flag

Still hiring?

10 checks

Likely active

In its favour2

  • Still on the company's own careers site, checked 1 h agoModerate evidence
  • Found in the last 48 hours, before the big job boardsModerate evidence

Against it1

  • Listed again after an earlier listing of the same role closedModerate evidence

How crowded?

6 checks

Low

In its favour4

  • In its Early Window: not on the big job boards yetStrong evidence
  • Asks for 8+ years: a narrow poolModerate evidence
  • Hybrid in Warsaw: only people nearby can take itSlight evidence
1 moreFewer
  • Asks for Polish: far fewer people can applySlight evidence

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
Details14 facts · Role, Location, Compensation, Employment, Company, Requirements
Tech stack
  • AWS
  • Kafka
  • Azure
  • LLMs
Seniority
Staff
Type
Full-time
Industry
Logistics
Specialty
Backend
Region
Europe
Show 8 more factsShow less

Role

Category
Development
Specialty
Backend
Seniority
Staff
Experience
8+ years
Tech stack
  • AWS
  • Kafka
  • Azure
  • LLMs

Location

Work model
Hybrid
Region
Europe
Office
  • Warsaw, Poland
Days in the office
1 to 2 days

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Full-time

Company

Industry
Logistics

Requirements

Languages
  • English (B2)
  • Polish (B2)

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason