Thinking beyond the task
Nguyễn Ngọc Châu on how broader responsibility shaped the way he builds technology and supports his team
Nguyễn Ngọc Châu’s interest in mathematics and computers led him into software engineering, where he gradually found his focus in front-end development.
After joining Netcompany four years ago, his role began to change. He was expected not only to complete tasks but also to understand the wider challenge, contribute to decisions, and take responsibility for the solution.
Today, that mindset shapes his work as Lead Software Engineer on the PULSE platform, both in the technology he builds and the way he supports his team.
From completing tasks to taking ownership
In Châu’s previous roles, the requirements and expected solutions were usually divided clearly.
At Netcompany, he encountered a different way of working.
Rather than focusing only on an assigned technical task, he was expected to understand a bigger picture, discuss possible approaches with experienced colleagues and make decisions about how the solution should be built.
»At first, that level of ownership felt stressful, but it became a turning point in my development,« he says.
Taking on broader responsibility changed more than his technical skills. Châu became more confident communicating ideas, challenging assumptions and considering how one decision could affect other parts of a project.
Over time, his focus shifted. Instead of asking only how to complete a task, he began asking about the broader solution.
That perspective has become central to the way he works today.
»At first, that level of ownership felt stressful, but it became a turning point in my development,« he says.
Building PULSE for the long term
As Lead Software Engineer, Châu helps maintain the stability and continued development of PULSE’s front end.
The technical challenge is that PULSE is not built for a single client or a narrowly defined use case. Its features need to work across different implementations while remaining flexible enough to support individual business needs.
Châu explains it through a practical comparison.
»Imagine that my team and I are building an assembly kit with different pieces. Clients can then use the kit and assemble the pieces according to their needs. Our job is to create something that works for everyone while still leaving room for customisation.«
That means the team cannot judge a solution only by whether it solves the immediate request. A choice that works well for one implementation may create limitations elsewhere in the platform.
»My focus is on building solutions that strengthen the platform as a whole and support its future development.«
For Châu, strong technical decisions come from looking beyond what works now and considering what the platform will need later. It is the same broader perspective he first had to learn when taking on more ownership, now applied at platform scale.
»My focus is on building solutions that strengthen the platform as a whole and support its future development.«
Growing capability, not dependency
Châu uses the same principle when supporting his team.
On a complex platform like PULSE, he believes team members need to understand more than the piece of code they are working on. »It’s important that everyone understands not only what needs to be done, but also why it matters and how the different parts connect,« he explains.
Rather than keeping knowledge or difficult tasks concentrated within himself, Châu tries to distribute responsibility.
»I don’t want to become a bottleneck,« he says. »I try to create space for team members to take on tasks at different levels of complexity. Meanwhile, I focus on the most difficult problems, strengthen the foundations of the codebase and remain available when someone needs guidance.«
The aim is not simply to help someone complete the task in front of them. It is to give them enough context and responsibility to move forward independently.
Shaping what comes next
Châu joined PULSE in its early development and helped lay the foundations of its codebase. Seeing the platform grow from those first stages remains one of the achievements he is most proud of.
Today, his role is to continue helping both the technology and the team develop further. On the platform, that means creating solutions that can support future needs. In the team, it means giving colleagues the knowledge and responsibility to tackle increasingly complex challenges.
For Châu, both come down to the same principle: creating strong foundations that others can build on.
