Skip to content
Moberg

A day in the life of Moberg's frontend team lead

From Senior React Developer to Frontend Team Lead — Silvio on the move from individual contribution to leading and growing a team.

Written by Karla Tomšić April 2024

Silvio transitioned from Senior React Developer to Frontend Team Lead, discovering his passion for mentoring and knowledge-sharing along the way. He's been with Moberg for nearly four years — and what started as a senior individual contributor role has grown into something quite different.

From senior developer to team lead

Silvio joined Moberg as a Senior React Developer. His first major project was Brandr — built nearly from scratch — followed by leading the frontend for Straumur, a large-scale initiative involving three separate frontend applications and substantial backend infrastructure.

From there, his professional development progressed naturally into mentorship and leadership, including work with our banking partner Kvika. The shift wasn't a sudden pivot — it grew out of the work itself.

A typical day

The day starts with a quick check on Microsoft Teams for anything urgent, then a look at the calendar and HR software to see who's where. From there, the Jira board sets the pace.

  • Check Microsoft Teams for urgent messages
  • Review calendar and HR software for team status
  • Process Jira board tasks
  • Daily standup, 10–11 a.m. — progress updates and where the team needs support
  • Balance the rest of the day between coding and leadership duties

The hardest part of the role isn't any single task — it's the balance. Coding still matters, but so does carving out time for the team.

Leadership philosophy

“Ask them. Ask what they want, what they're struggling with, and what their professional and personal goals are.”

For Silvio, leadership starts with listening. Building trust and transparency with both the team and the client is non-negotiable. Regular one-on-ones, leading by example with patience and a bit of humour, and creating a psychologically safe environment where people can speak up without fear — those are the daily practices that hold everything else together.

How Moberg supports the role

The company has invested in Silvio's growth in concrete ways. Moberg funded his final two years of graduate studies — a prerequisite for entering a therapy program he was passionate about. The monthly Leadership Academy keeps the conversation going on communication styles, feedback, and conflict resolution.

Leadership at Moberg is approachable and supportive — and that's not a slogan. It's part of how decisions are made and how people are treated, day after day.

The most rewarding part

Delivering high-impact projects while watching the team grow into more independent, confident engineers. The combination of technical challenge and people development is what makes the role meaningful — and what keeps the work interesting after four years.

Advice for aspiring leaders

“You won't have all the answers — listen, ask questions, be patient, and stay consistent.”

Show vulnerability. Show that you genuinely care. The rest follows from there.

What stands out about Moberg

Two things, really. The standard for code quality is high — the developers around you are professional and competent, and that pulls everyone up. And the culture is warm and positive, with genuine emphasis on well-being and personal growth. Both matter. Both stay consistent.

MTK: AI-driven development, held accountable

Blog

MTK: AI-driven development, held accountable

AI now writes a serious share of our code. MTK is how we make sure that it never lowers the bar — spec first, tests second, AI-generated code third, every change reviewed and traceable.

Microsoft Fabric vs Databricks: a high-level overview

Blog

Microsoft Fabric vs Databricks: a high-level overview

Two strong answers to the same modernization question — different architecture philosophy, operating model and audience. A neutral comparison across the dimensions that actually decide it.

How we handle rapid changes in development caused by AI

Blog

How we handle rapid changes in development caused by AI

The pace of change in AI is genuinely fast. Here's how we keep our engineering grounded — and quietly improve faster than the noise around us.

Ready to write your story?

Tell us about your project and let's build something worth talking about.

Start a conversation →