Fewer Seats, Higher Ceilings

In 2022, the group that speaks for the Philippine IT and business process industry told the country to expect 2.5 million jobs by 2028.

This year they revised it. The best case is now 2.14 million. The downside case is 1.85 million, which is lower than the 1.9 million people the sector already employs today. Revenue targets came down too, from 59 billion dollars to 50.5 billion (GMA News).

If you are about to start a data career in the Philippines, that headline reads like a door closing.

Read the sentence underneath it instead. IBPAP president Jack Madrid, explaining the revision: "For years, our industry has measured success by how many people we could employ. The next chapter will increasingly be defined by the value every Digital Filipino Worker creates."

That is not a door closing. That is a door changing shape.

Two numbers that look like they disagree

While the Philippine headcount forecast came down, the global picture for data work went the other way. The World Economic Forum's Future of Jobs Report 2025 puts big data specialists as the fastest growing role on the planet, up 110 percent by 2030, with AI and machine learning specialists at 85 percent and data analysts and scientists at 41 percent (World Economic Forum).

The same report expects AI and information processing to create around 11 million jobs and displace around 9 million.

So which is it. Fewer seats, or more seats.

Both, and they are not the same seats. The roles being counted out are the ones where a person is a pair of hands moving data from one place to another. The roles being counted in are the ones where a person decides what the data means. The Philippine number and the global number are describing the same shift from two different ends.

What this looks like from inside a plant

I work in manufacturing. My days are data analytics and data governance, which is a formal way of saying I spend a lot of time on the question of whose number is right.

Here is the thing nobody tells you before you start: the hard part is almost never the query.

The hard part is that finance and operations both have a number for the same month, the two numbers do not match, and both teams are certain. The hard part is that a report has been quietly wrong for five weeks and the person who noticed is not sure it is their place to say so. The hard part is being handed a request that never says what decision it feeds, and having the nerve to ask before you build anything.

None of that is Excel. All of it is the job.

I have watched people with better technical skills than mine stall, because they treated analytics as something you do to a spreadsheet rather than something you do for a person who has to decide on Monday. I have also watched people with ordinary tooling move fast, because they always knew who was reading and why.

The roadmap, honestly

There is no single ladder in data work. There are a few, they split earlier than most people expect, and which one suits you has more to do with temperament than with talent.

1. Analytics

You start as a data analyst, though here the same job is often posted as MIS analyst, reporting analyst or operations analyst. You answer business questions with SQL, spreadsheets and a dashboard, and before long you own a number that people argue about in meetings.

From there it goes senior analyst, then analytics lead, where the job stops being "produce this report" and becomes "decide what we measure, and defend it".

This is the widest door, and the one most people should walk through first.

2. Business intelligence

If you would rather build the thing everyone else reads from, this is your route: BI developer, then senior BI developer, then BI lead. Power BI and Tableau are the tools, but the actual skill is modelling, making the definitions hold so finance and operations finally see the same number instead of arguing about two.

Be honest with yourself about one thing. Plenty of BI developer postings here ask for two or three years. It is a real entry point, but it is often the second job rather than the first.

3. AI and automation

This is the newest route, and the one the IBPAP revision is pointing straight at. You start as an automation specialist, putting AI and automation into the workflows a team runs every day, then measuring honestly whether they helped. It moves toward business process analyst, then continuous improvement lead.

In a country whose largest employers are BPO and manufacturing, the person who can remove a week of manual work every month is not a nice to have. Continuous improvement was already a career here. AI just made the path into it much shorter.

4. Independent

Data virtual assistant, then freelance analyst, then consultant. You take reporting and clean up work off a small business owner's desk, usually for clients abroad, and over time you sell judgment rather than hours.

This route rewards a portfolio and a public presence more than any other, and it is the one where being based in the Philippines is an advantage rather than a constraint.

What actually gets you the first one

Some patterns are boringly consistent, whichever route you pick.

• A finished project beats a finished course. Not a tutorial you followed along with. Something with a messy dataset, a decision at the end, and a sentence about what changed because of it.
• You have to be able to say why, out loud. Most candidates can produce a chart. Far fewer can explain why they chose that chart, what they checked before trusting the number, and what they would do if the data disagreed with them.
• SQL is the floor, not the ceiling. Joins, grouping, and knowing why an inner join quietly lost you eight thousand rows. That last one comes up in interviews more than you would think.
• AI fluency is assumed now. Not "I use ChatGPT". Knowing where it speeds you up, where it confidently invents things, and what you check before shipping anything it touched.
• Own one number end to end. Even a small one, even for a family business. Being the person people come to when a figure looks wrong is what the job is actually made of.

Where training helps, and where it does not

I should be straight about my position, because I teach at Millennial Business Academy and you should weigh what I say accordingly.

Training does not get you hired. Nothing does, on its own. What a good program does is compress the part where you are on your own, guessing which of forty tutorials matters, building things nobody ever looks at, and finding out two years later that you learned the tool but not the judgment.

That is what the bootcamp is built around: Excel, SQL, Power BI and Tableau with AI woven through rather than bolted on, and a portfolio you finish with rather than one you promise yourself you will build later. Everyone finishes with the same certificate and the same body of work, and where they go next depends on which part of it they enjoyed most.

If you would rather try the free things first, please do. The free resources include practice projects built on genuinely messy datasets, a client simulator, a data cleaning lab, and a timed mock interview for analyst and BI roles that will tell you quickly where you actually stand. They cost nothing, and they are the honest version of a placement test.

The uncomfortable, useful part

Go back to that revised forecast, because there is a reading of it that helps you.

An industry that expects to grow revenue while hiring fewer people than it planned is an industry that intends to get more out of each person. That is bad news if your plan was to be a pair of hands. It is very good news if your plan was to be the person who decides what the hands should do.

The seats are getting fewer and better at the same time. Which of those you feel depends almost entirely on what you spend the next year building.

Start with one messy dataset and one real question. That is genuinely how it begins.