From paperwork to a connected workflow.

The challenge

Business onboarding touches more than a registration form. Documents need to be collected, information verified, applications reviewed, and agreements signed. Each step brings its own systems and responsibilities.

At actyv.ai, I worked on onboarding and administration tools that connected these activities in full-stack web applications.

What I owned

My contributions included the onboarding and admin portal, integrations with document parsers, KYC services and banking APIs, and an e-signature service. I also helped implement shared sign-on and role-based user systems across applications.

As I progressed from intern to SDE 2 and team lead, my work expanded to backend architecture and leading a six-person engineering team. The products were team efforts; these are the areas I contributed to.

Engineering decisions

Connect the steps in the journey

Collecting information is only one part of onboarding. Connecting the portal to verification and banking services made those services part of the broader application workflow.

Support sequential signatures

The e-signature integration supported documents moving through a sequence of signers. This addressed a different need from collecting a single signature: coordinating an agreement that multiple people must complete.

Share identity across products

Contributing to single sign-on and role-based access meant working on user journeys that crossed application boundaries. Identity became a shared product concern rather than a separate sign-in experience for every application.

The result

The onboarding product connected document collection, integrations, administrative review, and digital signatures. These capabilities supported a paperless workflow and gave users a web-based path through the process.

This work shaped how I think about full-stack engineering: the integration points matter as much as the individual screens.

About the preview

The screenshot is the onboarding entry screen already included in this portfolio. The workflow diagram is an illustration of the onboarding stages, not an internal system specification.