Software Engineer | IDIQ.

Software Engineer at IDIQ, a financial wellness company offering identity theft protection and credit monitoring through its IdentityIQ platform, serving 4M+ members. The work focused on the signup experience: migrating it from a legacy stack to React and Next.js, validating changes with A/B tests, and staying aligned through weekly calls with the designer and product owner.

Live artifacts

IDIQ → Company site

Scope

Signup flow migration, responsive UI, conversion testing

Stack

React, Next.js, TypeScript, Google Optimize

Role

Software Engineer

Outcome

Modern signup experience serving 4M+ members

Context

IDIQ's signup flow was a critical conversion surface for a platform used by millions of members. It ran on a legacy C#/.NET stack that made iteration slow and limited how responsive the UI could be across devices.

I joined as a Software Engineer on a small product team: one designer, one product owner, and me, helping move that experience to React and Next.js. The goal was not just a tech refresh, but faster design changes, better performance, and a foundation the three of us could iterate on together.

Why this mattered

Signup is where members first trust the product. A slow, brittle flow costs conversions and makes it harder to test improvements. Modernizing the stack was as much about velocity and measurement as it was about UI polish.

What I built

The work spanned migration, experimentation, and the collaboration layer between design and engineering on a high-stakes user flow.

Signup migration

Migrated the signup experience from a legacy C#/.NET stack to React and Next.js, replacing a monolithic flow with responsive, component-driven UI that improved performance and made design iteration faster.

Conversion testing

Led A/B testing with Google Optimize to validate UI changes against real user behavior, using data from live traffic to improve signup conversion rather than guessing from mockups alone.

Design collaboration

Joined weekly calls with the designer and product owner to refine user flows, resolve edge cases, and keep handoffs tight.

Component-driven UI

Built reusable React components for the signup surface so new variations, experiments, and responsive breakpoints could ship without rewriting the flow each time.

Outcome

Delivered a responsive, component-driven signup experience on React and Next.js, replacing the legacy .NET implementation. A/B tests through Google Optimize gave the team a repeatable way to validate UI changes against real behavior. Weekly calls with the designer and product owner kept the flow aligned as it shipped.

What I took forward

This role sharpened how I think about conversion surfaces: treat signup as a system you can measure and iterate on, not a one-time build. That mindset carried into later work on design systems and product UI.