DEV Community

Cover image for What Gemma 4 Doesn't Know About Cameroon — and What That Taught Me About Building AI for the Real World
Tazoh Yanick
Tazoh Yanick

Posted on

What Gemma 4 Doesn't Know About Cameroon — and What That Taught Me About Building AI for the Real World

Gemma 4 Challenge: Write about Gemma 4 Submission

This is a submission for the Gemma 4 Challenge: Write About Gemma 4

When my friend contacted me on WhatsApp with a crying 😢 emoji, my heart skipped. I asked what was wrong, and she sent me her Express Entry refusal letter. IRCC had denied her application — no CNPS affiliation, and the funds in her account were held in a microfinance institution, which the officer did not consider transferable. I read the letter line by line. What made it hard wasn't just that she'd been refused — it was that I understood every reason. I'm in the same queue, waiting for my own decision, and over the years I've helped a lot of friends and family enter the pool and fill their ePR applications. If I had seen her application before she submitted it, I could have flagged these things. That thought sat with me for days. When an email from the DEV Community landed about a challenge to build something creative and useful, it was the push I needed.

So I decided to build a Gemma 4–powered assistant that flags these mistakes before an applicant hits submit. The goal isn't to replace immigration lawyers or consultants. It's to give ordinary applicants — especially people navigating these systems alone — a second pair of eyes before costly mistakes become refusals.

Why Gemma 4

This project needed a model with structured reasoning capability, able to handle country-specific rules, and cost-effective.

Gemma 4 was the right fit because it gave very structured JSON output, and could hold long prompts without drifting from the real results.

I didn't do a technical review with other models, but I read about Gemma 4 and was convinced it could do the job, so I started building.

It actually mattered that I could run it via OpenRouter for free, because this proves that any developer in a place where resources are limited can conveniently build serious AI apps with Gemma 4.

On paper, Gemma 4 was the right model. The real test was what it would do when given a Cameroonian applicant's data.

Where Gemma 4 got it wrong

I ran my first test, in which I entered the data and details of a computer science and ICT government secondary school teacher. This is, of course, a typical example of the kind of applicant I have personally helped, so I know what a correct output should look like.

The output told me to translate any French documents into English. For the Cameroonian context, which was my test data, this is wrong — because Cameroon, just like Canada, is a bilingual country, and documents in French and English are both accepted by IRCC. Worth noting is that Gemma was not stupid. It simply didn't have the local context, because globally speaking, that advice for someone from Cape Verde or Equatorial Guinea is perfect. Gemma applied a firm rule without considering the special status of Cameroon.

With the same test data, Gemma flagged the teacher for missing CNPS. This was wrong, because civil servants in Cameroon are documented by l'acte d'intégration. Globally, Gemma's logic was correct, but locally it didn't hold.

Looking at the output again, it clicked: the two scenarios above were not two separate bugs — it was Gemma using the same reasoning pattern. It reasons well, but it didn't have the Cameroon context. The fix wasn't a better model. It was giving Gemma the context it didn't have.

The fix

After my first test, it dawned on me that I had to teach Gemma 4 about the Cameroonian context with regard to what I was building.

I made Gemma 4 understand there is a real difference between employees of the public and private sectors: civil servants are documented by l'acte d'intégration, while CNPS affiliation applies to private sector workers. I also taught it the bilingual rule — never recommend French-to-English translation, because Cameroon is bilingual, just like Canada. And I taught it to preserve local terminologies like "Lower Sixth" and "Probatoire," because that is what tells IRCC the employment letter duties are not copied verbatim from the NOC code.

It is worth mentioning that it wasn't a single prompt that produced the best results. Four rounds of testing with a range of data, finding gaps, and refining the prompts is what got us there. For example, a later test surfaced a gap that needed addressing: the microfinance / commercial-bank intermediary funds transferability issue, and the payslip-versus-bank-deposit consistency check.

Gemma 4 is actually a very capable model. With a precise domain context, it is reliable enough to produce locally correct output. No fine-tuning needed — just precise prompts.

Two real refusals

This isn't theoretical. Below are two real IRCC refusal letters from Cameroonian applicants, anonymized for this article.

Exhibit A — a web designer applying as NOC 21233, cited for three failures: cash payment without CNPS affiliation, payslip amounts not matching bank deposits, and proof-of-funds documents on Norton Financial letterhead carrying UBA's SWIFT code (UNAFCMCX), which the officer read as evidence that the funds were not actually transferable.
Anonymized IRCC refusal letter citing cash payment without CNPS, payslip-deposit mismatch, and a SWIFT code mismatch between Norton Financial Corporation and UBA

Exhibit B — funds held at LA MEC microfinance with no proof of a commercial-bank pathway, plus an acte de donation submitted without the donor's bank statements to back it up. The officer concluded the funds were not reliably transferable.

Anonymized IRCC refusal letter citing funds at LA MEC microfinance with no commercial-bank pathway, and an acte de donation without donor bank statements

Every ground cited in both letters — cash payment, missing CNPS, payslip-deposit mismatch, microfinance via commercial-bank intermediary, gift deed without donor records — is flagged by the tool before submission.

What this means

Gemma 4 is a capable open model, freely accessible and running on a developer's laptop without infrastructure or budget. As a developer whose laptop is not powerful enough to train models, I was still able to build something unique and useful for my community.

Nobody in San Francisco was going to build a Cameroon-aware immigration assistant. Not because the developers there are not smart, but because Express Entry refusals in Yaoundé are not a problem they see. The people best placed to build for a niche are the people inside it. Open, capable models make that possible.

Gemma 4 is for builders everywhere who understand real problems that nobody else is going to solve for them.

Top comments (0)