Ponture was a compact but valuable role because it combined implementation speed with trust-sensitive workflows. Identity verification, portal usability, and documentation quality all had a direct effect on how smooth the product felt.
I worked on both admin and customer-facing portals, which meant thinking about different user contexts inside the same product. The admin tools needed clarity and control, while the customer experience needed to feel simple and dependable.
That kind of split is useful because it forces you to think in systems rather than isolated screens. A decision in one surface often changes the demands on another.
Integrating BankID raised the importance of accuracy and flow design. When identity steps are part of the experience, even small mistakes can quickly turn into support costs or lost trust.
The work required careful attention to state handling, user messaging, and edge cases around verification.
Because the team worked across business and engineering roles, good documentation created real leverage. It reduced repeated clarification work and made future changes easier to align.