Skip to content
Dare Omotosho
ArticlesCareerNewcomer

What Sun Tzu's engaging the enemy principle teaches about job interviews

Sun Tzu wrote about engaging an opponent constructively rather than simply overpowering them, and it's an odd fit for career advice until you notice what a job interview actually is: a structured encounter where preparation, timing, and how you handle setbacks matter more than raw talent. A newcomer to tech walking into an interview is engaging in exactly the kind of contest Sun Tzu was describing, just with a job offer instead of territory at stake.

Show up prepared, not just willing

Sun Tzu's advice to appear weak in order to disarm an opponent translates, in an interview, into something closer to appearing genuinely prepared and interested rather than performing confidence you haven't earned. Three things build that preparation:

  • Research the company beyond the careers page, its mission, its products, and what's happened recently that a candidate who only skimmed the website wouldn't know.
  • Read the job description like a brief, not a checklist, identifying the specific skills and experience it's asking for and shaping your answers to show where you actually match.
  • Bring real questions, about culture, team structure, or the role itself, questions that demonstrate curiosity rather than filling a mandatory "any questions for us?" slot.

Doing this well signals something an interviewer can't get from a resume alone: that you took the opportunity seriously enough to invest time before you were asked to.

Strike with substance, not just skill lists

Sun Tzu's emphasis on striking at the right moment maps onto how you actually answer questions once you're in the room. The instinct to list skills is natural and largely useless; what lands is evidence.

  • Lead with accomplishments, concrete instances where a skill was applied to solve a real problem, not just a claim that the skill exists.
  • Quantify where you can. A number, a percentage, a measurable outcome does more work than an adjective.
  • Keep answers structured and plain. Jargon that isn't necessary for the question usually reads as padding rather than expertise.

A bad interview is data, not a verdict

Even careful preparation doesn't guarantee a clean interview, and that's fine. What separates people who improve from people who repeat the same mistakes is what happens afterward:

  • Go back over your own answers and be specific about where the response was weaker than it should have been.
  • Ask for feedback when it's appropriate to. Not every interviewer will give it, but the ones who do hand you something no amount of self-reflection can produce alone.
  • Practice deliberately, through mock interviews, recorded self-review, or just running through likely questions out loud, so the next attempt isn't starting from zero.

Where interviews are heading

AI-powered interview platforms are becoming a normal part of the early screening process, handling initial skills assessments before a human ever gets involved. That shifts some of the mechanical filtering earlier in the pipeline, but it doesn't replace what the final decision still comes down to: clear communication, real problem-solving ability, and whether you fit the team you'd actually be joining.

None of Sun Tzu's original text was written with a hiring manager in mind, but the underlying logic holds up: preparation beats improvisation, substance beats performance, and every encounter, won or lost, is information for the next one. Applied to an interview, that's less a metaphor than a practical strategy for treating your job search as something you can actually get better at.

Discussion

  • No comments yet, be the first to add one.

Comments appear once approved. Upvotes are live.