Senior Python Engineer, Platform Libraries (m/f/d)

Your mission

• Own Bus, the CDK, and the core stack. Features, tests, CI, releases, and deprecations across the connectors already running in production.
• Extract abstractions from real work. When the same pattern shows up in the third connector, it becomes a library feature. You're the one who notices, and the one who does it.
• Make the docs good enough to remove yourself. An outside contributor should be able to build a connector on our libraries without a call.
• Set the quality standard. You define what "tested" means before a connector reaches a customer, and you make it stick. 2. The Shipper: build connectors on real instruments
• Ship production connectors end to end. Spec sheet, physical device, protocol, proof of connectivity, tested connector, live customer. Independently.
• Reverse-engineer what isn't documented. Roughly half the instruments we touch have incomplete or wrong docs. Packet captures, trial and error, vendor calls.
• Work with the workshop. Our Connector Factory team gets instruments development-ready. You take it from there.
• Talk to the people who use it. Automation engineers and scientists at biotech and pharma customers. Their constraints shape what the libraries need next.

• Deep Python: 5+ years of writing production Python other people depend on. Async, typing, packaging, testing. You've designed APIs that other engineers built on, not just glue code.
• You've debugged a real protocol against real hardware: gRPC, serial, TCP, OPC UA, CAN, USB. Which one matters less than having sat with a packet capture and a device that won't respond.
• You ship without a spec: When the documentation is wrong, you reverse-engineer, instead of filing a vendor ticket and waiting.
• You build for other developers: An SDK, a library, an internal platform. Something where your job was making other engineers faster.
• Located in Munich: The instruments are physically here at WERK1.

Nice to have

• SiLA 2, or another device abstraction and interoperability standard
• Lab automation, scientific instruments, or a life science background
• Open source maintainership with actual external contributors
• C, C++, .NET, or Rust, for the vendor DLLs and drivers we end up wrapping
• Docker, Kubernetes, edge deployment
• German, for vendor conversations

Probably not a fit if Better to say this now than in week 6.

• Your Python is all APIs and databases and you've never debugged a physical device.
• You'd want two quarters to redesign the library architecture before shipping a connector.
• You like shipping integrations but have no appetite for going back afterwards to generalise, test, and document.
• You want the library work without the customer deadlines. Both are in the job.
• Connectors: Python, SiLA 2, gRPC, zeroconf
• Workflows: Python, Prefect
• Services: TypeScript, NestJS, Prisma
• Web: TypeScript, Vue 3, Nuxt 3, TailwindCSS
• Cloud: Docker, Kubernetes, Helm, AWS, Terraform
• Databases: PostgreSQL
• We offer
• Why You’ll Love Working Here

• Impactful Work: Work on meaningful products in an ambitious, supportive environment as part of a team revolutionizing connectivity in laboratory automation to enable breakthroughs in science and technology.
• Work with the Best: Join a talented, ambitious team in a dynamic, transparent environment where your ideas help shape the company's future.
• Collaborative Culture: Team-oriented environment focused on continuous knowledge-sharing and professional growth, with regular team-building activities including offsites and work-cations.
• Flexible Environment: Backed by an employee-first culture that supports flexible remote work and PTO, with our main office in the vibrant WERK1 Munich hub. Hardware debugging happens there, so being regularly onsite is a must.
• Attractive Compensation Package: Competitive compensation with growth potential in a VC-backed startup, along with a laptop of choice, annual productivity budget, and a growing list of benefits for sports, mobility, insurance, and more.
• Tech stack
• A non-exhaustive list of our main technologies and tools used for a given task: