Still Point / full portfolio
devk061
Product-systems engineer focused on control planes, customer runtimes, workflow-heavy tools, and AI-enabled product surfaces. The strongest story is deliberate operational clarity, not visual noise.
Open the anchored notes or scroll for the full shortlist-led route.
Systems
Product systems should stay legible long after the first deployment.
The strongest work separates control surfaces from customer runtimes when that improves safety, clarity, and release discipline.
Read the profileStack
Control planes, runtimes, contracts, and delivery discipline sit at the center.
The stack changes per product, but the pattern stays constant: authority design, typed contracts, hosted verification, and clear product framing.
See the stackProjects
The work is grounded in flagship repos with real workflow depth.
Booking Admin, Booking App, FinFlow, InvoiceLab, and PromptFlow are the current public proof because they show ownership, product depth, and operational clarity together.
View the projectsModel
The current focus is deepening product systems without losing clarity.
Hosted verification, documentation that helps, and AI features that behave like product software are now the center of the public story.
See the operating modelContact
If the work needs precision, write directly.
contact@devk061.de Open contact sectionAbout
Product systems with clear operational authority.
I build product systems where the operational model is explicit. The strongest pattern in my work is separating customer runtime from operator authority when that makes the system easier to ship, verify, and reason about.
Booking Admin and Booking App are the clearest proof of that thinking. FinFlow, InvoiceLab, and PromptFlow extend the same story into finance, document workflows, and AI-enabled product tooling.
The through line is consistent: workflow depth, typed contracts, hosted verification, and documentation that helps people operate the system instead of guessing how it works.
Authority boundaries
Typed contracts
Hosted verification
Calm handoffs
Open to
Product, platform, and full-stack roles
Best aligned with work that values systems ownership, workflow depth, and product surfaces that stay operable after launch.
Current focus
- Control-plane and runtime separation where it matters
- Workflow-heavy tools with clear product framing
- AI surfaces that still behave like software engineering
Skills
The toolkit follows the product system, not the other way around.
Authority design
Control surfaces, release authority, and runtime verification when safety matters.
Product runtimes
Customer-facing systems that stay clean because the authority model is deliberate.
Workflow systems
Business flows where rendering, approvals, exports, or sync logic carry the real value.
AI tooling
AI features that improve the workflow instead of sitting beside it as a gimmick.
Delivery discipline
Hosted verification, environment gates, and delivery loops treated as part of the product.
Docs and quality
Source-of-truth files, readable runbooks, and contracts that keep the repo operable.
Projects
Flagship repositories that carry the public story.
01
Control plane
Booking Admin
Internal platform for tenant configuration, release state, runtime inventory, and deploy promotion. This is the strongest evidence of systems ownership because it treats operator authority as a product surface.
- Publication authority and runtime verification
- Role-aware admin UX and release-readiness evidence
- Platform engineering with product consequences
02
Product runtime
Booking App
Customer-facing runtime intentionally separated from the control plane. It shows product UX, hosted-lane delivery, and why the Booking split is an architectural strength rather than a docs artifact.
- Same-origin manifest handling and hosted smoke proof
- Customer runtime kept distinct from admin authority
- Multi-lane deployment with typed contracts
03
Workflow product
FinFlow
Cross-platform personal finance product with sync-heavy flows, assistant orchestration, and cloud-backed state. It reads like a real product because the value is in workflow continuity.
- Stateful product logic across mobile and web
- Assistant tooling connected to real product workflows
- Cloud-backed product operations, not a static demo
04
Vertical workflow
InvoiceLab
German invoice authoring workspace with Chromium PDF rendering and EN 16931 export. The signal is document correctness, shared contracts, and a workflow where the business domain drives the engineering shape.
- Document rendering, exports, and compliance in one surface
- UI, renderer, and shared contracts kept coherent
- Difficult workflow made product-like and testable
05
AI tooling
PromptFlow
Prompt engineering product surface with web, API, and mobile layers, evaluation workflows, and multi-model tooling. The AI angle stays credible because the repo reads like product software.
- Prompt tooling, auth, and persistence shaped as one system
- Eval workflows and release channels support real iteration
- AI features framed as engineering, not theatre
Methods
Operating model that repeats across the strongest work.
Separate authority from runtime
Keep control surfaces distinct when safety and clarity improve.
Use typed contracts aggressively
Schemas and shared contracts keep every surface aligned.
Treat hosted verification as part of the feature
Deploy lanes, health contracts, and smoke evidence are product work.
Make docs operational
README files, status ledgers, and docs hubs should reduce ambiguity.
Use AI where it changes the workflow
Assistants, evals, and prompt tooling belong inside real product systems.
Contact
Open to roles that value product depth and operational clarity.
Looking for engineering ownership, not just implementation?
The best fit is work where product, architecture, and operational clarity all matter. If the team values control-plane thinking, workflow depth, and systems that can actually be operated, that is the right conversation.
Product, platform, and full-stack roles all fit when they need real systems design instead of a narrow feature-only contribution.
CV and deeper repo walkthroughs are available on request.