Finance-trained and two years into the workforce — in payroll, not my target field, but I treated it the same way I approach a financial model. Understand the system, find where it loses time or accuracy, and build something that actually fixes it. That thinking doesn't turn off depending on the job title.
I try to design things for the person who will use them, not the person who built them. That means a colleague can pick up a tool without needing me to explain it, a workflow can be handed off cleanly, and nothing I build introduces a risk the business didn't ask for. Security and liability aren't afterthoughts — they're part of the design.
I also stay in it past the build. When I introduce something new to a team — a workflow, a tool, a process — I make sure the people around me understand it well enough to use it, question it, and eventually improve on it. A tool nobody understands has a ceiling. A tool the team understands has a future.
I'm actively looking for a finance or data role where I can contribute from day one and keep growing. The projects on this site are the most honest version of what that looks like in practice.