How much tech fluency do you have?

Tech fluency is understanding how software works under the hood well enough to make decisions with judgment, talk as an equal with engineers, and direct an AI that builds for you.

It's not knowing how to code. It's having the mental map: what an API is, why a migration matters, what happens in a deploy. Without that map, every technical conversation is a list of words you don't understand. With it, you decide.

The questions cover the five fundamentals of modern software, one from each on every attempt:

• How the web works — APIs, HTTP, status codes, frontend vs backend.
• How software is built — databases, migrations, validation.
• AI and language models — what an LLM does, hallucinations, agents.
• Infrastructure and operations — Docker, CI/CD, environments, rollback.
• Your working environment — Git, commits, pull requests, environment variables.

You can build a product with AI without years of technical experience. But to direct that conversation — to know what to ask for, evaluate what you get, and decide well — you need to understand the foundations.

AI makes building more accessible than ever. Tech fluency is what lets you take advantage of it instead of being at the mercy of whatever it hands back.

This test measures whether you have the map. The next step is using it: building your own product from idea to deploy. That's what the Founding Product Engineer training teaches.

If this test feels too easy, you're ready for what comes next.

The questions come from Modern Software in 100 Questions. If you miss one, the full explanation is there, with analogies and no jargon. And if you want to go from understanding to building, the courses take you by the hand.