Hello, my name is
Marshall Laszlo Toth!

On-site work involved clearing, structuring, and stabilizing areas for measurement while information moved from physical reality into drawings, notes, and formal records. I prototyped ideas such as automated plan drawing with a pen plotter, but quickly encountered the hard limits of regulation, tradition, and irreversible data capture.

This experience grounded my systems thinking outside software. It showed that real-world domains often hide the most unforgiving constraints; exactly where the patterns of physical-to-digital loops and time-sensitive synchronization become critical.

The work spanned modern applications and content-driven Neos CMS projects for industrial and logistics clients. A large part of the role involved navigating existing architectures and client-specific workflows rather than building from scratch, constantly balancing clean engineering with the realities of long-lived systems.

Toward the end I operated in a heavily reduced team, maintaining delivery with high autonomy and context switching. This environment sharpened my ability to sustain heterogeneous systems when resources and stability continuously decline.

My focus was on building reliable data flows between external platforms and the internal domain, handling inconsistent structures and ensuring integrity during client migrations. In parallel I created process-oriented interfaces that translate complex backend logic into safe, step-by-step workflows to reduce user error.

The role started in a rapidly scaling remote team where onboarding and alignment were still evolving. I chose to conclude the engagement early when the gap between expected impact and actual velocity became clear, prioritizing efficient use of time and resources for both sides.

The platform supports board-level decision-making in high-stakes enterprise environments where data integrity and traceability are non-negotiable. Entering this environment meant operating inside a system whose scale and interconnectedness exceeded what could be fully reasoned about locally.

This role became a turning point. Internalizing stricter typing, asynchronous patterns, and distributed thinking alongside the legacy codebase taught me how to build confidence in partially understood architectures and reinforced that the hardest work in modernization is keeping the old system trustworthy while it evolves.

The platform combined customizable storefronts with scalable backend processes to support rapid onboarding and high variability across partners. The core challenge was synchronizing three fundamentally different domains where delays or mismatches had immediate physical consequences.

Although the project later shifted direction due to organizational decisions, the experience provided deep insight into building platforms where the boundary between digital and physical must remain tight and resilient.

My work spanned booking flows, partner management tools, and public APIs built on Laravel, Vue.js, GraphQL, and Azure. A significant contribution was improving partner-side operations (internal calendars, communication, and automation) to reduce manual coordination and data inconsistencies.

Operating in a distributed, multi-national environment reinforced how directly timing and data accuracy affect business outcomes when digital systems must stay aligned with constantly changing physical hotel capacity.

The system integrated TechTeamer’s FaceKom remote identification with Microcredit’s lending flow, combining document submission, biometrics, and automated scoring. My team owned the core system of record responsible for customer states, loan lifecycles, and audit trails across distributed components.

This experience exposed how digital trust is constructed in practice, every approved loan being the result of multiple systems agreeing on a single high-stakes decision despite constant external dependencies.

The core work was the API layer enabling real-time synchronization of customers, stock, orders, and shipments. I also contributed to one-click onboarding for major platforms and to operational tools such as handheld pickers and packing station coordination with shared printers.

These systems had to function under real warehouse constraints where timing and reliability directly determined throughput. The experience sharpened my understanding that physical-to-digital loops are unforgiving; errors are not exceptions but disruptions in physical flow.

The platform combined multi-language storefronts, complex product narratives, and high-touch support flows with deep fulfillment logic. Because soap production was craft-driven and used natural ingredients, stock and availability had to stay aligned with real-world manufacturing timelines and variability.

In parallel I worked in service desk, acting as a bridge between business operations and the system. This constantly exposed the friction points where digital promises meet physical limits, reinforcing the need for adaptable, understandable software.

The work included inventory systems, early configurators (with enormous combinatorial complexity), and experimental projects like a low-cost POS for Érték Bár. I also gained hands-on operational insight by working as a bartender during high-traffic events.

This period laid the foundation for how I think about software today: not as isolated applications, but as part of larger, real-world systems shaped by manufacturing constraints, logistics, and human pressure; exactly where the patterns I still use today first emerged.