Pro kandidáty

A leading international fintech company operating payment systems used daily by millions of customers and businesses globally. Their infrastructure handles real-time transactions across continents — at genuine scale. The team is technically serious: real architecture discussions, no ticket factory. They're currently expanding to accelerate the next wave of product development — including modernization of core payment flows and exploration of blockchain and digital settlement infrastructure.Core Requirements — Java — 3+ years of commercial experience — Spring Boot and microservice architecture — not just awareness, actual hands-on work — NoSQL databases (MongoDB or similar) and cloud platforms (AWS or equivalent) — Apache Camel or WebFlux — experience with at least one Profile — Czech or Slovak — conversational level required; English for written communication — Independent — you don't wait to be told what to do next — Communicative — you can explain a technical decision to someone who isn't an engineer — Proactive approach to technical design, not just implementation — Comfortable in cross-functional teams with non-engineering stakeholders Nice to Have — AI Agents experience (development or integration) — AWS certifications or deep AWS knowledge (EKS, Lambda, Atlas) — FinTech or payment systems background — Jira proficiency for Epic and User Story management These are genuine advantages — not hard filters. If the core requirements fit, reach out.Role / Mission You'll join a cross-functional Scrum team working on both new product features and the ongoing modernization of an existing payment platform. The team includes architects, analysts, developers, QA, and a Scrum Master — you'll collaborate across all of them. You report to the Engineering Manager. Architecture decisions are made collaboratively within the team — you'll be part of design discussions from the start, not handed specs to implement. In 12 months: you own at least one major component of the payment infrastructure. The codebase is cleaner, microservice boundaries are clearer, and the team ships features faster because you helped make that happen. Key Responsibilities — Build new product features and drive modernization of existing payment application components — Participate in requirement grooming and planning — understand the business domain, not just the tickets — Evaluate technical solutions, identify risks, and contribute to architecture decisions during design phases — Break down work, estimate scope, and take ownership of sprint commitments — Do pull requests — review code (yours and others') with focus on quality and long-term maintainability — Work with complex business logic: payment workflows, distributed transactions, eventual consistency — Collaborate with mobile developers (iOS/Android) on API contracts and integration points — Contribute to CI/CD practices and automated testing improvements This is not a helpdesk role. Not a shift-based rotation. You write code that powers real financial flows — and you'll know why every line matters. Operating Model Remote-first. Occasional visits to the Prague office for team sync and planning — not mandatory, but available. Flexible working hours with a daily standup to align the team. Working language: Czech or Slovak internally (English for documentation and cross-team communication). Scrum-based team rhythm, async-friendly for deep work.Interested? Apply or reach out directly: | linkedin.com/in/jirisoljak No CV needed. Just your LinkedIn and a few lines about yourself. You'll be speaking directly with an experienced IT headhunter with hands-on IT background — 450+ hires. Expect a relevant discussion without HR fluff, with a clear understanding of technology, the market, and your real situation. Process: — Intro call (15–30 min) — Technical interview with the Hiring Manager — We move fast, based on mutual availability — You always know where you stand — no ghosting, no black box EU work authorization required. No visa sponsorship.

This is one of the world's largest construction and development groups — active across Europe and North America, 30,000+ employees, consistently ranked in the global top 20. Buildings, infrastructure, urban regeneration. Projects that shape how cities look for decades. At the core is an Oracle Fusion ERP covering the entire Central Europe region — Financials, HCM, and Supply Chain across multiple countries. The IT organisation is international, with governance in the UK. The culture is Scandinavian: open, direct, and flat by enterprise standards. This is the next step in how their IT is evolving. Maybe that step involves you. Oracle Fusion is live. Roles, access rights, and SoD rules were set during implementation — but that's not the same as long-term ownership. Now it needs someone who actually owns this layer. The goal is to build real ERP security competence in the Czech Republic — connected to the international team, but with real ownership on the local side. The team is growing. This is a new position, not a replacement hire.What Matters Most: Three things that matter: * ERP security background, hands-on — 2–4 years working with roles, access rights, or identity management in an enterprise ERP. Oracle Fusion is ideal. SAP GRC or another ERP security background works — you'll pick up the Oracle context. * SoD is not just a term you know — you can explain why a specific role combination is a problem and what the actual risk is. You understand SOX and GDPR beyond just ticking boxes. * You think before you click — when a role request comes in, you ask why before you approve. That's it. Oracle Risk Management Cloud, scripting skills, and direct audit experience are strong advantages — not hard requirements. The right mindset and ERP security background will take you the rest of the way. Nice to Have: * Direct experience with Oracle Fusion Applications or Oracle Risk Management Cloud * Scripting or automation skills (Python, Shell) for streamlining repetitive security tasks * Hands-on SOX audit preparation or support experience * Oracle or relevant IAM certification These are nice to have — not hard filters. The right ERP security background and mindset will take you the rest of the way.Role / Mission: Your mission is simple: make sure people in Oracle Fusion have exactly the access they need. Nothing more. Nothing less. That means designing and maintaining roles, running SoD analyses, managing user lifecycle, and working with business and IT to turn requirements into configurations that actually work. You report to the Head of ERP. You're one of the core members of an internationally distributed EMEA team — architects, analysts, developers, and support. A senior Oracle Fusion colleague is there not to watch over you, but to step in when things get tricky. You help define the security rules for the region, not just execute them. The impact is direct. One bad role setup or a missed offboarding creates a gap in controls. A good setup passes audits without drama. After 12 months, this is what good looks like: you know the full access map for the region, you run SoD analyses independently, your documentation is current, and an audit doesn't catch you off guard. Key Responsibilities: * Design, implement, and maintain roles, responsibilities, and access controls in Oracle Fusion (Financials, HCM, SCM) * Run SoD analyses and resolve role conflicts — understanding what you're configuring, not just clicking through * Manage the full user lifecycle: onboarding, changes, offboarding — accurately and on time * Configure advanced controls in Oracle Risk Management Cloud (notifications, model controls, perspectives, state management) * Prepare documentation for internal and external audits (SOX, GDPR) and actively support audit activities * Keep security process documentation current — not just before audit season * Work with business process owners and IT to translate requirements into technical configurations * Escalate issues to Oracle Support Portal when they go beyond what the team can handle internally What This Role Is NOT: * Not a helpdesk or ticket queue — you don't just click approve, you actually understand what you're granting * Not a systems architecture role — overall system design is with a more senior colleague in the international team * Not infrastructure or network security — this is the Oracle Fusion application layer, full stop * Not a short-term or transitional position — stable, long-term role in the core IT team Operating Model: Working language is English — you'll use it daily with the internationally distributed EMEA ERP team (architects, analysts, developers, and support; governance and senior leadership in the UK). Czech Republic, 1–2 days/week on-site — otherwise remote. Reporting line: Head of ERP.Interested? Apply or reach out directly:  | linkedin.com/in/jirisoljak No CV needed. Just your LinkedIn and a few lines about yourself. You'll speak directly with an experienced IT headhunter who understands the tech — expect a relevant, no-bullshit conversation. Process: * Intro call (15–30 min) * Screening with the CZ ERP team * Main interview with Head of ERP (UK) * You always know where you stand — no ghosting, no black box EU work authorization required. No visa sponsorship.

One of the world's largest logistics networks — land, sea, air, 220+ countries. The IT backbone behind it: 5,600+ specialists globally. The Prague team is part of core engineering delivery, not a regional satellite. For this specific mobile area, there are two analysts based in Prague right now. You'd be the third. Mobile use cases on the platform are expanding. The engineering capacity is there. What's missing is clarity — what to build, why, and in what order. The previous person in this role moved into a broader function within the company. People here grow — they don't leave. This position is re-opening at a time when the mobile scope has grown, so it's not a straight replacement. The work has expanded beyond what two people can own alone.What Matters Most: Forget a long checklist. This role comes down to three things: * You understand delivery — you can tell a clean backlog from a mess. You know what "done" should feel like before the first ticket gets written. * You think in problems, not tickets — you don't take a brief at face value. You dig until you find the real ask, then shape the solution. * You push back with substance — stakeholders expect a real conversation, not a nod. The dev team expects clarity, not ambiguity. You're comfortable holding that line on both sides. English at a level where written communication does the heavy lifting — you're distributed across time zones, so a well-written update or requirement doc often replaces a call. Your async written English matters as much as your spoken English. High-level mobile knowledge matters — Android/iOS ecosystem, app lifecycle, enterprise distribution. You won't write code. But you need to know what the conversation is about. Nice to Have: * Experience in enterprise or regulated environments * Basic orientation in cloud platforms (Azure, AWS, GCP) from a business perspective * Experience with internal mobile app distribution * Agile certifications (Scrum, SAFe, or similar) These describe the platform context — not hard filters for selection.Your job is to close the gap between what the business wants and what gets built. That means going past what stakeholders say they need. Finding the actual problem. Pushing back on weak briefs. Coming back to the team with a backlog that makes sense and can be picked up without another round of back-and-forth. The team covers the full product lifecycle end-to-end — from build to run. Around 15 people: developers make up the majority, with testers, delivery roles, a dedicated architect, and support. The Prague hub is small — three people, including this role. The rest of the team is internationally distributed across multiple time zones. You'll report directly to the Head of Mobile Delivery. That setup matters: you won't be a local BA coordinating within arm's reach. You'll be the bridge between Prague and a globally distributed team — which means strong written communication and the ability to move things forward without waiting for someone to follow up on you. Stakeholders know their domain. Conversations are direct, not hand-holding. Your influence here comes from expertise, not mandate. You don't own the final call — that sits with the business owner. But you're the one who shapes the quality of the decision before it gets made. That's what this role is actually about. After 12 months: delivery in your area is faster and more predictable. Requirements stop being a guessing game. Cross-timezone handoffs are clean — not a bottleneck. Stakeholders come to you early — not after things have already gone wrong. Key Responsibilities: * Go to stakeholders, understand the real problem behind each request, push back on weak briefs, and find the better solution — not just the easier one * Translate business needs into user stories, acceptance criteria, and backlog items the team can pick up and run with — no open questions left hanging * Run agile ceremonies: refinement, sprint planning, retrospectives — the team understands not just what they're building, but why * Keep business, development, and delivery connected across a globally distributed team — everything in English What This Role Is NOT: * Not a developer role — you won't write code * Not a passive role — you're not waiting for tasks, you're creating clarity * Not a Product Owner position — you'll shape and influence backlog decisions, not own them * Not a support or shift-based role Operating Model: Prague office, 2 days a week. Agile delivery. English is the working language — all communication, written and spoken, no exceptions. No shifts, no on-call. The team is internationally distributed; the bulk of the work happens through structured time-zone overlap, not pure async — but your written communication needs to carry weight when overlap ends. Tech context: Android/iOS (enterprise distribution), Node.js and Python backend, Jira, Confluence. Multiple product lines in scope.Interested? Apply or reach out directly:  | linkedin.com/in/jirisoljak No CV. Just your LinkedIn and a few lines about yourself. You'll be speaking directly with an experienced IT headhunter with hands-on IT background — 500+ hires. Expect a relevant discussion without HR fluff, with a clear understanding of technology, the market, and your real situation. Process: * Intro call (15–30 min) * Hiring Manager interview * We move fast, based on mutual availability * You always know where you stand — no ghosting, no black box EU work authorization required. No visa sponsorship.sponsorship.

Česká technologická firma, kterou před více než dvaceti lety založili dva kamarádi hned po škole. Řada lidí, kteří s nimi začínali, je tu dodnes — a to říká víc než jakýkoliv culture pitch. Firma se dávno posunula za hranici e-commerce. Dnes staví informační systémy, zákaznické portály a řešení na míru pro klienty z automotive, retailu i investičního sektoru. Všechno, co vytvoří, si také sama provozuje — na vlastní infrastruktuře, bez závislosti na externích cloudech, včetně vlastího AI stacku na vlastním hardwaru s LLM modely. Tým o zhruba 20 lidech pokrývá celý delivery: architekturu, analýzu, vývoj, testování i provoz. Funguje bez zbytečné hierarchie a bez přepálených buzzwordů. Developery tu berou jako partnery, ne jako kapacitu.Must-have Zapomeň na dlouhé checklisty. Tahle role stojí na třech věcech: * PHP + Laravel v produkci — víš, co se děje, když kód běží a používají ho reální uživatelé. Ne ze školy — z reálného projektu. * Schopnost dotahovat věci bez dohledu — převezmeš projekt, dovedeš ho do konce a nečekáš na zadání každého dalšího kroku. Problémy řešíš proaktivně. * Komunikace s klientem — dokážeš vysvětlit technické věci srozumitelně a bez omáčky. Překládáš realitu projektu, ne dokumentaci. Pokud nesplňuješ všechno — ozvi se. Doménový kontext (automotive, retail, investiční sektor) popisuje prostředí, ne filtr. Nice to Have * MySQL / MariaDB nad rámec CRUD — optimalizace dotazů, práce s většími daty * Zkušenost s Git workflow v týmu — PR, code review, branching strategie * Povědomí o serverovém prostředí a nasazení (Linux, Docker, CI/CD) * Zkušenost s e-commerce, portály nebo informačními systémy Tohle je kontext, ne tvrdé požadavky.Převezmeš část projektového portfolia a budeš za něj technicky odpovědný od začátku do konce. PHP/Laravel je nástroj — podstatné je, že se neomezuješ jen na kód. Navrhuješ řešení, děláš rozhodnutí a komunikuješ přímo s klientem. Pracuješ v přibližně 20členném týmu, který pokrývá celý delivery stack — architekti, analytici, developeři, testeři i servis. Reportuješ přímo Project Leadovi nebo CTO. Role vznikla s růstem firmy — projekty už nejde pokrýt jen juniorní kapacitou. Na svých projektech postupně přebíráš přímý kontakt s klientem. Technické problémy dokážeš vysvětlit srozumitelně a bez prostředníků. Architektonická rozhodnutí konzultuješ se seniory, ale máš u nich od začátku hlas — ne jen kódujíš zadané. Za rok máš na starosti 2–3 projekty a jsi na nich technicky klíčový člověk. Rozumíš tomu, jak firma staví a provozuje aplikace — a aktivně ovlivňuješ to, jak je bude stavět dál. Klíčové požadavky: * Navrhuješ a implementuješ webové aplikace, zákaznické portály a informační systémy v PHP/Laravel — od návrhu databáze přes API až po integraci s frontendem * Pracuješ na projektech od zadání po nasazení a postupně přebíráš technické vedení — komunikuješ přímo s klientem * Hlídáš kvalitu kódu v týmu — code review a best practices * Identifikuješ technické problémy včas a řešíš je dřív, než eskalují * Podílíš se na architektonických rozhodnutích — od prvního projektu máš hlas * Není to pozice pro juniora hledajícího vedení krok za krokem * Není to role, kde jen plníš tickety bez kontextu a zodpovědnosti za výsledek * Není to korporát se schvalovacími kolečky — rozhodnutí na projektech děláš ty * Není to čistě coding role — součástí práce je komunikace s klientem a technické vedeníZaujalo tě to? Napiš nebo pošli reakci: | linkedin.com/in/jirisoljak CV není potřeba — stačí LinkedIn profil a pár vět o sobě. Budeš mluvit přímo se zkušeným IT headhunterem s vlastní IT praxí — 500+ náborů. Relevantní diskuze bez HR balastu, s porozuměním technologii, trhu i tvé reálné situaci. Proces: Krátký úvodní call (15–30 min) Maximálně 2 kola — pokud věc dává smysl, rozhodnutí přijde i po prvním Před finálním rozhodnutím osobní setkání V každém kroku víš, kde jsi EU work authorization required. No visa sponsorship.