Home/Work

Teaching giant models to pack light.

Where
Huawei, Processor Algorithm Research Center, Singapore
Role
AI Algorithm Researcher
When
Dec 2025 → Nov 2026
Models
Qwen3-30B-A3B, Qwen3-VL-30B
Hardware
Ascend 910B NPUs
The one-paragraph version

Big models are mostly storage. Billions of numbers, each one usually kept at 16 bits, waiting to be multiplied. My year at Huawei was spent asking how many of those bits we can quietly throw away before the model notices. It went from a paper about letting each expert pick its own bit budget, to 2-bit vision-language models, to a side quest that taught a research agent to stop re-Googling things it already knew.

Scroll slowly. The panel shows one layer of a Mixture-of-Experts model and changes with each chapter. It's an illustration, not real data.

Pointing at the Huawei logo
me-huawei.jpg
The Huawei crew in front of a giant horse sculpture
huawei-team.jpg
01

The memory problem nobody brags about.

A Mixture-of-Experts model is a crowd of specialists. Qwen3-30B-A3B has 128 experts in each layer. For every token, a little router picks 8 of them and the rest sit the turn out.

That's why it only does about 3B params of work per token even though it's 30B big. Cheap to run, in theory. The catch: all 128 experts still have to live in memory, ready, in case the router calls on them.

Watch the panel: tokens drop into the router, which lights up 8 experts at a time. Every square is full size, because every expert is stored at 16 bits.

02

Not every expert deserves the same bits.

The usual way to quantize is to give every weight the same precision, say 4 bits, and call it a day. But experts aren't equal. Some get called constantly and carry a lot. Others barely show up.

DuoRate leans into that. It allocates precision per expert, so the bits go where they actually change the output. I contributed to the research, and the headline result is the number in the panel's corner.

2.9 bitsper weight on average
≈ 4-bitquality on Qwen3-30B-A3B
Paper · Oct 2026

DuoRate — per-expert precision allocation for MoE serving

arXiv:2610.13328Submitted to ICML & CVPR
03

Then I went all the way down to 2 bits.

Next I built a post-training quantization pipeline for Qwen3-VL-30B, a vision-language model that reads images as well as text. "Post-training" means no retraining. You take the finished model and compress it.

The recipe was W2A16: 2-bit weights, 16-bit activations. Sixteen bits down to two is 8× smaller weights. That was the target, on Ascend 910B NPUs.

8×target weight compression
W2A162-bit weights, 16-bit activations

Napkin math: about 30B weights × 16 bits ≈ 60 GB. At 2 bits it's ≈ 7.5 GB. Watch the memory bar shrink.

04

Where do the tokens actually go?

To spend bits wisely, you need to know which experts actually get used. So I dug into expert-routing behaviour across vision-language workloads: which experts light up for text, which for images, and how lopsided the traffic gets.

That map is what tells a compression scheme where precision is worth spending, and where it's wasted on an expert that barely gets called.

Try it: switch token types and watch different experts heat up. The pattern here is made up for illustration. The real analysis is in the research.

05

Side quest: an agent that Googled too much.

Not everything was bits. I also worked on TTD-DR, a deep-research agent that writes reports by searching, drafting, and revising. It kept searching for things it had basically already found, and it kept asking an LLM "is this relevant?" over and over.

I plugged in LightRAG, which builds a knowledge graph out of everything the agent has already read. Then I replaced the LLM relevance check with embedding-similarity gating: if a new query is close enough to something the graph already knows, skip the search.

60–80%fewer redundant web searches
40–60%fewer LLM calls per query

In the panel: green queries get answered from the graph. Orange ones still go to the web and add a new node.

Before Huawei

The origin arc.

Jun → Jul 2024

Foresight EdgeData Analyst Intern · Singapore

My first time turning messy sales data into something people check every morning. I built a Power BI dashboard covering 8 SME clients and Python models for sales forecasting and spotting customers likely to churn.

Oct 2023 → Jan 2024

Yasham SoftwareSoftware Development Intern · India

Replaced a pile of manual workflows with a Laravel + MySQL CRM, including logins, role-based access, and transaction processing for the internal CRM and inventory. This is where I learned that "the backend" is mostly edge cases.

2026 · invite-only

Jane Street & OptiverFirst Year Trading & Tech Program · Exclusive Insights Day

Mock trading simulations on market-making and risk, plus probability classes taught by full-time traders. Basically a crash course in thinking clearly when you don't have all the information.