Skip to content
All books
Stage 1 · Get found

The Silent Rejection

Why good engineers get no reply, and who decided before anyone read the code.

5.0 · 2 reviews on Gumroad

About the book

You apply, you hear nothing, and nobody tells you why. The rejection happened, but it happened silently, before the interview existed, made by someone who spent seconds on your profile.

“As engineers, we are always focused on the skills we need to improve, but we often forget that there is another layer before those skills are evaluated, and maybe not forgetting it, we just don't know it exist.”

Juan Francisco Dorado Torres, Senior iOS Engineer

This book maps that decision. The author has conducted 500+ technical interviews from the hiring side, and before each one had to decide who was worth the hour. The engineers who never got it were often not weaker. They were harder to read.

You get the two-reader test that every profile must survive, a 100-point Visibility Score across six categories, and four repair plans routed by your weakest category, not a generic checklist.

What you get

  • The seven stages your profile passes through, and why a clean parse is not a ranking
  • The two-reader test: a recruiter and a hiring manager read the same profile for different things
  • A 100-point Visibility Score in six categories that routes you to one of four repair plans
  • Two engineers, iOS and backend, shown before and after
  • Turning public evidence into claims you can defend in the room
  • Fill-in templates for your headline, about section, recruiter message and referral request

A page from the book

Copied as printed, so you can judge the format before you buy.

Chapter 2, page 19

The same claim has two readers

Low signal

“Experienced engineer who worked on scalable systems.”

What the recruiter concludes

The wording is generic and cannot be matched to a precise search.

What the hiring manager concludes

“Scalable” is an unsupported adjective. There is no boundary, load, failure mode, or decision to test.

High signal

“Owned the offline retry path for the checkout flow, removed a crash on reconnect the team tracked, and set the crash-free threshold each release shipped against.”

What both conclude instead

The candidate owned a defined technical problem. The interviewer can ask about the failure mode, alternatives, thresholds, and result. The high-signal version does more than sound stronger. It creates a testable claim. Testability is what separates evidence from promotion.

Want more pages?

Before and after

Headline

Before

iOS Developer

After

Senior iOS engineer | Payments and checkout | Swift, offline-first

Resume bullet

Before

Worked on the checkout screen.

After

Owned the offline checkout flow for a payments app, removing a reconnect crash on the top purchase path and holding the crash-free rate above the release gate across eighteen releases.

Choose your edition

Every edition includes free lifetime updates.

Book

PDF and EPUB

$69

The complete 81-page book. Understand how the decision is made and fix every signal yourself.

  • The Silent Rejection, PDF and EPUB
  • The 100-point Visibility Score and the four repair plans
  • Fill-in templates inside the book
Get the book, $69
Core edition

Book + Toolkit

The book plus the tools

$99

Everything in the book, plus the fill-in-the-blank tools to do the work in one sitting.

  • The Visibility Score workbook, printable PDF and editable Word
  • Resume bullet templates: the Action + Problem + Impact formula, 10 fill-in templates and worked examples by discipline
  • LinkedIn templates: 15 headline examples, the four-part About section and a Featured checklist
  • Recruiter and referral scripts
  • Editable Word versions of every template, and a 30-minute start path
Get the book and Toolkit, $99

What is inside

  1. 1The decision before the visible eventp. 10
  2. Parsing is not rankingp. 14
  3. 2Signal and skillp. 17
  4. 3The cost of ambiguityp. 21
  5. 4Choosing what to be legible asp. 23
  6. The visibility scorep. 26
  7. 5Your professional identityp. 32
  8. 6Your resumep. 34
  9. 7Your LinkedInp. 38
  10. 8Your outreachp. 42
  11. Before and after: two profilesp. 45
  12. 9Public evidence when the work is inspectablep. 52
  13. 10What happens after the forwardp. 61
  14. 11The signals that clear senior and staff screensp. 66
  15. 12The routed visibility upgradep. 72
  16. Resourcesp. 78

What readers say

“Usually I don't write reviews but this one really helped me. I used this book and improved my resume and LinkedIn. My visibility score went from 53 to 96 from 100 and I started getting replies and interview invites. I know how to approach recruiters. The idea of signal vs skill made a lot of sense to me. It showed me that I was not being seen clearly, even if I had the skills. The book helped me fix how I present my work in a simple and practical way. After using it, I finally started getting more chances for interviews.”

Anonymous
Gumroad verified purchase

Reader reviews from Gumroad.

Who this is for

This is for you ifYour applications go quiet before a technical conversation begins.

  • Junior Engineer
  • Mid-Level Engineer
  • Senior Engineer
  • Staff-track Engineer
  • Career Changer
  • Returning Engineer

Not for

  • Already receive frequent recruiter outreach
  • Have a strong professional network that routes around cold applications
  • Consistently reach final interview stages
  • Want reassurance rather than a blunt read of what is weak
The library pathWhere this fits
  1. 01Get foundThe Silent RejectionYou are here
  2. 02Build the record and negotiateThe iOS Engineer playbook · Leverage
  3. 03InterviewThe iOS interview blueprint · The senior signal · Top 300 React Native interview questions · 500 Flutter interview questions · The senior SDET interview handbook
  4. 04Answer practice and live roundsThe 24-hour iOS interview answer book · The 24-hour Android interview answer book · Share your screen
  5. 05Architecture and qualitySwiftUI under load · Mobile System Design blueprint · Security is a feature · The second pass
  6. 06Staff systems and ownershipAltitude · Ticket taker, outcome owner
  7. 07Build with AIBuild with your brain on (coming soon)
  8. 08LeadLeadership blueprint (coming soon)
  9. 09ArchitectArchitect blueprint (coming soon)
Portrait of Mike Salari

About the author

Mike Salari

Staff Mobile Engineer · Mobile Architect · Technical Author

Before conducting 500+ technical interviews from the hiring side, I had to decide who was worth one. This book documents the decision path that filtered people out, and how to survive it.

15 years building production mobile software, with experience across Apple, Adobe, Cisco, Mastercard and Visa. 500+ technical interviews from the hiring side.

Read the full story

Before or after you buy

Not ready yet? Check your visibility score →

Already own it? After the book, fix the document and targeting evidence that still fails the first scan. Explore Engineer Career Rebuild →

Put the positioning work into practice with LineUp: build and tailor your CV, then the cover letter and LinkedIn headline around it. Open LineUp CV · Visit visibility.salari.dev

FAQ

The Silent Rejection: questions before you buy

Why am I not getting interview calls?

Often it is not skill. Recruiters scan in seconds and skip anything ambiguous. A generic headline, a duty-list resume or an unfinished LinkedIn filters you out before anyone reads your experience.

Why do recruiters ignore my LinkedIn profile?

Because they search and scan on signals: a specific headline, a matchable title, a clear About and consistent positioning. The blueprint shows the exact signals recruiters look for and how to fix yours.

Does personal branding matter for software engineers?

Yes, but not in the influencer sense. It means making the experience you already have legible and matchable, so the right opportunities can find you.

How can senior engineers become more visible?

By fixing the surfaces a recruiter actually sees: identity, resume, LinkedIn and outreach, and by stating scope and impact instead of responsibilities.

What signals do recruiters evaluate?

The headline, the resume bullet structure (action, problem, impact), the filename, the LinkedIn About and the consistency between them. Each one is a reason to stop or to move on.

Is this only useful when job hunting?

No. Visibility affects promotions, referrals and internal opportunities too. It is about being understood, not only about being hired.

Is it specific to iOS or mobile engineers?

No. The framework applies to backend, frontend, mobile, data and platform engineers, from mid-level to staff.

How long does it take to apply?

The upgrade plan is built to be done in a single focused sitting, surface by surface.

Is there a free way to start?

Yes. The free Engineer Visibility Score gives you a 100-point audit and your weakest surface before you buy anything.

What format do I get and how is it delivered?

An instant PDF and EPUB download through Gumroad, with lifetime updates.

Visibility is access to evaluation.

The decision that filters you happens before anyone reads your code. Start with the check in Chapter 1. It takes ten minutes.

Get the book, From $69

Share this book

XLinkedInBlueskyThreadsHacker News