We’re a successful Czech FinTech company (non‑bank lender) entering a new phase: evolving a fast‑moving startup product into a stable, sustainable enterprise platform. We support an existing legacy system while building a modern, next‑generation solution in parallel – and we’re expanding our team to make this transition.

Joining us means working with a modern tech stack, shaping architecture, and influencing how a proven startup grows into a long‑term, resilient product.

What We Offer

Meaningful Technical Growth

• Deep, hands‑on work with modern Python tooling and cloud technologies
• Real ownership of architecture and long‑term technical direction

Build Engineering Culture You Can Be Proud Of

• Strong focus on code quality, clarity, and maintainability
• Pragmatic decision‑making — no over‑engineering, no unnecessary bureaucracy
• A team that is actively shifting toward thoughtful engineering over rushing features

High Impact on the Product

• Direct influence on architectural decisions and system evolution
• Close collaboration with product and business teams

Flexible, Modern Work Environment

• Fully remote work setup with flexible working hours with the ability to collaborate during CET business hours
• Async‑friendly communication that supports deep work
• International team with diverse perspectives and experience

Compensation & Benefits

• Competitive salary and yearly bonuses
• Paid time off and sick-days

Your role

As a Python Engineer, you will:

• design product architecture and implement simple and complex features,
• suggest improvements across technical and product areas,
• help break down epics and provide technical estimates,
• work closely with other developers, QA engineers and managers,
• work with business consultants to understand and address needs of business.

What skills should you have?

• Senior-level back-end Python programming with a proven track record of delivering systemsto production.
• Developing clean modules and maintaining high code clarity.
• Designing and implementing backend services and APIs.
• Thinking in terms of maintainability, clarity, and long-term evolution of systems.
• Hands-on experience with MongoDB or similar document databases,
• Understanding of message queues and event-driven communication patterns,
• Ability to quickly learn new frameworks, tools, and patterns when needed,
• Have strong testing culture: write unit (component, integration, and end-to-end tests whenapplicable) for your features.
• Using type checking and static analysis as part of daily workflow.
• Ability to provide thoughtful, constructive code reviews and have commitment to engineering excellence.

Additionally it would be great if you:

• have experience in FinTech / lending / payments domain,
• have experience with AWS (or GCP, Azure) services and cloud infrastructure,
• have solid Docker skills and understanding of containerized environments,
• are able to work with CI/CD systems (GitHub, GitLab) and are not afraid to write/setuppipeline yourself,
• are comfortable with infrastructure-as-code and automation practices.

Tech Stack

Tools that we currently use or plan to use in the future.

• Python 3.1X
• FastAPI,
• Pydantic,
• Pytest
• Mypy (We’re planning to try 'ty')
• ruff
• uv
• Docker
• AWS (SDK, CDK, CloudFormation, EC2, ECS, Fargate, S3, Dynamo, Kinesis, SQS, AWSLambda, CloudWatch, SSM)
• OpenTelemetry, Prometheus, Grafana.
• Ansible
• GitLab CI/CD

This role may not be a good match if

• You need close guidance, step‑by‑step direction, or struggle to self‑organize your work.
• Ambiguous requirements frustrate you, or you prefer others to fully define solutions before you start.
• Writing tests feels like overhead, or you tend to ship features without strong test coverage.
• You resist code reviews or see them as a formality rather than a collaborative quality practice.
• Cloud infrastructure makes you uncomfortable, or you avoid DevOps‑related tasks even when they’re simple.
• Async communication feels slow or difficult, and you rely heavily on synchronous discussions to move forward.
• You prefer sticking to familiar tools and patterns rather than learning new ones when the situation calls for it.
• You avoid ownership, or you tend to over‑engineer or under‑engineer solutions instead of aiming for pragmatic clarity.

Hiring Process

We keep our process simple, transparent, and respectful of your time. You’ll always know what to expect.

1. CV Screening
We review your background, experience, and projects to understand whether the role aligns with your strengths.

2. First Interview — Experience & Fit
A conversation where we introduce ourselves, discuss your experience, and explore your technical background. This is a two‑way conversation to see whether there’s a good mutual fit before moving to deeper technical work.

3. Second Interview — Live Coding & Architecture
A practical session focused on real engineering work. We’ll:

• discuss architecture, system design, and trade‑offs
• look at real code samples together and talk through improvements
• do a small live‑coding exercise to understand how you think and structure solutions

This session is collaborative, not adversarial — we’re interested in your reasoning, clarity, and approach to problem‑solving.