Zoltan R.

Built a full end-to-end mental health platform (MindLibra.hu) as sole developer: therapist profiles, online booking via WP Amelia, client portal, and conversion-focused landing pages. Delivered as a fast-moving MVP, intentionally choosing WordPress + Stripe Connect over a custom stack to optimise for speed, iteration velocity, and non-technical operability.

The core technical challenge was Stripe Connect: routing each payment in real time between the clinic and the correct therapist's Express account, handling split billing, payouts, and webhook reconciliation reliably. This required deep integration work beyond standard plugin territory.

Covered the full scope independently — frontend (Elementor, custom JS), backend logic, payment infrastructure, user onboarding flows, and production performance fixes. The platform launched successfully, onboarded real therapists, and began live client acquisition.

Key takeaway applied: in early-stage products, speed of execution and business validation outweigh architectural complexity — but the payments layer still required serious custom engineering.

Built a B2B wholesale product catalog for ADOB Kft., a Hungarian mixed-goods distributor replacing a legacy catalog with a modern web application: a public, SEO-optimized storefront for retail buyers, plus an admin panel where the client independently manages thousands of SKUs via Excel imports — no developer involvement in day-to-day operations.

The heart of the system is the Excel import pipeline as single source of truth. Large files are processed asynchronously with BullMQ, with real-time progress tracking in the admin UI. Each batch resolves brands and categories by name with conflict detection and deduplication, generates hierarchical URL slugs idempotently across imports, computes per-product checksums to skip unchanged rows, and queues image fetching/resizing separately so media never blocks product writes. Category hierarchies use a closure table pattern for efficient ancestor/descendant queries at any depth.

Search runs on Typesense (chosen over Elasticsearch for operational simplicity on a single VPS), indexed incrementally on import completion — faceted filtering by brand, category, and price is sub-100ms in production. The system also integrates the Webshippy fulfillment platform API, syncing product stock automatically as a scheduled background job.

Architecture: two independently deployed services. Frontend: Next.js on Vercel, server-rendered product and category pages, Tailwind CSS with a custom design system on the client's brand. Backend: NestJS REST API with PostgreSQL/Prisma on a Hetzner VPS. Security hardening: Nginx GeoIP2 geo-blocking, endpoint-level rate limiting, Fail2ban on login endpoints.

Delivered solo, on a fixed scope and a hard legal deadline requiring a demonstrably live web presence — launched on schedule. Post-launch, the engagement transitioned to a managed hosting contract: server operations, automated daily backups, SSL management, and reactive support.

Worked as a senior frontend engineer at Job&Talent, one of Europe's largest workforce and staffing platforms, embedded across multiple product squads in a fast-moving, high-pressure environment.

The core technical challenge was migrating a large internal admin platform from a monolithic Next.js application to a micro-frontend architecture using Webpack 5 Module Federation. At the time the ecosystem was immature, documentation was sparse, and many integration patterns had no established precedent. Much of the work involved experimentation, custom tooling, and solving architectural edge cases directly in production.

Led the full migration architecture, designed independent deployment pipelines that allowed multiple squads to ship in parallel without blocking each other, and built custom Webpack transformation plugins to handle compatibility and runtime integration requirements. Delivered product features end to end, integrated analytics and feature flagging across distributed frontends, and drove CI/CD improvements, developer experience upgrades, and cross-team engineering alignment.

The transition meaningfully improved development scalability by enabling independently deployable frontend applications and reducing coordination overhead between squads.