en

Leading through example: How senior engineers can transform team culture

In large engineering organizations, challenges don’t always come from the technology itself. Teams can be full of talented developers, yet still struggle to deliver consistently. Silos form, communication drops, and motivation declines — not because of a lack of capability, but because the shared rhythm of the team gets lost.

This is where senior engineers can make a fundamental difference. Not necessarily through formal authority, but through leadership in practice.

When Anffer Castillo joined one of our high-tech clients as a senior software engineer, he stepped into an environment where most teams were performing well — except for one. This particular team was experiencing delivery challenges and had begun working in isolation rather than as a cohesive unit. Discussions were limited, collaboration was minimal, and the team’s confidence had visibly eroded.

The possibility of splitting the team had already been raised. Instead, the organization chose another path: bring in senior guidance to rebuild collaboration and ownership from within.

Rebuilding collaboration from the inside

Anffer’s role was not to “manage” the team, but to influence how it worked — through contribution, communication, and example.

“Everyone was operating in their own silo. The goal wasn’t to change people, but to change how we think and work together.”

His approach was intentionally practical:

  • Take responsibility for complex tasks

  • Share solution reasoning transparently

  • Bring design discussions to the full team

  • Encourage questions, feedback, and shared decision-making

Instead of telling people what to do, he modeled the behaviors of a collaborative engineer, showing that discussions and co-creation lead to better outcomes.

Over time, the team shifted from a set of individual contributors to a group solving problems together.

The turning point

Results appeared in both culture and delivery. The team — which had previously struggled to complete sprint commitments — began to establish consistency.

In one milestone moment, the team successfully delivered three sprints in a row for the first time.

Anffer: “Seeing the team celebrate that moment showed we had turned a corner. It wasn’t just about output. It was a shared win.”

The confidence that had been missing returned. The team regained identity, clarity, and ownership.

Leading without the job title

Anffer’s influence grew naturally. Even without a formal "tech lead" title, he became the person teammates turned to for guidance. “I didn’t push for a leadership role — I just focused on doing the work, sharing knowledge, and involving the team. The transition from engineer to reference point happened on its own.”

For organizations, this distinction matters: Leadership is not a title — it’s a behavior.

Thanks for reading.
Now let's get to know each other.

What we do

WAES supports organizations with various solutions at every stage of their digital transformation.

Discover solutions

Work at WAES

Are you ready to start your relocation to the Netherlands? Have a look at our jobs.

Discover jobs

Related articles

Let's shape our future

Work at WAES

Start a new chapter. Join our team of Modern Day Spartans.

Discover jobs

Work with WAES

Camilo Parra Gonzalez

Camilo Parra Gonzalez

Business Manager