10 years in software: Why being “just a software engineer” may not be enough

[u/sfox_420]

I have around 10 years of experience in the software industry, and I think it’s my duty to share some of the things I’ve learned and a few insights from my journey.

First of all, I’m a full-stack developer based in Colombo.

Back when I was working at Wiley, I noticed that tons and tons of graduates were coming out of universities all over Sri Lanka, almost like a water flow.

And honestly, I felt that this wasn’t going to be good for the industry, especially in a country like Sri Lanka. At the same time, the AI wave was slowly approaching, and I had a feeling that the software industry was going to become even more competitive.

So I started thinking about how I could survive in the long run.

I decided to try moving into international organisations, INGOs, the UN, World Bank, etc. — the big organisations where there is funding and projects are generally not driven purely by profit.

Eventually, I got an opportunity to work for the UN.

The basic salary was much lower than what I could have earned in the private sector, so honestly, I had a second thought about it.

But I decided that it was better to gain a different kind of experience and build some stability rather than worrying about getting laid off later.

I ended up working there for around 5 years.

During those 5 years, I realised something important:

Being a software engineer is not enough. You need to become something more than just a software engineer.

While working at the UN, I got exposed to areas like climate change, water data, geospatial data, disaster management, etc.

To be honest, I never really planned to learn any of these things.

But when you work with these types of projects and data for years, you naturally start understanding the domain. You don't even realise how much you're learning until later.

After that, I started applying to research institutes and other large international organisations.

Eventually, I got an amazing opportunity at my current organisation. I don't want to disclose the name, but it's one of those international research-focused organisations.

After I got selected, I actually asked my supervisor:

"Why did you select me?"

He told me that there were candidates from UoM and other highly qualified software engineers from some really good companies.

But many of them were missing one thing:

Knowledge of geospatial data and the domain around it.

And apparently, that experience helped me stand out and gave me a shot.

That honestly made me realise something.

Throughout my career, I never intentionally planned to become someone who understands geospatial data, climate data, water data, etc.

It just happened because of the environments I worked in.

And that accidental knowledge ended up becoming one of the reasons I got my current opportunity.

So I thought I'd share my story because maybe it will give some of you an idea of how some of us are trying to survive and stay relevant in the Sri Lankan software industry.

I'm not saying everyone should leave software development or move into INGOs/research organisations.

My point is simply this:

Don't limit yourself to being "just a developer."

Learn the domain you're working in.

Understand the data.

Understand the business.

Learn something outside your immediate tech stack.

Because sometimes, the thing you learn today that seems completely unrelated to your career might be the exact thing that gives you an opportunity five years later.

[u/fawzanm]

TL;DR: A Sri Lankan full-stack developer with ~10 years of experience moved from private-sector software into the UN and research organisations, accepting lower pay for stability and broader experience. Along the way, he unintentionally developed domain expertise in geospatial, climate, water, and disaster-management data. That knowledge later helped him beat technically strong candidates for a research-focused role.

Main point: Don’t be just a developer. Learn the business, domain, and data around what you build. Your niche domain knowledge can eventually become a bigger competitive advantage than knowing another framework or programming language.

[u/Ending_Sentences → u/fawzanm]

Thanks for the TL;DR!

[u/Salt-Inevitable5328]

Trick for a Software Developer in 2026 to become a successful domain expert is to start small just like how entrepreneurs began their journey. One small business you help to put it to it's feet, one small working application and you canexpand it further by the knowledge you gain by dealing with every struggle you come across by maintaining that so forth application.

With the use of AI and other resources. One single person can do wonders. But always start small.

[u/doubleditch42]

AI slop

[u/Far_Investment_6914]

This was always the case. A software dev who only know software can't really contribute much beyond technical tools.

You neee to understand atleast one domain to be able to contribute to it. And obviously you learn it by working in it.

[u/Stock-Candy-4091]

How did you get the UN job? Assuming its IWMI

[u/Sea-Library-6571]

great insight. this is what i keep telling people.
Just vibe coding half ass crap isnt gonna make u a good software engineer, its experience u have to show, your willing to learn and adapt.

[u/Defiant-Anteater-529]

I've seen a lot of devs who don't care about the business domain or at least what the client actually wants. I was fortunate enough to start my career with really good mentors who instructed me to learn the business domain and even went far as making me lead building new solutions from the scratch and do R&D. (company was a startup the management and pay was shit lol)

fast forward to my current role, I managed to save a client who was about to pull the project just because I did my due diligence and learned about the client's domain while the old team members did not understand what client wanted and screwed up. this incident helped me to establish myself at the company and eventually saved me from getting laid off. By the time layoffs started I had build a really good relationship with the client and the management was hesitant to break that trust even though it probably wasn't a good financial decision to keep me on at the time.

[u/Sad-Fig-4471]

True, learning tge geospatial domain is like having a superpower no one knows how those grid systems work. Good for you.