Choosing an NEA project that won't sink you

Every year, some of the strongest programmers in a cohort pick an NEA project so ambitious they spend all their time fighting the build and none of it demonstrating algorithmic thinking, testing, or evaluation — the things that actually carry marks.

A good NEA project idea usually has a few things in common:

• A real, specific problem for a real, specific type of user — not "an app that does everything for everyone."
• Enough algorithmic and data-structure depth to show off what you've learned, without requiring you to invent entirely new computer science.
• A scope you can finish with time left over for testing and evaluation — which, realistically, are worth as much as the build itself.

Before committing, ask honestly: could I explain, right now, what data structures I'd use and why? If the answer is vague, the idea probably needs narrowing.

Our NEA Project Idea Generator is designed to surface project concepts with this balance already considered, including an explicit feasibility score across programming depth, database depth, testing opportunities and achievable scope — a starting point for your own planning, not a shortcut around it.