Why Good Full Stack Developer Candidates Still Get Rejected

EXAMPLE PANEL NOTES (illustrative)

Candidate A
+ React components clean, good state handling
+ Explained project UI flow clearly
- Could not write a LEFT JOIN without help
- API returned 200 for errors
- Resume lists 'expert in Node.js'
Concern: backend tasks would need heavy support.

Candidate B
+ Solid in React, comfortable in SQL
+ Explained API errors and status codes
- UI less polished than A
Decision: B is the closer fit for this team.

AFTER A REJECTION, ASK YOURSELF

1. Which question made me least comfortable?
   ______________________________________
2. Which layer was it in?
   frontend / backend / database / devops
3. Did my resume promise more than I showed?
   Y / N   Which line? ____________________
4. Did the role description stress a skill
   I barely discussed? ____________________
5. What one thing would most likely have
   changed the result? ___________________

// Works, but runs one query per order
router.get('/api/orders', async (req, res, next) => {
  try {
    const { rows: orders } = await pool.query(
      'SELECT id, customer_id, total FROM orders ORDER BY id DESC LIMIT 50'
    );
    for (const order of orders) {
      const { rows } = await pool.query(
        'SELECT name FROM customers WHERE id = $1',
        [order.customer_id]
      );
      order.customerName = rows[0] ? rows[0].name : null;
    }
    res.json(orders);
  } catch (err) {
    next(err);
  }
});

// One round trip to the database
router.get('/api/orders', async (req, res, next) => {
  try {
    const { rows } = await pool.query(
      `SELECT o.id, o.total, c.name AS "customerName"
         FROM orders o
         LEFT JOIN customers c ON c.id = o.customer_id
        ORDER BY o.id DESC
        LIMIT 50`
    );
    res.json(rows);
  } catch (err) {
    next(err);
  }
});

// LEFT JOIN keeps an order even if its customer
// row is missing, matching the first version.

function Profile({ userId }) {
  const [user, setUser] = useState(null);

  useEffect(() => {
    fetch(`/api/users/${userId}`)
      .then(res => res.json())
      .then(data => setUser(data));
  }, []); // bug 1: userId missing from dependencies

  // bug 2: even with [userId], switching users fast
  // can let an older response overwrite the newer one.

  return user ? user.name : 'Loading...';
}

function Profile({ userId }) {
  const [user, setUser] = useState(null);

  useEffect(() => {
    let ignore = false;
    setUser(null);
    fetch(`/api/users/${userId}`)
      .then(res => res.json())
      .then(data => {
        if (!ignore) setUser(data);
      });
    return () => {
      ignore = true;   // runs before the next effect
    };
  }, [userId]);

  return user ? user.name : 'Loading...';
}

// Each effect run has its own 'ignore' variable.
// When userId changes, cleanup marks the previous
// request as stale, so its late response is dropped.

RATE YOURSELF 1-5 HONESTLY

Frontend
  Components and state            ___
  Effects and data fetching       ___
Backend
  Route design and status codes   ___
  Validation and error handling   ___
Database
  Joins and aggregates            ___
  Indexes and N+1 awareness       ___
Delivery
  Git workflow                    ___
  Deploying the app               ___

Lowest two scores = your next focus.

FOR EACH SKILL ON YOUR RESUME

Skill: ______________
What level does the wording suggest?
  beginner / working / strong / expert
What level would an interview show?
  beginner / working / strong / expert

If they differ, rewrite. Examples:

"Expert in Node.js"
 -> "Built REST APIs in Node and Express
     with validation and JWT auth"

"Proficient in SQL"
 -> "Write joins and aggregate queries;
     added indexes for slow list endpoints"

IF DATABASE IS YOUR WEAK LAYER
  - Rewrite one list endpoint with a JOIN
  - Log query count per request
  - Add one index and check EXPLAIN

IF FRONTEND EFFECTS ARE WEAK
  - Build a profile switcher with fast clicks
  - Reproduce the race, then fix it
  - Explain the cleanup function aloud

IF API DESIGN IS WEAK
  - Design CRUD routes for a new resource
  - Return correct codes for each error
  - Write one API test per error case