Practice prompt engineering

The best engineers
write the best prompts.

AI hasn't replaced engineers — it's raised the bar. Practice on deliberately vague problems. Get scored on how well you think, not just what you ask.

The app is too slow.
GoalExplore requirements
1

Your Prompt

A few guesses — frontend is probably re-rendering too much, the API gateway might be hitting a distant region for some users, and the queries likely aren't indexed. I'd start with the query layer first.

AI Response

Good instinct to narrow it down. It's slow for everyone on the main feed — and yes, the DB is the culprit. Queries aren't indexed and the feed hits it on every load...

Prompt score
8.2 / 10

The shift

Code is no longer
the bottleneck.

For decades, the ability to write code was the scarce skill. Now AI can write the code. What it can't do is think clearly about the problem.

The new leverage point is upstream: defining constraints, surfacing tradeoffs, asking the right questions. In other words — prompting well.

Before AI

Write the implementation

Now

Define the requirements precisely

Before AI

Know every API

Now

Know what to ask for

Before AI

Debug line by line

Now

Narrow the problem space quickly

How it works

01

Pick a vague problem

Every problem is deliberately under-specified — just like real engineering work. No hand-holding.

02

Write a prompt chain

Ask clarifying questions, define constraints, explore tradeoffs. The AI mirrors the quality of your thinking.

03

Get scored on your prompts

Your prompts are evaluated — not the AI's answers. Better questions unlock better scores and deeper insights.

Community

See how others
approach the same problem.

View all attempts
AK
alex_k
Security-first

First thing I'd lock down is auth — who can shorten a URL, and can they see analytics for links they didn't create? Permissions need to be airtight before we talk scale.

9.1 / 10
MR
mia_r
Scalability-first

At 10K redirects per second the bottleneck is the read path. I'd assume a CDN-edge cache in front of everything and work backwards from there. Write path barely matters.

8.7 / 10
JT
j_tran
User-first

Before any infra — what does a broken redirect cost us? If users hit a dead link once they churn. I'd rather over-engineer reliability than chase p99 latency on day one.

8.4 / 10

Ready to level up?

Find out how good your
prompts really are.

Pick a problem, write your prompts, and see how you stack up against the best thinkers.