About Malanga Mposha

Finance professional and systems builder. I help people build freedom with better systems and AI, and write these guides from my own work.

I spent close to ten years in finance, in financial services. Now I build systems that give people back control of their work, their income and their time.

Finance is where I learned how. AI is the tool I use now. Freedom is the reason.

If you just finished one of my articles, this page is the proof behind it. Where I come from, what I've built, and how the numbers here get made.

Where it started

I grew up in Zambia.

Then I moved to Canada, and the small stuff caught me off guard. I opened a bank account. I got the internet hooked up. Both just worked, with far less friction than I was used to.

For me it was the first time "working as intended" was something I could point at.

The habit of building toward that feeling started earlier, before I had a name for it.

In high school I had to learn biology, a subject I had no interest in. So I built a way to learn it anyway: flashcards, repetition, practice. I got the second-highest mark in my grade. The system beat the interest.

In university I got into options trading and watched tastytrade all day. It was the first time I learned something because I wanted to be good at it, not to pass an exam. The approach was simple. Go through the data, know your expected rate of profit, repeat it enough times, and make it boring.

An options table is chaos the first time you look at it. After enough staring, the structure showed. I could read the liquidity in a few seconds and know right away whether a spread was worth attempting.

That is the one move I've used on everything since. When something looks chaotic, I look for the framework underneath it. If nobody laid one out, I reverse-engineer one. I get to a baseline I'm comfortable working from, then I iterate. When new learning breaks part of the old system, I tear that part down and rebuild it, no sentiment.

It shows up when I open a new model or a new deck at work: find the structure first, then improve it. It shows up in my kitchen. Empty the dishwasher first. Cut all the veg first. Then cook.

The sentence I use for everything I do is this one: organize chaos into order, so that things and people can function the way they were actually intended.

The "people" part is on purpose.

A system that runs clean is nice. A system that lets a good person stop firefighting and get back to the work they were hired for is the point.

The finance years

I studied finance and came in through a rotation program. Then the usual ladder: analyst, senior analyst, manager, then senior manager in business partnering.

If you only read the titles, I look like a cookie-cutter FP&A guy.

The work under them tells a different story.

In my first rotation, the thing that excited me was a combined KPI dashboard for two organizations that were merging.

In the next one, the company moved from Outlook to Google, and I trained more than 500 people through the switch. I didn't just show them where the buttons were. I learned how each team actually worked, rebuilt that in the new tools, and taught myself Google Apps Script to automate what I could. That was my first real lesson in change management.

After that I improved existing models so my boss could make decisions faster.

As an analyst, the first thing I did was move our Excel reporting into Tableau.

Then the work got bigger.

We acquired a small company where the executive assistant was pretty much running QuickBooks. She was about to retire. (No pressure.) I led the finance side of bringing it in: accounting, billing, banking, invoices, the sales commission plan and the earn-out math. The systems were live in about six months. The business came in at break-even and turned a profit on the efficiencies alone. By the end it was one line item on our books.

That's the most common finance problem I know.

The company grows. The finance stays where it was.

I was also the only finance person on our side of a joint venture that launched a new financial data product. I built the pricing model with our partner, then set up and ran the money side from scratch: billing, collections, settlements between legal entities, payments to the partner and the accounting memos behind all of it. I walked the auditors through every piece. It grew to hundreds of clients.

One of my favorite pieces of work was a no. A team wanted to move a subscription product from variable to fixed pricing to make revenue steadier. I modeled how many new subscribers it would take to make up what the fixed price would eat. Then I pointed out the market was already saturated. The new customers needed to close that gap didn't exist, so the change didn't happen.

I designed sales commission plans with our VP of Sales, built to reward the deals that moved the company forward, not just the easy ones.

In my last seat I helped consolidate the company's budget and forecast, figures in the billions, before they went to the CFO. I was also a gatekeeper on project spending. Initiatives adding up to around $100 million came through me for approval.

On paper, my people leadership was thin: two or three analysts, for about a year. The bigger part never made the resume. In that last seat I owned one process end to end, and more than 30 people worked inside it. I set the standard, trained and coached the people running it, and held the line. Leadership without the title. It took someone asking the right question before I saw it as leadership at all.

That is business partnering in one line, as I'd say it: I'm good in the technical conversation, then I turn around and teach it to the business folks.

The last big thing I built in that world was an AI agent that sped up our modeling and got presentation slides out much faster. It got to the point where I didn't open the models anymore. I just talked to the agent.

Every seat, I ended up building a system that made someone's day easier. That's the part of the job I like.

Along the way I passed CFA Level I and did a master's in blockchain and digital currency.

Why freedom

Some people build a business for income. I build to become free. And the thing you build shouldn't become your next prison. It should give you the option to walk away.

Before Arca I tried a few businesses.

A Shopify store that depended on marketing I didn't control. Affiliate sites that a Google algorithm change could flatten overnight. An Amazon business, the closest fit for me because it was pure process and numbers, until a supplier let me down and the platform banned the account. Crypto, which made sense long term but needed capital I didn't have.

Every one of them died on something I didn't own.

Somebody else could make a decision, and it was gone.

They taught me a second lesson too.

With the store and the Amazon business, I went straight to the part I love: the fulfilment machinery. I went deep on the ad system backend the same way, the ad groups, the splitting, the scaling. I understood the machine. I was bad at the creative, and I never owned the product piece. The sourcing, the one thing the whole business rested on, I handed to someone else, and it failed.

You can't optimize a dropshipping system when your sales are at zero. You have to fix your market. The system only started to matter once we were already a little bit successful.

Systems don't matter at zero.

So what does freedom actually mean to me? Freedom is not freedom from work or responsibility. It is freedom of choice. Nobody choosing for me, and nobody forcing me to choose.

The test is simple. If someone tells me to stop doing something I believe in, can I say "I'll put in my two weeks, let me know your thoughts" and mean it?

I'd call it self-sufficiency rather than self-reliance. Self-reliance sounds like you can't work with others. Self-sufficiency means I could do it alone if I had to, without depending on someone else's feelings or decisions. Self-sufficiency gives you the choice. The choice lets you be true to yourself.

And I build that self-sufficiency so the people closest to me can depend on me. I do the hard work because I know not everyone can, and I want to be the dependable one at home.

I'm married, and we have a baby on the way. That is not abstract right now.

What I build

I started Arca in January 2026. It is the first thing I've built where I own the whole stack: the process, the systems and the output.

I have one rule about the order: "fix your operations first before you apply ai."

AI does whatever your process tells it to, including the broken parts.

I've built systems for my own work that take requests in, hand the research and the busywork to specialist tools, and check every result before anything goes out. A person approves every outbound action.

I built the controls the way a finance person would, because that's what I am. My own words for it are "designing the machine that manages itself."

I once scrapped a whole nine-agent setup because it wasn't getting me to the goal. Same instinct as the options table. When a system stops serving the goal, the system goes.

The goal wins over the sunk cost.

The AI Job Search Agent is one of the systems I've built. It's the one this site connects to, because a job search is where a lot of people feel least in control.

The job search is one of the more broken systems I've been through, so I treated it like one.

Most advice makes you pick. A few roles, done with care, or hundreds from a template.

My view is that "you don't have to pick between quality and volume: with ai you can actually do both." I call it Targeted Volume.

So I built a system for my own search. It read finance postings, scored every role against what I actually wanted and could prove, and cut the ones that didn't fit before I spent a minute on them.

I still went after FP&A roles. But I leaned toward the ones that asked for the building part, because that's the work I want more of.

It scored more than 1,600 roles. 931 were cut at the score. I sent more than 130 applications, and none went out without my yes.

My search ended in a signed offer for a six-figure finance role in financial services.

I've managed people, and I've been the candidate. I've lost a case round by getting to the answer too fast. Both sides show up in what I write.

Where the numbers come from

The pay figures on this site come from ranges employers wrote in their own job postings, counted. They are not survey averages.

For the FP&A salary guide, my tool read 7,721 unique US postings and kept the 1,262 with a pay range the employer wrote. Reposts, estimated salaries and off-title roles went out.

Where the numbers come from lists every rule, so you can argue with the method instead of the result.

Numbers from anywhere else, like the Bureau of Labor Statistics, link to their source where the claim is made.

How this site is written

This is my second try at a site like this.

The first was while I was studying affiliate marketing. I followed an influencer and did the mechanical things: set up WordPress, set up the blog and the newsletter. I wanted a sidebar that scrolled with the page, which was beyond me, so I paid someone to build it. I spent about $200 in total and published zero articles. Every change needed someone else's hands, and I quit.

This time I can change anything myself, and the site passed 30 articles within about a week.

What hasn't changed is the risk. Ask an AI to write about finance careers with nothing behind it and you get the average of the average. A summary of a summary.

So every article starts from my own work. Before I write, I go back through what I've said and done on that topic: voice notes, transcribed meetings, the actual work. The hardest part is checking a finished page for what I don't know I'm missing.

I also write against a weakness I know I have. When I pick up a new topic I assume I know nothing, read a lot of short opinions, keep the few that fit how I work, then go deep and learn it fast. Then I forget the rest of the world hasn't caught up. Just because I've got the concept doesn't mean the reader has. So the rule here is to write for the person three months behind me.

Each story is told in full on one page only. Other pages take a different angle or link back to it. That's why the case round above is one line here and a full section on the FP&A interview questions page.

Each article also names 3 to 5 outside sources you can check for yourself. How we write has the rest of the rules.

The stories are mine. I name the industry I worked in, financial services, and leave the companies and the people in them unnamed.

If nobody read any of this, I'd still be writing about how systems work and how to build them better. Finance is the one I went deepest on. AI is the lens, not the subject.

If you want to follow what I'm building, I post on LinkedIn, X and YouTube.