Skip to main content

Phase 0 - Recruiter Training Handbook

Technical Awareness for Non-Technical Recruiters

Purpose of Phase 0​

Phase 0 exists to build technical awareness, not technical expertise.

This phase is designed for recruiters with no engineering background who need to understand:

  • What software developers actually do
  • The difference between frontend, backend, fullstack, web, and mobile development
  • How software products are built at a high level

Recruiters are not expected to code. They are expected to understand what problem each role solves.

⚠️ Phase 0 must be completed before reviewing technical resumes or conducting screenings.

Training Philosophy​

  • Recruiters do not hire technologies.
  • They hire people who solve specific problems using technology.
  • Understanding roles at a conceptual level enables better screening, clearer communication, and fewer mistakes.

1. What a Software Developer Does (In Simple Terms)​

A software developer builds, maintains, and improves digital products.

Examples of products:

  • Websites
  • Web applications (dashboards, platforms, portals)
  • Mobile applications (iOS / Android)
  • Internal tools and systems

Developers:

  • Translate business needs into software
  • Solve problems through logic and structure
  • Maintain and improve existing systems

2. Web Development vs Mobile Development​

Web Development​

  • Software accessed through a browser (Chrome, Safari, etc.)
  • Examples: websites, admin dashboards, SaaS platforms
  • Runs on laptops, desktops, tablets

Mobile Development​

  • Software installed on mobile devices
  • Examples: iOS and Android apps
  • Built specifically for phones and tablets

👉 Web and mobile are different platforms and often require different skills.

3. Frontend Development​

Frontend developers work on what users see and interact with.

Examples:

  • Screens and pages
  • Buttons, forms, menus
  • Layout, responsiveness, visual behavior

If frontend fails:

  • Users get frustrated
  • Interfaces break
  • Products feel slow or confusing

Frontend is closely related to user experience (UX).

4. Backend Development​

Backend developers work on what happens behind the scenes.

Examples:

  • Business logic
  • Data storage and processing
  • APIs that connect systems
  • Authentication and security

If backend fails:

  • Data is incorrect
  • Systems crash
  • Security is compromised

Backend work focuses on reliability and correctness.

5. Fullstack Development​

Fullstack developers work on both frontend and backend.

Clarifications:

  • Fullstack does not mean expert in everything
  • Most fullstack developers are stronger on one side
  • Fullstack roles are common in startups and small teams

Recruiters must identify: 👉 Which side (frontend or backend) the candidate is stronger in.

6. How the Pieces Work Together​

At a high level:

  • Frontend → User interaction
  • Backend → Logic and data
  • Database → Stores information
  • API → Connects frontend and backend

All parts must work together for a product to function correctly.

7. Common Developer Role Variations​

Recruiters may see titles such as:

  • Web Developer
  • Software Engineer
  • Frontend Engineer
  • Backend Engineer
  • Mobile Developer
  • Fullstack Engineer

👉 Titles vary. Responsibilities matter more than titles.

8. What Recruiters Should Listen For​

During resume reviews or conversations, recruiters should listen for:

  • What part of the system the developer worked on
  • Whether they mention users, data, or systems
  • Whether they explain why something was built

⚠️ Avoid focusing only on tools or buzzwords.

9. What Recruiters Are NOT Expected to Do​

Recruiters are not expected to:

  • Write or review code
  • Judge technical architecture
  • Compare technologies in depth

Recruiters are expected to:

  • Understand role boundaries
  • Identify mismatches early
  • Ask clarifying questions

10. Completion Criteria for Phase 0​

A recruiter completes Phase 0 when they:

  • Can explain frontend, backend, and fullstack in simple words
  • Understand the difference between web and mobile development
  • Can explain what developers build
  • Feel comfortable reading technical resumes at a high level

11. Non-Technical Glossary for Recruiters​

This glossary explains common technical terms in plain language:

  • Frontend → The part of an application users see and interact with.
  • Backend → The part of an application that handles logic, data, and security behind the scenes.
  • Fullstack → A developer who works on both frontend and backend (usually stronger in one area).
  • Web Application → A software product accessed through a browser.
  • Mobile Application → A software product installed on a mobile device (iOS or Android).
  • UI (User Interface) → The visual layout of screens and elements.
  • UX (User Experience) → How easy and pleasant a product is to use.
  • API → A way for systems to communicate with each other.
  • Database → Where data is stored and retrieved.
  • Server → A computer or system that runs backend logic.
  • Cloud → Online infrastructure used to host applications and data.
  • Authentication → How users log in and prove who they are.
  • Framework → A set of tools developers use to build software faster.
  • Tech Stack → The combination of technologies used in a project.
  • Deployment → Releasing software so users can access it.
  • Production → The live version of a product used by real users.
  • Bug → An error or problem in software.
  • Feature → A specific function or capability of a product.