Dávid Novák
SK
Case 03 of 05

Leading a team of six, and making one checkout feel native in every partner’s brand.

PRODUCT
Embeddable checkout and payments SDK
ROLE
Frontend Lead
YEARS
2024–2025
TEAM
About six engineers, alongside the client’s own
SCOPE
Motion system, white-label theming, team leadership
~6engineers in the frontend-heavy team I led for about a year.
7+white-label partner themes on a shared theme system, light and dark.
Extendedby the client, several times.
CONTEXT

An embeddable checkout SDK. Partner apps drop it in so their users can fund an account from a wallet, an exchange account or a card, each in the partner’s own brand.

MY ROLE

Frontend Lead of a frontend-heavy team of about six, working alongside the client’s engineers, until a planned hand-over to the next lead.

THE CHALLENGE

A checkout that has to feel native inside many different brands, and a large team delivering into fragile legacy code without regressions.

What I didFour edits to the plan
AProposed a motion system
THE OPPORTUNITY

Animations across the checkout, without a shared system.

WHAT I BUILT

Inserted: One motion system: shared timing and easing tokens, animated amounts and fees, status icons, a dialog that resizes smoothly, and step transitions, all in Storybook.

RESULT

Used across the entire checkout, and the client was very happy with it.

BMade theming instant
THE OLD WAY

Struck out: Writing a new theme just to check whether something fits.

MY EDIT

Inserted: A reworked showcase where the team previews and tweaks themes in real time.

RESULT

Used daily by the whole team, across 7+ partner themes.

CSet out the trade-offs
THE BRIEF

Flagged: Embed a third-party verification flow in an iframe.

MY NOTE

Inserted: Before we commit: no callbacks, inconsistent UI, awkward modal sizing and transitions, and security and UX risks.

RESULT

The client kept the iframe, with the costs on the table. I made it as seamless as possible: the dialog animates its width to fit the embedded step.

DCoached, not replaced
THE SITUATION

A team member who had struggled with communication in past reviews.

WHAT I DID

Inserted: A structured improvement plan, framed as an opportunity rather than a last warning.

RESULT

They improved significantly and went on to receive great feedback from the client.

HOW I LED
  • Regular 1:1s
  • Weekly buddy syncs
  • Daily syncs on a critical integration
  • Candid-feedback rounds with the client
  • Clear escalation paths
  • Hand-over sessions

The key objective was integrating a new payment provider into fragile legacy code without regressions, so I put daily alignment in place. I paired a mid-level engineer with a new junior, and gave the mid-level engineer a small initiative of their own to grow their leadership.

OUTCOME

The client extended the engagement several times. The motion system and theming shipped across partner brands, and a teammate I coached went on to earn great client feedback.

“He would always proactively ask whether I was blocked or having problems, and made sure to remind me to raise red flags early. His openness to talk about these issues provided a much-needed sense of security.”
— Engineer on a team David led
NEXT CASE04 Digital collectibles platform