Algorithmic Trading Systems Engineer vs Core Banking Systems Specialist (Temenos / Mambu): Salary & Career Benchmarks in Poland

In Poland, Algorithmic Trading Systems Engineer roles typically command a higher median salary than Core Banking Systems Specialist (Temenos / Mambu) positions. According to our 2026 live benchmark data, a mid-level Algorithmic Trading Systems Engineer earns a median salary of PLN306K, whereas a Core Banking Systems Specialist (Temenos / Mambu) brings in roughly PLN255K (a gap of PLN51K at the median).

Seniority, tech stack, and location all move this gap. Senior practitioners in either discipline can exceed the upper range through specialist skills. See the skills premium section below for the specific certifications and tools that push offers to the top of the range.

While both positions are vital to a modern tech organisation, Algorithmic Trading Systems Engineer and Core Banking Systems Specialist (Temenos / Mambu) have fundamentally different daily workflows.

Algorithmic Trading Systems Engineer focuses primarily on building and maintaining low-latency trading systems, from strategy execution engines to market-data ingestion and order-routing infrastructure. Day-to-day work revolves around optimising execution latency in C++ or Java, backtesting strategy changes against historical tick data, monitoring live trading systems during market hours, and working with quants to productionise new strategies.

Core Banking Systems Specialist (Temenos / Mambu) focuses on configuring, customising, and maintaining core banking platforms such as Temenos or Mambu that handle account, ledger, and product processing for banks. Their time is spent configuring product and account rules in Temenos or Mambu, managing core banking upgrades and patches, integrating the core with payment and channel systems, and supporting regulatory reporting extracts.

Transitioning between these two paths is achievable but requires targeted upskilling.

Moving from Algorithmic Trading Systems Engineer to Core Banking Systems Specialist (Temenos / Mambu):

Moving from Core Banking Systems Specialist (Temenos / Mambu) to Algorithmic Trading Systems Engineer:

Neither path requires starting from scratch. Professionals in both roles share underlying technology fluency; the gap is usually domain knowledge and specific tooling rather than core engineering fundamentals.

In Poland in 2026, both roles are seeing demand, but with different drivers.

Algorithmic Trading Systems Engineer demand is high, particularly in Warsaw's banking and fintech sector, home to Poland's largest domestic banks and a fast-growing payments industry, led by employers such as Revolut and mBank. Core Banking Systems Specialist (Temenos / Mambu) demand is high, concentrated in Warsaw's banking and fintech sector, home to Poland's largest domestic banks and a fast-growing payments industry, led by employers such as Santander Bank Polska and ING Bank Śląski.

Workspace flexibility significantly impacts total compensation value in Poland.

Algorithmic Trading Systems Engineer roles score 25% on our remote-friendliness index (Low). This is because much of the work depends on proximity to trading desks or on-call banking infrastructure, a norm that Poland's IT sector has broadly kept in place thanks to the widespread B2B (umowa B2B) contracting model, which gives both employers and specialists more flexibility than a standard umowa o pracę. Where in-office attendance is required, it is typically driven by trading-floor proximity and same-room incident response, which larger employers with a Kraków or Wrocław global capability centre are more likely than smaller Polish software houses to formalise into a fixed hybrid schedule.

Core Banking Systems Specialist (Temenos / Mambu) roles score 40% (Moderate). Much of the work depends on proximity to trading desks or on-call banking infrastructure, a norm that Poland's IT sector has broadly kept in place thanks to the widespread B2B (umowa B2B) contracting model, which gives both employers and specialists more flexibility than a standard umowa o pracę is the primary driver of flexibility. When office days are required, it is usually for trading-floor proximity and same-room incident response, which larger employers with a Kraków or Wrocław global capability centre are more likely than smaller Polish software houses to formalise into a fixed hybrid schedule.