Frontier problems

Problems worth
your next three months.

If you already know what you can't stop working on, keep doing that. If you want to know what we think is underworked at the frontier of AI, read on.

Getting in doesn't require working on these — we're excited by anyone pointed at something this serious.

What algorithm is a transformer actually running?

Prior work claimed transformers implement gradient descent or ordinary least squares in-context. Recent work shows this is wrong — attacks designed for one don't transfer to the other. We don't actually know what algorithm large transformers implement. Someone needs to find out.

First connection: TBC First connection pending

How do you hijack an AI system, and how do you stop it?

A single poisoned example in a prompt can force a transformer to output whatever the adversary wants. Adversarial training helps, but the mechanistic explanation is still missing. The attack surface for deployed AI systems is almost entirely unmapped.

First connection: TBC First connection pending

Can you make a capable model run on hardware that costs less than a motorbike?

Most serious AI work assumes access to serious compute. Most of Southeast Asia doesn't have it. The gap between what's possible at the frontier and what's deployable in a constrained environment is an engineering problem, not a research one. Someone needs to close it.

First connection: TBC First connection pending

What does it look like when an AI system lies to its monitor?

Chain-of-thought reasoning was supposed to make AI systems interpretable. It turns out models can learn to produce reasoning that satisfies monitors without actually reflecting their internal process. Detecting this — and preventing it — is one of the hardest open problems in alignment.

First connection: TBC First connection pending

How do you audit an AI system you can't fully understand?

Regulators and institutions are being asked to certify AI systems they have no tools to inspect. The gap between "we need governance" and "we have the infrastructure to govern" is enormous. Building that infrastructure — evaluation frameworks, audit tools, policy-as-code — is tractable and urgent.

First connection: TBC First connection pending

What makes an AI system robust when someone is actively trying to break it?

Most AI systems are evaluated on clean data by users trying to make them work. Real deployment is adversarial — users trying to extract things the system shouldn't say, attackers trying to poison its inputs, environments nothing like the training distribution. Robustness under adversarial conditions is almost entirely unsolved.

First connection: TBC First connection pending

How do you build a reliable agent that acts over long horizons?

Current AI agents fail in predictable ways when tasks get long, ambiguous, or require multi-step planning. The failure modes are not well understood. Building agents that are reliable enough to be trusted with consequential tasks — and understanding why they fail when they do — is one of the defining problems of the next five years.

First connection: TBC First connection pending

What is the minimum viable governance infrastructure for AI?

Every country in SEA is trying to figure out AI policy. Almost none of them have the technical capacity to implement it. The gap isn't in the policy — it's in the tools. What would it actually take to build the monitoring, audit, and enforcement infrastructure that makes AI governance real rather than aspirational?

First connection: TBC First connection pending

Working on something not listed here? Good. Apply anyway. →

Have a problem, connection, or capital that belongs on this list? Email team@buildy0r.com with enough context to evaluate — we read everything.