Available for Head of Frontend roles · Frontend Architecture · Engineering Leadership

Frontend Architect · Engineering Leader | Multi-Tenant & White-Label Platforms | JavaScript, Vue.js, Nuxt.js | PHP, Symfony

Frontend Architect and Engineering Leader with experience in JavaScript, Vue.js, Nuxt.js, PHP and Symfony. I design and scale frontend architecture and engineering organizations in fintech and crypto environments, focusing on multi-tenant and white-label platforms, system design and engineering leadership.

Miroslavs Lepickis

Scalable frontend architecture

Vue.js, Nuxt.js and JavaScript systems designed for performance, maintainability and long-term scalability.

Multi-tenant & white-label platforms

Embedded and partner-driven systems with strict isolation, contracts and integration stability.

Engineering leadership

Team scaling, ownership models and delivery systems for high-complexity product environments.

Industry context

Six years at Paybis — a high-risk crypto and fintech platform processing $5.5B in transactions across 250+ countries and 6.9M users.

Leadership note

Frontend is managed as a strategic product capability, not as a purely presentational execution layer.

Focus

My work sits at the intersection of product strategy, frontend architecture and organizational design. I build systems that scale technically, structurally and culturally.

What I do

  • Define long-term engineering and frontend strategy aligned with business goals.
  • Design architectures that support growth without destabilizing delivery.
  • Build scalable team structures with clear ownership and accountability.
  • Establish engineering systems that make shipping predictable and measurable.
  • Integrate performance, reliability and security as systemic constraints.

How I operate

  • Start from risk, compliance and business constraints.
  • Align architectural decisions with roadmap reality.
  • Prefer incremental evolution over disruptive rewrites.
  • Document principles and decisions through ADRs and clear standards.
  • Build feedback loops through metrics, monitoring and postmortems.
Engineering LeadershipFrontend StrategyOrganizational DesignArchitectureDelivery SystemsSecurity & Performance

Scope

I operate in environments where engineering decisions directly affect revenue, compliance and user trust.

Regulated & high-risk domains

Compliance constraints shape architecture, UX and operational posture.

Revenue-critical journeys

Identity, onboarding, payments and transactional systems where reliability impacts growth.

Distributed & embedded systems

Partner integrations, iframe-based widgets and contract-driven compatibility across environments.

High-risk environments

In regulated products, weak ownership boundaries become delivery and compliance risks.

1. From release events to predictable delivery

Context

Manual coordination created release stress and scaling risk as the organization grew.

Constraint

Product velocity could not slow down.

Action

Redesigned the delivery system. Introduced trunk-based development, lightweight quality gates and shared ownership standards.

Outcome

Shipping became routine. Risk became measurable. Delivery stabilized at scale.

2. Incremental architecture without rewrites

Context

Structural limitations reduced iteration speed and increased coupling.

Constraint

A rewrite was not viable.

Action

Defined an incremental evolution path with explicit boundaries aligned to roadmap milestones.

Outcome

Architecture improved steadily while maintaining business continuity.

3. Performance as an organizational discipline

Context

Performance degradation accumulated as features expanded.

Constraint

Feature velocity had to remain high.

Action

Introduced performance budgets, profiling standards and monitoring integrated into delivery workflows.

Outcome

Performance discussions shifted from opinion to data. Regressions surfaced early. In one initiative, widget LCP was reduced from 8s to 4s within 6 months through async re-architecture and direct vendor collaboration.

4. Secure embeddable flows in untrusted environments

Context

Widgets operated inside partner-controlled environments.

Constraint

Host environments could not be trusted.

Action

Implemented isolation boundaries, explicit messaging contracts and backend-aligned recovery mechanisms.

Outcome

Integration reliability improved. Security posture strengthened. Support load decreased. The widget scaled to serve multiple industry partners including hardware wallet and exchange integrations across 250+ countries.

Background

I evolved from hands-on frontend engineering into leading and scaling frontend organizations within fintech and crypto environments. Today, my focus is building engineering systems, operating models and teams that deliver sustainable outcomes at scale.

B2C and B2B experience

I have built consumer-facing products as well as partner and internal systems. Context changes constraints. Engineering discipline remains constant.

B2C

  • Conversion-critical journeys shaped by fraud controls and trust mechanisms.
  • Speed as an acquisition driver. Stability as a retention driver.
  • Explicit error handling and recovery paths in user-critical flows.

B2B

  • Contract stability through disciplined versioning.
  • Operational clarity via permissions, auditability and predictable UI behavior.
  • Integrations optimized for correctness and controlled rollouts.

Widgets and embeddable flows

Embeddable on-ramp and off-ramp systems require coordination across frontend, backend and partner environments. Integration quality directly impacts trust.

Trusted by Ledger, TREZOR, Edge and Phemex.

Architecture and contracts

  • Versioned integration contracts with controlled evolution.
  • Explicit state modeling supporting retries and recovery.
  • Observability focused on funnel visibility and actionable errors.
  • Optimized asset delivery for fast startup and cache efficiency.

Delivery responsibilities

  • Integration via callbacks, redirects and webhooks.
  • Frontend and API components evolving in alignment.
  • Explicit handling of partial failures with bounded retries.
  • Operator tooling designed for fast diagnosis and resolution.

Speaking

Paybis Workshop – Reality Layer: Paybis On-Ramp Integration at EthCC Cannes 2025 (INPUT Global × Sumsub).

Watch the session

Frontend security

Security is treated as a systemic property. The objective is measurable risk reduction without compromising delivery. I have owned end-to-end threat modelling exercises — identifying 20+ attack vectors across a live platform, proposing concrete mitigations for each, and driving implementation across code and infrastructure.

Security mechanisms

  • Secure-by-default rendering practices reducing XSS exposure.
  • CSRF-aware flows with explicit session boundaries.
  • Cryptographic signature verification for sensitive requests.
  • Dependency risk management and supply chain hygiene.
  • Strict secrets handling at build and runtime.

Infrastructure and decision logic

  • Domain allowlists enforced at the edge.
  • Request validation before business logic execution.
  • Graduated response strategies under uncertainty.
  • Decision-making supported by metrics and audit logs.

Security posture

Security controls are most effective when embedded in architecture and delivery standards, not added after incidents.

Toolbox

I operate comfortably within the Vue and Nuxt ecosystem and maintain strong backend context in PHP and Symfony. My primary value lies in strategy, system design and organizational leadership rather than specific frameworks.

AI-Augmented Engineering

Claude Code. Skill design. Agentic workflows. The thesis: predictable AI output is an architecture problem, not a prompting trick — design responsibility boundaries, not rules.

Frontend

TypeScript. Vue. Nuxt. SPA, SSR and SSG architectures. Performance engineering.

Backend context

PHP. Symfony. API design. Security constraints. Integration patterns.

Engineering systems

CI/CD design. GitLab Pipelines. GitHub Actions. Trunk-based development. Quality gates. Monitoring. Organizational practices.