How to judge a developer before you hire, and how I answer each point
Abdul Wahed Nur · · 2 min read
In short: Ask for real work, business knowledge, honest limits, a written scope, visible progress and a clear handover.
Every developer says "best quality, best price". That sentence cannot be checked, so it is worth nothing. Instead of claiming to be better than everyone, here are the questions I would ask if I were hiring, with my honest answers.
1. Can I see something real that works?
Look for live systems, not screenshots. I run ekhaneikini.com, my own online store, and keep a service and parts management system in use. Both are linked on the Work page. There is also a demo, clearly labelled as a demo with sample data.
2. Does the developer know the business side?
Software fails more often because of misunderstood business rules than because of bad code. I run a real store, so I have lived with stock, couriers, returns and customers who pay in parts.
3. What will they refuse to promise?
I do not promise rankings, sales or "AI that does everything". I do not take SaaS builds, hardware, or autonomous AI agents as client work. The Services page lists what I do not offer.
4. How are changes and mistakes handled?
Every project starts with a written scope and milestones with a price for each. Changes after that are a new line on a new quotation, not a surprise on the final bill.
5. Can I see where the project stands?
You get a client area with milestones, a progress bar computed from finished milestones, written updates, private files, quotations and invoices.
6. What happens to the code and the server?
Deployment is set up per project, on your own server or hosting account. Ask what you will receive at the end, source code and setup notes included, and get it written into the scope.
Where I am honest about limits
- I am one developer. A large project moves at the pace of one person.
- My earlier eCommerce core system work (2020 to 2021) was defining the logic and directing its development, not writing the code.
- Some things are planned, not built. They are labelled as plans.
If another developer answers these six questions better than I do for your project, hire them. If I answer them well, send me the scope.
