Shared foundations for a consumer fintech.

Engineering across consumer web, internal customer operations, and marketing delivery at a US credit-card fintech. I built architecture that other engineers could extend and shipped features on top of it.

RESPONSIBILITY: Senior Software Engineer
CONTEXT: United States · Remote · Aug 2025–Aug 2026

Next.jsReactTypeScriptFlutter WebRiverpodAWS AmplifyGitHub Actions

01 / CONTEXT

Three applications with different responsibilities.

MadeCard is a consumer credit-card fintech focused on homeowners. My work spanned consumer web, the internal admin portal, and the marketing site.

The challenge was delivery and maintainability: financial workflows needed to ship while the team needed shared foundations for continued development.

02 / ARCHITECTURE

A feature-module foundation for consumer web.

I designed the feature-module architecture used across the Next.js, React, and TypeScript consumer application. Work included passkey authentication, OTP MFA, payments and autopay, rewards, mortgage redemption, and transaction disputes.

This was client application architecture and integration work, giving product features a consistent structure for the team to build on.

ARCHITECTURE

Engineering scope across the product

CONSUMER
- Next.js / ReactAuthentication · payments · rewards · disputes
OPERATIONS
- Flutter WebCustomer-360 admin foundation
MARKETING
- Next.js / AWS AmplifySEO routes · CI page crawls · branch previews

Parallel application surfaces, not a backend dependency diagram.

03 / OPERATIONS

Internal tools and a safer publishing path.

I built the Customer-360 admin foundation in Flutter Web. Subsequent team work extended it for customer operations.

For marketing, I migrated the live site from Webflow to Next.js. An SEO route registry, CI page crawling, and AWS Amplify branch previews supported the new publishing workflow.

04 / TOOLING

Make routine edits easier for the whole team.

I shipped a React inspection overlay that identifies the component under the cursor and generates an LLM edit prompt. It gave the team a shorter path from identifying a change to expressing it in implementation terms.

Across the applications, my contribution combined shipped features and reusable foundations that supported the team’s continued delivery.

Discuss the engineering.

Interested in the architecture, implementation decisions, or working together?

Get in touch