Most hiring mistakes are visible in advance, if you know what to ask. These eight questions take ten minutes and tell you more than a portfolio does.
- Who will actually do the work? Ask for a name, not a team. A studio that cannot name the builder is often passing the work on.
- Can I see something you built and what changed afterwards? A good answer names a source for any number. A weak answer uses adjectives.
- Whose name will the code, the designs and the accounts be in? The answer you want is yours, from the first day.
- How will I know what you did each week? Written updates are better than a promise of a call.
- What happens if the store slows down or breaks after launch? Ask who fixes it and how fast they reply.
- Which apps will you add, and why? Every app can slow the store. A good developer can say what each one replaces.
- How will tracking work? If the answer does not mention how a sale reaches the ad platform, ask again.
- What would you not do for me? An honest studio can say what it is not good at.
What to listen for
Plain answers, named people, sources for numbers, and the word yes to handing over the keys. Be wary of anyone who cannot explain a step in words you understand.
Photograph from Unsplash.





