“Tell us about a system or app you built or improved”

For developer, data and system posts this question decides the interview. The panel wants proof that you have shipped something real and that you can talk about it clearly: what problem it solved, who used it, what you did yourself, and what happened after. It does not have to be big. An attendance app used by 12 teachers, an Excel dashboard that replaced a paper register, or a shop website you rebuilt all score well if you describe them properly.

1. 1The problem and who had it: “The clinic recorded stock on paper and ran out of amoxicillin twice a quarter.”
2. 2What you built or changed, in one plain sentence, then the tools: “A stock-tracking web app, Laravel and MySQL, on a local server.”
3. 3Your part exactly: “I designed the database and wrote the back end; a colleague did the design; I did the deployment alone.” Say “we” for the team and “I” for your own work.
4. 4One hard problem and how you solved it. This is where the panel learns how you think: the internet dropped mid-save and created duplicate entries, so you added a check on the server.
5. 5The result with a number: users, time saved, errors avoided, money, months in use.
6. 6What you would do differently or next. It shows you review your own work.

If you have not built anything at work yet, use a university project, a freelance job, or something you built for your family's business, and say so honestly. What matters is that it was real, someone used it, and you can explain every part you claim. A panel in Mogadishu or Hargeisa will ask “why did you choose that framework?” and “what broke?”, and a person who copied a tutorial cannot answer.