Payment products you see in stores every day — behind them sits payment infrastructure that has to work without exception. This role is inside it.
The team is growing and looking for a backend engineer who takes ownership of specific microservice components — not someone filling tickets. The work you do runs in production. You'll know why every line of code exists.
The team is communicative — grooming is a real technical discussion, not a planning ceremony. If you think out loud, enjoy solving things together, and don't need an architectural title to join a design discussion, you'll fit.
Medior profile with Java + Spring Boot + microservices foundation — the rest can be learned on the job. This is not a role for someone who wants to be a senior architect from day one.
An international FinTech company operating payment systems used daily by thousands of merchants and millions of customers. The infrastructure handles real-time transactions — a product with real impact that you can see.
The team is technically serious but social. Code gets reviewed, architecture gets discussed — and people enjoy it. No corporate formalism. A new colleague gets space for proper onboarding and sets their own pace. Within a year, you'd own a component.
Job description
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 — 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 — partly because of you.
Key Responsibilities
- Build new product features and drive modernization of existing payment application components
- Participate in grooming and planning — understand the 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 code reviews — 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
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.
Working language: Czech or Slovak internally; English for documentation and cross-team communication. Scrum-based team rhythm, async-friendly for deep work.
The team's default mode is conversation — problems get talked through before they get coded. If you naturally communicate and think out loud with others, you'll fit.
Requirements
Core Requirements
- **Java + Spring Boot** — 3+ years of commercial hands-on experience (not just familiarity)
- **Microservices architecture** — real experience with event-driven systems or message brokers (Kafka, RabbitMQ or equivalent)
- **Stable career trajectory** — 3+ years at a single employer in your most recent role
- **Pure backend focus** — if frontend regularly forms part of your work, this won't be the right fit
Profile
- Czech or Slovak — conversational level required; English for written communication
- **Communicative and dialogue-oriented** — you can explain a technical decision to someone outside engineering; code review isn't a ritual for you
- **Humble** — "I don't have that, but I have something similar and I'll get up to speed" is a stronger answer than bluffed knowledge
- Proactive approach to technical design, not just implementation
- Comfortable in cross-functional teams
This is a pure backend role. If frontend is even occasionally part of how you work — this won't be the right fit.
Nice to Have
- Apache Kafka or Apache Camel — useful if you have it, not a hard requirement
- NoSQL databases (MongoDB or similar)
- Cloud platforms (AWS or equivalent) — DevOps handles infra, you work with the services
- FinTech or payment systems background — faster onboarding, not a condition
These are genuine advantages — not hard filters. If the core requirements fit, reach out.
Offer & Terms
Why This Is Worth Your Time
- **Real ownership in production** — own specific microservice components in a live payment system used by thousands of merchants daily
- **A team that actually enjoys working together** — communicative, no corporate formalism, interview is a conversation
- **Remote-first without compromise** — no relocation, no commute required
- **Medior is welcome** — onboarding takes a year, the client knows it and plans for it; you don't need to be super-senior
- **Architectural input from day one** — design discussions are open, not reserved for seniors
Compensation & Benefits
- **Salary: CZK 120,000 – 170,000 / month + 10% annual performance bonus**
- 5 weeks vacation + 5 additional paid days off
- Annual leisure allowance: CZK 18,000 (vacation, sports, activities)
- Meal vouchers fully covered by employer
- Pension contribution
- Language courses (if needed)
- Mental health support + online medical services
- Flexible working hours + hybrid mode
- Office refreshments
More information
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 IT headhunter with hands-on experience — 450+ hires. Expect a relevant discussion without HR fluff, with a clear understanding of technology, the market, and your real situation.
**Process:**
1. Intro call (15–30 min)
2. Technical interview with the Hiring Manager
3. 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.
