What I'm bringing with me switching to front-end dev

For the last few years, I've been working in student systems at UNSW — leading a team, rolling out a major new product, and solving all kinds of system-related challenges along the way. It's been a rewarding role, but now that the project is nearly complete and my time there is winding down, I'm finally making the move I've been preparing for: transitioning into front-end development full-time.

While I've been learning web development in the background — building projects in React, refining my JavaScript, diving into HTML and CSS — I've also been picking up skills in my day job that I know I'll carry into this next chapter. Here are a few of the things I'm bringing with me:

1. A problem-solving mindset
Much of my current role has involved identifying problems, untangling processes, and figuring out where things are going wrong. Sometimes that's technical, sometimes it's data-related, and sometimes it's just about improving how people interact with systems.

That same mindset is at the heart of front-end development: understanding what the user needs, working through edge cases, and building something that's both functional and clear.

2. Working with (and around) constraints
Anyone who's worked in large organisations knows there are always limits — whether it's legacy systems, rigid data structures, or vendor platforms that don't always behave as you'd like. I've learned to work within those boundaries, finding practical solutions that still deliver value.

From what I've already seen in front-end projects, that experience translates well — especially when working with design systems, third-party APIs, or complex UI requirements.

3. Translating between people and systems
As a senior business consultant, I've often been the person connecting the dots between different groups: analysts, product owners, developers, end users. I've written Jira tickets, run demos, gathered feedback, and translated business needs into actionable features.

Front-end developers sit at that same intersection — bridging user needs and technical implementation. I'm comfortable in that space and genuinely enjoy working across disciplines to bring ideas to life.

4. A focus on maintainability and documentation
I've seen how messy things can get when systems aren't documented or when one-off fixes become permanent without proper context. I've always made a point of leaving behind clear notes, structured documentation, and code that others can follow.

Now, as I write more front-end code, that mindset sticks — writing clean, reusable components and documenting my thinking along the way.

5. Comfort with ambiguity
Project timelines shift. Requirements change. Documentation is sometimes out of date (or missing altogether). That's been a consistent reality in my current role, and I've learned to navigate it — asking questions, tracking down the information I need, and figuring things out as I go.

That comfort with ambiguity will be just as useful in a dev team — especially when exploring unfamiliar codebases or adapting to evolving features.

Looking ahead
With the new product fully rolled out, and the project winding down, the timing finally feels right. I've been building up my front-end skills, working on projects I'm proud of, and I'm excited to shift gears into a role where I can do that every day.

The transition is already underway — and I'm looking forward to joining a team where I can grow, contribute, and keep learning as a developer.