The Honest Reason Full Stack Developer Rejections Rarely Get Explained

ROUND: Technical 2 (illustrative example)
ROLE: Full Stack Developer, junior

Problem solving     3/4  Good approach, slow on edge cases
Frontend (React)    3/4  Clean component, state handled well
Backend / API       2/4  Pagination design weak, no limit cap
Database            2/4  Could not explain index for sort
Code quality        3/4  Readable, good names
Communication       3/4  Clear once prompted to structure

Recommendation: Lean no hire
Reason: backend depth below what this team needs

Subject: Your application for Full Stack Developer

Dear candidate,

Thank you for taking the time to interview with us.
After careful consideration, we have decided to move
forward with other candidates whose experience more
closely matches our current needs.

We wish you the best in your job search.

Regards,
Talent Team

(Everything useful from the scorecard is missing.)

Subject: Thank you, and one small request

Hi [Recruiter name],

Thank you for letting me know, and for the chance
to interview for the Full Stack Developer role.
I enjoyed the API design discussion in particular.

If it is possible, I would be grateful for one area
the panel felt I should strengthen. I completely
understand if this is not something you can share.

Best regards,
[Your name]

LISTEN FOR THESE DURING THE INTERVIEW

- Interviewer asks the same thing twice
  -> your first answer missed the point

- "Can you think of another way?"
  -> they wanted a different approach

- "What would happen with a million rows?"
  -> scale or efficiency was the real topic

- They move on quickly after a hint
  -> the hint was the answer they wanted

Write these down right after the round.

// GET /api/products?page=3&limit=20
router.get('/api/products', async (req, res, next) => {
  try {
    const limit = Math.min(Math.max(parseInt(req.query.limit, 10) || 20, 1), 50);
    const page  = Math.max(parseInt(req.query.page, 10) || 1, 1);
    const offset = (page - 1) * limit;

    const { rows } = await pool.query(
      'SELECT id, name, price FROM products ORDER BY id DESC LIMIT $1 OFFSET $2',
      [limit, offset]
    );
    res.json({ page, limit, items: rows });
  } catch (err) {
    next(err);
  }
});

// GET /api/products?after=1234&limit=20
router.get('/api/products', async (req, res, next) => {
  try {
    const limit = Math.min(Math.max(parseInt(req.query.limit, 10) || 20, 1), 50);
    const after = parseInt(req.query.after, 10);

    const { rows } = Number.isFinite(after)
      ? await pool.query(
          'SELECT id, name, price FROM products WHERE id < $1 ORDER BY id DESC LIMIT $2',
          [after, limit])
      : await pool.query(
          'SELECT id, name, price FROM products ORDER BY id DESC LIMIT $1',
          [limit]);

    const nextCursor = rows.length === limit ? rows[rows.length - 1].id : null;
    res.json({ items: rows, nextCursor });
  } catch (err) {
    next(err);
  }
});

COMPANY / ROUND: ___________  DATE: ______

Questions asked (as exact as possible):
1. _______________________________________
2. _______________________________________
3. _______________________________________

Where did the interviewer repeat or rephrase?
__________________________________________
Which hint did they give?
__________________________________________
My weakest answer and why:
__________________________________________
My strongest answer and why:
__________________________________________

RATE EACH AREA 1-4, LIKE A SCORECARD

Problem solving       ___  Evidence: ________
Frontend              ___  Evidence: ________
Backend / API         ___  Evidence: ________
Database              ___  Evidence: ________
Code quality          ___  Evidence: ________
Communication         ___  Evidence: ________

Lowest area after 3 interviews: ___________
That is my real feedback.

WITHIN TWO DAYS OF THE INTERVIEW

1. Pick the question you liked least.
2. Solve it fully with no time pressure.
3. List the follow-ups you expect:
   - bigger data? ____________
   - bad input?   ____________
   - concurrency? ____________
4. Write a 60-second spoken answer.
5. Say it aloud twice, then record it.
6. Add it to your 'answer again' document.