Hiring guides

7 pages in this section. Each one opens with a short answer, goes deeper, says where the advice does not apply, and ends with the questions people ask next. Written by Sachin Sharma. See the editorial policy.

Read these when you are about to hire. Each gives a checklist you can tick, the proof worth asking for, and the red flags that mean walk away. The list works for any developer, including me.

• 01What a developer actually decides for a non-technical founderA developer makes hidden system design choices that decide if your app works offline, scales to 10,000 users, or keeps data safe. Test them with real.
• 02What a developer actually does on a clinic booking appWhat a clinic booking app developer actually does: prevents double-bookings, manages no-shows, and follows DPDP Act rules. How to test for these skills.
• 03What a developer actually does on a coaching institute appA developer maps your student lifecycle, designs for low-tech parents, and builds systems that survive staff turnover. See the real decisions behind the code.
• 04What a developer actually does on a diagnostics lab appWhat a developer does on a diagnostics lab app: secure workflows, audit trails, and lab integration. How to test for these decisions.
• 05What a developer actually does for a small business websiteA developer for a small business website makes key decisions on speed, ownership, and cost control. See the 12 checks to test their fit before hiring.
• 06What a Flutter developer actually does on your first appWhat a Flutter developer actually does on your first app: the decisions they make, how to verify their work, and what must be in your contract
• 07What a Next.js developer actually does on a web productA Next.js developer makes architecture decisions like when to pre-render, when to use server components, and how to structure APIs—not just code in React.