Benjamin Becht Deutsch Contact

About me

Twenty years in the domain, then the software.

I'm Benjamin Becht — certified precision-machining master (Feinwerkmechaniker-Meister) and Betriebswirt (HWK), with more than twenty years in precision manufacturing. Before I wrote software for maintenance, I did the work: setup, calibration, first commissioning, and twelve years of technical customer support for injection-moulding machines across 35+ countries.

That domain is the point. The software I build — ProAct above all — supports exactly the work I used to do, which is why it fits how maintenance teams actually operate.

Career

Where I come from.

Technical customer support · ARBURG

Jul 2013 – Mar 2025

Technical support and complaint handling for injection-moulding machines across more than 35 countries.

  • Cut the defect rate in the rotary-unit quality programme by more than 90% within a year
  • Key user of the SAP rollout, including the requirements specification
  • KPI and dashboard work → +22% revenue, +10% team efficiency
  • Resolved production bottlenecks → +50% operational efficiency
  • Manufacturer training in preventive maintenance (ARBURG, 2015)

Machine setter · ARBURG

Jun 2011 – Jun 2013

Setup, first commissioning, and calibration of injection-moulding machines.

Recent practice

PureTech Water — remote practicum.

June – August 2026 · remote

A remote engineering practicum: deployment via Git and GitHub Actions, a test environment mirroring the live shop, and a technical write-lock protecting production against writes. I built 56 of my own Python tools and shipped 296 SEO data fields live, error-free.

Further training

Rounding it off.

The formal software training comes after the domain and the built work, not before it.

  • Software Engineering certificate — WBS Coding School (July 2025 – August 2026)
  • Microsoft AZ-900 (May 2026) · PCEP (October 2025) · Google Data Analytics (February 2023)

Languages

Languages.

  • German — C2
  • English — C1
  • Chinese — basics (HSK 3)

Operating principles

How I approach the work.

Simple beats clever

The best code is the code the next person can read at 2 a.m. during an incident. I optimise for clarity and changeability before cleverness.

Make trade-offs explicit

Every architecture is a set of trade-offs. I write them down — in ADRs, in PRs, in plain language — so decisions are owned, not stumbled into.

Strong typing, explicit boundaries

I prefer strict types and explicit exception handling over loose code and silent fallbacks. Errors should be loud and local, not mysterious and global.

Ship value incrementally

Big-bang rewrites are where projects go to die. I favour migrations and releases that deliver value in small, reversible steps.

Tests are part of the work

ProAct ships with 285 automated tests because a maintenance system has to be trustworthy. Tests are not a phase after the build — they are the build.

Get in touch

Open to a conversation.

I'm looking for a permanent role. Email is the best way to reach me.

Contact