SolCard · Design Engineer
At SolCard I worked on the two surfaces that matter most: the website that brings people in, and the dashboard they live in afterwards. Both were being built new, which is the best possible time to care about quality, because nothing has hardened yet.
I helped develop the new website. For a product like this, the site has one job: make the product understandable and credible in the first few seconds. That comes down to type, spacing, hierarchy, and restraint more than it comes down to effects.
So the work was as much editing as building. Fewer competing elements. Clearer sections. Details that hold up when you look closely, because people judge financial products by exactly that kind of closeness.
The dashboard was the larger piece. I helped build it while shaping how it was structured: what the recurring layouts are, how screens are organized, which patterns repeat and which ones shouldn't exist twice.
Structure is the part of a dashboard users never name but always feel. When navigation, spacing, and components follow the same logic everywhere, the product feels dependable. That feeling is the actual feature.
Alongside the two builds, part of my role was simply pushing the design quality up across the product: tightening the UI systems, replacing one-off solutions with shared patterns, and cleaning up the details that accumulate when a team is moving fast.
None of this was a single dramatic change. It was a steady raising of the floor, so the worst screen in the product stayed close to the best one.
SolCard ended up with a new website, a new dashboard, and, underneath both, a more coherent set of UI systems to keep building on. The product looks like one team made it on purpose. That was the goal.