Job Search After A Layoff

Notes from "What I'd do if I got laid off as senior engineer", a 6:47 video on the Let's Get Rusty channel uploaded 2026-08-23, read 2026-10-25 (8,842 views at the time). The speaker is Bogdan Pshonyak. A 2017 Green River post says he joined Tableau as a software engineer; his public LinkedIn profile lists Let's Get Rusty and earlier Swurveys, so "former Tableau engineer" is only as good as that post.

The video is the source for the strategy below; the transcript was read in full. A Vietnamese write-up of the same video circulates with extra advice — CV confidentiality, a tailoring checklist, a tracking sheet, preparation while employed — and those parts are marked as additions, not as his words.

Assess before applying

The first move is not to update the resume, message people on LinkedIn, or grind LeetCode. It is to look at the situation plainly.

Runway: how many months savings can carry you and your dependents. A long runway buys time for the right role; a short one means taking a fast, less ideal role first.
Market: which roles are losing demand, and how the current skills map to the roles that still hire. The video suggests a deep-research tool for the numbers, not vibes.
Target from both: cash short and specialization still in demand means apply in the same field now. Long runway and a declining specialization means spend the time moving to a new area.

He gives his own example: at a startup that was about to run out of money, barely out of school and without savings, he took his front-end skills and applied to local front-end roles through job sites and local networking events, and landed relatively quickly.

Write the achievements down while they are fresh

Recorded as a side note in the video, and the part people skip. Months later the project is remembered but not the problem, the decisions you made, or the result. Write it down early, with numbers where they exist, so the resume can show impact instead of a task list.

The write-up adds two sensible limits: describe scope, complexity, responsibility, and outcome when there is no metric, and keep to the confidentiality duty to the old employer — no source code, customer data, or internal documents in a personal file.

Specialize (the blue ocean)

A generic engineer is in a red ocean: many candidates with the same Go, Java, Python, SQL, Docker, and Kubernetes on the page, and a hiring manager with no reason to pick one. A blue ocean is a narrower area where few compete.

His example: a student with over a decade of experience across front end, back end, systems, and mobile was applying to embedded Rust roles and not getting interviews. They reframed everything embedded-adjacent toward embedded, cut the unrelated work, and he started getting interviews and landed the embedded Rust role. The point is not that everyone should switch to embedded Rust; a resume that reads as one specialty is easier to place than a list of ten domains.

The write-up's caveat is fair: a niche can be too small, so pick the intersection of what you can go deep on, what companies actually hire, and what you already have. The question to answer is "why should the company pick me for this role", not "am I the best engineer in the industry".

Tailor each application, use AI as an editor

One resume sent to hundreds of companies is cheap and weak. A role focused on database performance cares about query optimization and profiling; another cares about API design, distributed systems, or running production. If the resume buries the relevant part, the reader will not find it.

AI helps match a resume to a job description: feed it the posting and the resume, ask which requirements dominate, which achievements are relevant, and how to order them. The video's own advice is in that direction. The write-up adds the guardrail that matters: let AI present what you did, never invent experience, inflate results, or add tools you have not used, and be ready to defend every line in an interview.

Treat the search as a funnel

Thirty or forty applications is not a lot. His arithmetic, with optimistic conversion rates:

Stage	Assumed rate
Application → recruiter response	10%
Recruiter conversation → technical interview	50%
Interview → offer	25%

Two offers then need about 160 applications: 160 × 10% = 16 responses, 8 technical interviews, 2 offers. He calls these rates optimistic, so the real number is likely higher, and says he would start with hundreds — partly to have more interview practice. The point is to read each stage, not to send resumes mechanically: no responses means the resume or the role fit is wrong, failing technical rounds means the knowledge or the explanation is, and reaching final rounds without offers means something in the presentation or the criteria.

The write-up adds a tracker with company, role, date, source, status, and outcome per round. That is the data the funnel needs.

Use channels beyond job boards

Job boards, LinkedIn, and company career pages are the default, not the only route. Meetups, conferences, hackathons, and technical communities put you in front of engineers and tell you which teams are growing and what they are building.

Two stories from the video: he got his first job while still in college through networking events, when someone he had met months earlier started a company and reached out, which made the interview much easier. A friend used to wait outside the Uber offices and start conversations with engineers leaving the building. He rates this in-person work as an advantage precisely because most engineers will not do it.

The write-up is right that this is not a shortcut: networking widens access, competence and fit still decide the outcome, and a referral ask should not be the first message to someone.

His own target

If he were searching today, he says he would aim at developer tools, or back-end and infrastructure work tied to data and AI. That is a personal choice, not a recommendation, and it lines up with the specialization point above.

What the Vietnamese write-up adds

Confidentiality limits when recording achievements.
A four-step tailoring pass: read the posting, pick relevant projects, adjust summary/skills/bullet order, verify every claim.
A simple application tracker.
Networking as access rather than a shortcut.
Preparing while still employed: keep achievements, keep interview skills warm, update the profile, build the network.
No strategy guarantees a job in weeks; timing depends on the economy, location, level, field, and salary expectation.

Check before repeating

"10 months" average job search. A United Way NCA survey run 2026-02-26 to 2026-03-07 puts the average search at about 6.6 months and tech at 9.7 months, so the video's 10 is a rounding; the "longest of any industry" line comes from a secondary summary of that survey, not from reading the full report.
The funnel rates and the 160 figure are his illustration, not measured data. The multiplication is correct for the rates given.
"Hundreds of applications" is advice, not a target to hit blindly; quality of fit and the market decide what a realistic number is.
The embedded Rust story and the Uber story are anecdotes, not evidence that either tactic works generally.
Section headings and the "adds" list above follow the write-up's structure where the video is thinner; the strategies themselves are from the transcript.

Sources

See also: Job Applications · Salary Negotiation · IT Job Interview Notes · Interview Preparation Checklist