Side-by-side benchmark comparison across agentic, coding, multimodal, knowledge, reasoning, and math workflows.
Nova Pro
38
0/8 categoriesQwen3.5-35B-A3B
68
Winner · 7/8 categoriesNova Pro· Qwen3.5-35B-A3B
Pick Qwen3.5-35B-A3B if you want the stronger benchmark profile. Nova Pro only becomes the better choice if you would rather avoid the extra latency and token burn of a reasoning model.
Qwen3.5-35B-A3B is clearly ahead on the aggregate, 68 to 38. The gap is large enough that you do not need to squint at the spreadsheet to see the difference.
Qwen3.5-35B-A3B's sharpest advantage is in coding, where it averages 72.6 against 17.5. The single biggest benchmark swing on the page is LiveCodeBench, 14% to 74.6%.
Qwen3.5-35B-A3B is the reasoning model in the pair, while Nova Pro is not. That usually helps on harder chain-of-thought-heavy tests, but it can also mean more latency and more token spend in real use. Qwen3.5-35B-A3B gives you the larger context window at 262K, compared with 128K for Nova Pro.
BenchLM keeps the benchmark table and the operator tradeoffs on the same page so a better score does not hide a materially slower, pricier, or smaller-context model.
Runtime metrics show N/A when BenchLM does not have a sourced snapshot for that exact model. The scoring rules and freshness policy are documented on the methodology page.
| Benchmark | Nova Pro | Qwen3.5-35B-A3B |
|---|---|---|
| AgenticQwen3.5-35B-A3B wins | ||
| Terminal-Bench 2.0 | 31% | 40.5% |
| BrowseComp | 39% | 61% |
| OSWorld-Verified | 32% | 54.5% |
| tau2-bench | — | 81.2% |
| CodingQwen3.5-35B-A3B wins | ||
| HumanEval | 33% | — |
| SWE-bench Verified | 19% | 69.2% |
| LiveCodeBench | 14% | 74.6% |
| SWE-bench Pro | 20% | — |
| Multimodal & GroundedQwen3.5-35B-A3B wins | ||
| MMMU-Pro | 37% | 75.1% |
| OfficeQA Pro | 46% | — |
| ReasoningQwen3.5-35B-A3B wins | ||
| MuSR | 37% | — |
| LongBench v2 | 51% | 59% |
| KnowledgeQwen3.5-35B-A3B wins | ||
| MMLU | 41% | — |
| GPQA | 40% | 84.2% |
| SuperGPQA | 38% | 63.4% |
| MMLU-Pro | 53% | 85.3% |
| FrontierScience | 41% | — |
| SimpleQA | 39% | — |
| Instruction FollowingQwen3.5-35B-A3B wins | ||
| IFEval | 66% | 91.9% |
| MultilingualQwen3.5-35B-A3B wins | ||
| MGSM | 61% | — |
| MMLU-ProX | 60% | 81% |
| Mathematics | ||
| AIME 2023 | 41% | — |
| AIME 2024 | 43% | — |
| AIME 2025 | 42% | — |
| HMMT Feb 2023 | 37% | — |
| HMMT Feb 2024 | 39% | — |
| HMMT Feb 2025 | 38% | — |
| BRUMO 2025 | 40% | — |
| MATH-500 | 59% | — |
Qwen3.5-35B-A3B is ahead overall, 68 to 38. The biggest single separator in this matchup is LiveCodeBench, where the scores are 14% and 74.6%.
Qwen3.5-35B-A3B has the edge for knowledge tasks in this comparison, averaging 79.3 versus 43.5. Inside this category, GPQA is the benchmark that creates the most daylight between them.
Qwen3.5-35B-A3B has the edge for coding in this comparison, averaging 72.6 versus 17.5. Inside this category, LiveCodeBench is the benchmark that creates the most daylight between them.
Qwen3.5-35B-A3B has the edge for reasoning in this comparison, averaging 59 versus 45.4. Inside this category, LongBench v2 is the benchmark that creates the most daylight between them.
Qwen3.5-35B-A3B has the edge for agentic tasks in this comparison, averaging 50.5 versus 33.3. Inside this category, OSWorld-Verified is the benchmark that creates the most daylight between them.
Qwen3.5-35B-A3B has the edge for multimodal and grounded tasks in this comparison, averaging 75.1 versus 41.1. Inside this category, MMMU-Pro is the benchmark that creates the most daylight between them.
Qwen3.5-35B-A3B has the edge for instruction following in this comparison, averaging 91.9 versus 66. Inside this category, IFEval is the benchmark that creates the most daylight between them.
Qwen3.5-35B-A3B has the edge for multilingual tasks in this comparison, averaging 81 versus 60.4. Inside this category, MMLU-ProX is the benchmark that creates the most daylight between them.
Get notified when new models drop, benchmark scores change, or the leaderboard shifts. One email per week.
Free. No spam. Unsubscribe anytime. We only store derived location metadata for consent routing.