Senior Python Developer - full stack
<h2>Job Title </h2>
Senior Python Developer - full stack
<h2>Job Description</h2>
<div class="section" id="position-details">
<h1>Position Details</h1>
<ul class="simple">
<li><strong>Salary:</strong> EUR 70k annual base salary, with VSOP available for discussion</li>
<li><strong>Working Hours:</strong> Daytime working hours aligned with Central European Time (CET)</li>
<li><strong>Work Setup:</strong> Fully remote position</li>
</ul>
</div>
<div class="section" id="role-summary">
<h1>Role Summary</h1>
<p>We are hiring a <strong>Senior Python Developer</strong> to lead design and implementation across a <strong>stateful, workflow-driven platform built in Python</strong>. This role requires strong backend engineering fundamentals and the ability to work confidently across <strong>application logic, APIs, integrations, asynchronous processing, state management, testing, and production architecture</strong>.</p>
<p>You will work on a platform that combines:</p>
<ul class="simple">
<li>Python services and core runtime design</li>
<li>FastAPI-style HTTP APIs and callback endpoints</li>
<li>Redis-backed state and workflow persistence</li>
<li>Async external-provider integrations and retry handling</li>
<li>Multi-channel messaging backends</li>
<li>LLM-assisted workflow components</li>
<li>End-to-end testing of orchestration, contracts, and recovery paths</li>
</ul>
<p>This is a <strong>senior hands-on engineering role</strong>. We expect <strong>clear technical judgment, strong ownership, and pragmatic architectural decision-making</strong> without unnecessary complexity.</p>
</div>
<div class="section" id="responsibilities">
<h1>Responsibilities</h1>
<ul class="simple">
<li>Design, implement, and maintain <strong>production-grade Python services and runtime components</strong></li>
<li>Own complex backend features <strong>end to end</strong>, from domain modeling through rollout and regression coverage</li>
<li>Build and evolve <strong>stateful workflow systems, orchestration layers, and asynchronous processing</strong></li>
<li>Integrate with third-party APIs and external service providers in a <strong>reliable, observable, and fault-tolerant way</strong></li>
<li>Improve system correctness around <strong>retries, idempotency, error handling, and distributed state transitions</strong></li>
<li>Contribute across the stack including <strong>APIs, integrations, contracts, and tooling</strong></li>
<li>Write <strong>high-signal tests</strong> covering unit, integration, contract, and recovery scenarios</li>
<li>Review code rigorously and raise the bar for <strong>design clarity, maintainability, and runtime safety</strong></li>
<li>Collaborate with stakeholders to turn <strong>ambiguous requirements into robust implementation plans</strong></li>
</ul>
</div>
<div class="section" id="working-style">
<h1>Working Style</h1>
<p>We value engineers who are:</p>
<ul class="simple">
<li><strong>rigorous</strong></li>
<li><strong>pragmatic</strong></li>
<li><strong>comfortable with ownership</strong></li>
<li><strong>concise in communication</strong></li>
<li><strong>capable of handling both systems thinking and implementation detail</strong></li>
</ul>
<p>If you are strongest only in <strong>isolated backend CRUD development</strong> and do not enjoy <strong>stateful systems, integrations, or workflow complexity</strong>, this role is likely not the right fit.</p>
</div>
<h2>Restrictions</h2>
<ul>
<li><strong>Telecommuting is OK</strong></li>
<li><strong>No Agencies Please</strong></li>
</ul>
<h2>Requirements</h2>
<div class="section" id="required-experience">
<h1>Required Experience</h1>
<ul class="simple">
<li><strong>6+ years of professional Python development experience</strong></li>
<li>Strong experience with <strong>modern Python backend development</strong>, including <strong>type-aware design and asynchronous programming</strong></li>
<li>Strong experience designing and maintaining <strong>APIs and service boundaries</strong></li>
<li>Solid experience with <strong>Redis or comparable key-value/data-structure stores</strong> in production systems</li>
<li>Experience with <strong>event-driven or workflow-oriented systems</strong>, including retries, resumability, and state transitions</li>
<li>Experience integrating with <strong>external services, callbacks/webhooks, and long-running remote processes</strong></li>
<li>Strong testing discipline with <tt class="docutils literal">pytest</tt> and a clear understanding of <strong>regression prevention</strong></li>
<li>Comfortable working in systems that mix <strong>deterministic application logic with AI/LLM-assisted components</strong></li>
<li>Ability to work across <strong>backend, platform, and integration concerns</strong> without narrow specialization</li>
</ul>
</div>
<div class="section" id="preferred-experience">
<h1>Preferred Experience</h1>
<ul class="simple">
<li>Experience with <strong>FastAPI, Starlette, or similar Python web frameworks</strong></li>
<li>Experience with <strong>conversational systems, messaging backends, or multi-channel product flows</strong></li>
<li>Experience with <strong>queue-like async coordination patterns, webhook security, and idempotent callback handling</strong></li>
<li>Experience with <strong>localization/i18n pipelines and user-facing workflow systems</strong></li>
<li>Experience with <strong>Docker-based local development and production deployment workflows</strong></li>
<li>Experience working in codebases with <strong>strong architectural boundaries, typed domain contracts, and documentation-driven development</strong></li>
</ul>
</div>
<div class="section" id="technical-profile">
<h1>Technical Profile</h1>
<p>The right candidate should be comfortable with most of the following:</p>
<ul class="simple">
<li><strong>Python</strong></li>
<li><strong>Async I/O and coroutine-based service design</strong></li>
<li><strong>FastAPI-style API development</strong></li>
<li><strong>Redis-backed application state</strong></li>
<li><strong>Pytest-based automated testing</strong></li>
<li><strong>REST/webhook integrations</strong></li>
<li><strong>State machines, orchestration, and workflow engines</strong></li>
<li><strong>Payload/schema design and validation</strong></li>
<li><strong>Production debugging and operational reasoning</strong></li>
<li><strong>Docker-based development environments</strong></li>
</ul>
</div>
<div class="section" id="what-good-looks-like">
<h1>What Good Looks Like</h1>
<ul class="simple">
<li>Produces code that is <strong>clear, defensible, and easy to evolve</strong></li>
<li>Understands <strong>failure modes before they happen</strong> and designs accordingly</li>
<li>Makes <strong>deliberate tradeoffs</strong> instead of defaulting to abstraction or framework-heavy solutions</li>
<li>Can move between <strong>architecture, implementation, and debugging</strong> without losing precision</li>
<li>Writes tests that reflect <strong>real system behavior</strong>, not just happy-path implementation details</li>
<li>Communicates <strong>directly and professionally</strong> with strong technical judgment</li>
</ul>
</div>
<div class="section" id="seniority-expectations">
<h1>Seniority Expectations</h1>
<p>This role is not limited to ticket execution. We expect the engineer in this position to:</p>
<ul class="simple">
<li>identify <strong>weak spots in architecture and implementation</strong></li>
<li>propose <strong>clean solutions with minimal ceremony</strong></li>
<li>drive <strong>difficult features across multiple modules</strong></li>
<li>improve <strong>engineering standards through code review and design decisions</strong></li>
<li>and take responsibility for <strong>correctness in production-facing behavior</strong></li>
</ul>
</div>
<div class="section" id="nice-to-have-domain-exposure">
<h1>Nice-to-Have Domain Exposure</h1>
<ul class="simple">
<li><strong>Messaging platforms</strong> such as WhatsApp or web chat systems</li>
<li><strong>Identity, onboarding, or verification workflows</strong></li>
<li><strong>AI-assisted product experiences</strong></li>
<li><strong>Workflow engines and rule-driven application behavior</strong></li>
</ul>
</div>
<div class="section" id="employment-tax">
<h1>Employment / Tax</h1>
<ul class="simple">
<li>EU VAT compliance is a must for contractors</li>
<li>EU GDPR compliance is a must</li>
<li>EU work permit is a strong pre</li>
</ul>
</div>
<h2>About the Company</h2>
<p>Trusted Carrier is a <strong>German logistics technology company</strong> founded in <strong>2026</strong> on the initiative of the <strong>German Road Haulage, Logistics and Disposal Association (BGL)</strong>. The company provides a <strong>digital, open platform</strong> that connects <strong>shippers, transport companies, and drivers</strong>, enabling <strong>standardized and verified data exchange</strong> across the logistics ecosystem.</p>
<p>The platform focuses on delivering <strong>trusted and validated master data</strong> related to <strong>companies, vehicles, drivers, and transport equipment</strong>. This data is <strong>centrally managed, quality checked, and accessible via interfaces</strong> to support <strong>compliance, safety, and operational efficiency</strong>.</p>
<p>By digitizing documentation and workflows such as <strong>driver credentials, vehicle information, and transport requirements</strong>, Trusted Carrier reduces <strong>manual processes, waiting times, and administrative overhead</strong>. This enables more <strong>automated, transparent, and reliable supply chain operations</strong>.</p>
<p>Trusted Carrier primarily serves the <strong>transportation and logistics industry</strong>, with initial focus areas such as the <strong>chemical sector</strong>, and continues to expand into <strong>additional industries and European markets</strong>. The company’s goal is to drive <strong>end to end digitalization and data standardization across logistics networks</strong>.</p>
<h2>Contact Info</h2>
<ul>
<li><strong>Contact</strong>: Karlheinz Toni</li>
<li><strong>E-mail contact</strong>: <a class="reference external" href="mailto:jobs%40trustedcarrier.net">jobs<span>@</span>trustedcarrier<span>.</span>net</a></li>
<li><strong>Web</strong>: <a class="reference external" href="https://www.trustedcarrier.net">https://www.trustedcarrier.net</a></li>
</ul>
</div>