I help SaaS teams build product features, connect business systems, and work through production issues. Hands-on Python and Django engineering, with the APIs, background jobs, and infrastructure around it.
My core toolsPythonDjango / DRFPostgreSQLRedisCeleryDockerCI/CD
Selected work
Real problems. My part in solving them.
The problem, my contribution, and the current stage of each project.
MXFend
Own product / Email authentication
Public tools
A product I’m building to help people check their email-domain configuration and understand what the results mean.
My contribution: Building public diagnostic tools and connecting SPF, DKIM and DMARC findings with actionable explanations.
What’s available today
The public tools cover email authentication and domain diagnostics, including SPF, DKIM and DMARC. The challenge is turning protocol-level findings into explanations people can act on. Explore MXFend ↗
Integration work connecting an e-commerce platform with an ERP, including order data and the surrounding business workflow.
My contribution: Python / Django integration work, API adapters, order mapping, background processing and diagnostics.
Engineering approach
Separate platform adapters keep API-specific logic away from the business workflow. Explicit data mapping and background jobs make the integration easier to inspect, test and troubleshoot. The current stage is pilot integration and testing.
Work on a media-processing system with job APIs, worker queues, storage integration, and video encoding.
My contribution: Worker configuration, storage integration, encoder validation and deployment infrastructure.
Engineering approach
My work includes worker configuration, storage integration and encoder validation. The system is in development; I’m currently working through encoder validation and the behaviour of the processing workflow.
I’m an independent backend engineer based in Czechia. Python and Django are my main focus; experience with PHP, Vue/Nuxt and infrastructure helps me understand the systems around the backend.
My work spans product development, business integrations and production troubleshooting. I work independently while keeping the team involved in decisions that affect the product, its operation or future maintenance.
Where I can help
When your team needs backend depth.
Hands-on engineering for product work, connected systems and production challenges. The selected projects show how these areas meet in practice.
01
Backend & SaaS development
When a product needs new capabilities or an existing backend needs extending: Django application logic, data models and REST APIs shaped around the product workflow.
When information has to move between systems: API adapters, data mapping, webhooks and background processing, with failures that can be inspected and investigated.
When a processing job fails or an application behaves differently in production: investigate across the stack, validate worker and encoder behaviour, and work on Docker environments and CI/CD.
I join SaaS teams as an independent backend engineer, with a preference for long-term collaboration. I can take on a defined backend workstream or contribute alongside your existing engineers.
I work remotely on a B2B basis. I invoice through my Czech business and work on an hourly basis, with a maximum capacity of 120 hours per month.
I work independently and keep collaboration async-first. Meetings and overlap are agreed around the work; my schedule is flexible, without fixed eight-hour daily shifts.
Understand the contextDiscuss your product, the current system and the problem your team needs to solve.
Agree the scopeDefine responsibilities, priorities, communication and monthly involvement.
Build and verifyImplement the work, review decisions with the team and document what matters for maintenance.
Remote from CzechiaEU B2BUp to 120 h / monthAsync-first
Let’s work together
Tell me what your team is working on.
Email me about your product and the backend work you need help with. We can start by clarifying the scope and whether the collaboration is a good fit.
What to include in your first message
A short description of your product and stack, the main challenge, and your expected monthly involvement is enough to start.