Backend
Building the services, interfaces, and data boundaries that keep products dependable as they grow.
Hendrik's path into technology did not begin through a traditional software engineering route. It began with curiosity, self-directed learning, and the need to understand how useful systems are actually put together.
Programming became a practical way to turn that curiosity into working products. Over time, he built software across multiple domains, moving between backend engineering, data processing, automation, web applications, and lower-level systems work.
The common thread is depth. Hendrik is interested not only in using a framework, but in understanding the architecture, data flow, and behavior beneath it. That approach eventually led him to found TradeOps and build the platform from the ground up.
Developed practical technical foundations before moving into software engineering.
Worked in technical environments where precision, planning, and translating requirements into practical output mattered.
Built programming knowledge independently through study, experimentation, and complete software projects.
Built software around operational requirements, automation, data, and real business workflows.
Delivered custom software directly to clients across web applications, backend systems, automation, and technical problem solving.
Leads the product vision and technical implementation of the TradeOps platform.
Hendrik is the founder and technical builder behind TradeOps. His role spans product vision, software architecture, implementation, and the operational details required to turn an idea into a working platform.
The work crosses languages and layers, but the objective stays consistent: build software that solves a real problem and remains understandable enough to operate responsibly.
Building the services, interfaces, and data boundaries that keep products dependable as they grow.
Turning fragmented information into repeatable pipelines, analysis, and operational software.
Taking products from a working concept to a complete application used through real business workflows.
These public projects show the range of Hendrik's engineering interests, from backend architecture and data systems to product workflows and technical tooling.
A market-research platform built from concept to implementation, combining software architecture, data processing, AI-assisted workflows, member delivery, and product operations.
View TradeOps Product EngineeringA software product built around practical user workflows, structured application logic, and a production-minded implementation.
View on GitHub Data SystemsA data-focused project exploring how domain information can be processed, organized, and presented as a useful software system.
View on GitHub Backend ArchitectureAn API-centered banking system project focused on backend boundaries, business rules, and dependable data flows.
View on GitHub Systems ToolingA technical bridge for browser-driven workflows, reflecting an interest in automation, integration, and software internals.
View on GitHubHendrik has created and published two Udemy courses, including teaching Pine Script and practical programming concepts. Teaching has strengthened his ability to break technical ideas into understandable steps without removing the details that make them useful.
View Udemy profileAs an independent software developer, Hendrik has completed more than 80 Fiverr projects. The work has involved building custom solutions, working directly with clients, and translating business requirements into technical systems that can be used in practice.
View Fiverr profileAlongside software development, Hendrik maintains an interest in understanding how software works internally. The work is practical and exploratory, connecting reverse engineering techniques with better vulnerability awareness, security tooling, and more secure software development.
All security research is performed only on systems owned by Hendrik or where explicit authorization has been granted.
A local security-research workspace built to reduce noise without removing the operator from the investigation. Hunter explores an evidence handoff model for Burp Suite, while ReconPilot implements a Rust-based pipeline for collection planning, normalization, enrichment, graph correlation, prioritization, and reporting.
The architecture keeps external-tool execution and AI reasoning behind separate, explicit controls. Model output is treated as a hypothesis that must cite available evidence and still requires analyst validation.
View project on GitHubConcrete engineering areas represented in the current research codebase.
Explicit include and exclude rules, dry-run defaults, and separate execution controls keep operator intent visible.
Structured collection, normalization, enrichment, and graph correlation turn fragmented observations into an application map.
Local artifacts are analyzed for API families, schemas, authentication indicators, objects, routes, and JavaScript findings.
Routes, entities, trust boundaries, diffs, and workflow transitions are connected before an analyst assigns priority.
Codex is optional, invoked deliberately, and used to form hypotheses from bounded evidence rather than validate findings.
Machine-readable outputs, casefiles, validation reports, and append-only audit events preserve how conclusions were reached.
Technology is a tool. Building powerful systems requires equal attention to reliability, security, and responsible use.
Hendrik focuses on creating useful software while continuously improving his understanding of how systems behave.
For professional conversations, project context, or technical work, use any of the links below.