RealtyMogul · Engineering case study
One investment, many ways through
Keeping a multi-step investment journey attached to the right investment through account changes, redirects, and partial progress.
An investment application is more than a form. People choose an account, answer qualification questions, arrange funding, sign documents, and sometimes return hours later. I worked across the React flow and Python API to make those transitions more dependable.
The problem
The same person could have more than one investment in progress. A cache or route that only knew the person—not the investment—could show the wrong step or carry the wrong answers forward.
Backend steps also had to accept partial qualification answers without changing the order of the business side effects already relied on by the live system.
What I did
Give each journey an identity
Carried the investment UUID through the flow, including account choices, funding steps, and the return from document signing. Scoped step caches to that same identity.
Route from the current record
Refreshed resolved investment state before choosing the next screen, rather than trusting an old local answer after a redirect or account change.
Keep partial progress valid
Preserved partial qualification posts and API side-effect ordering, then added regression and end-to-end coverage for duplicate investments and step transitions.
What changed
The flow's identity and partial-progress rules are explicit in code and tests. This was team-owned product work; my contribution was hands-on implementation and repair across its UI and API boundaries.