How many software engineering jobs should I apply to?

For an active search: 100-300 for mid-level engineers, 200-500 for new grads (the funnel is narrower), 50-150 for senior+ engineers (less volume needed because referrals carry more weight). The exact number depends on response rates from your specific resume and target tier.

Is LeetCode still required in 2026?

For most large and mid-size tech companies, yes. The bar varies (FAANG-tier expects Medium-Hard fluency; many startups will take you with strong Easy-Medium), but coding interviews on algorithmic problems remain the standard first technical screen. Some companies (Stripe, Anthropic, a few others) prefer take-home or system-design-heavy interviews instead.

What's the typical software engineer interview process?

Recruiter screen (30 min) → 1 phone interview with engineer (45-60 min coding) → 4-6 onsite/virtual onsite rounds (mix of coding, system design, behavioral). The full loop typically runs 4-8 weeks from first contact to offer. Process length varies; FAANG is slower (6-8 weeks typical), well-organized startups are faster (2-4 weeks).

Can I get a software engineer job without a CS degree?

Yes, but it's harder than it was a few years ago. Self-taught and bootcamp graduates do land SWE roles in 2026, but the bar is higher: expect to need a substantive portfolio of real shipped projects, open-source contributions, and the same interview-prep depth as CS graduates. Smaller companies and contractor-to-hire paths are often more open to non-traditional backgrounds than large companies.

How long does a SWE job search take?

2 to 6 months for experienced engineers in 2026 is the realistic range, start of active search to accepted offer. New grads should plan for the August-February campus recruiting season. Senior+ engineers with strong networks often land in 1-3 months because referrals shortcut the funnel.

How to Find a Job as a Software Engineer (2026 Guide)

Software engineering is the largest tech-role family by volume and the most-discussed online, but most of the advice you'll find is either generic ("write a clean resume") or narrowly focused on FAANG interview prep. Here's the honest playbook for the actual SWE job search in 2026, by career stage and by role tier.

SWE job tiers and roles

"Software engineer" covers a wide spread of role specializations and pay bands. The major sub-categories:

Backend. Building services, APIs, databases. The deepest hiring market by volume. Languages skew Python, Java, Go, Node.js, Rust depending on company.
Frontend. Web (React, TypeScript dominant), increasingly with native-mobile crossover. Visual polish + interaction design + performance.
Full-stack. Both, with the expectation that you'll specialize within 1-2 years. Common at startups, less common at FAANG.
Mobile. iOS (Swift), Android (Kotlin). Smaller market than web in 2026 but stable.
Infra and platform. Kubernetes, distributed systems, observability, internal tooling. Pay band tends to be 10-20% higher than equivalent application engineering.
ML and AI engineering. The fastest-growing category in 2026. Strong demand at top pay bands, particularly for "ML for production" rather than pure research.
Embedded and low-level. Smaller market, concentrated at hardware and defense-tech companies. Higher technical bar, narrower job pool.

Where SWE jobs are posted

Company careers pages. The ground truth. Many roles live here days or weeks before being posted elsewhere.
LinkedIn. Largest aggregator + sourcing. Required.
Hacker News "Who's Hiring" (news.ycombinator.com, first of each month). High signal for engineering-led companies.
Wellfound. Startup-focused, mostly seed to series-C.
YC Work at a Startup. Filtered to YC-backed companies. Higher signal-to-noise.
Otta / Welcome to the Jungle. Curated, useful for European and remote-friendly roles.
Levels.fyi job board. Salary-data-aware listings.
GitHub Jobs is gone. Don't search for it; the board was retired in 2021.

The SWE interview funnel

The standard process across most companies large enough to have formal recruiting:

Recruiter screen (30-45 min). Logistics, motivation, level calibration. Be ready to articulate why this company, why this role, and what comp range you're targeting.
Initial technical phone interview (45-90 min). One coding problem (Medium difficulty typical), sometimes with a brief system-design discussion.
Onsite / virtual onsite (4-6 rounds, full day or split across days). Typical breakdown: 2-3 coding rounds, 1-2 system design (mid-level and up), 1 behavioral, sometimes 1 hiring-manager round.
Team match (varies). Some companies (Google, Meta) team-match after offer; others (Microsoft, most startups) interview you with the team directly.
Offer + negotiation (1-3 weeks). Negotiate. Always.

Time investment per company: 8-15 hours of interview time plus 20-40 hours of prep if you're not already sharp on coding fundamentals. Multiply by 5-10 companies for a real search.

Portfolio expectations

For SWE specifically, the portfolio is your GitHub. Three rules:

Pin your three best repos. Each should have a readable README explaining what it does, the stack, and what you'd do differently if rebuilding.
One shipped project beats three tutorial follow-alongs. Recruiters can tell. A small Chrome extension with 50 users says more than a generic todo app.
Open-source contributions are signal-positive but not required. One merged PR to a project people have heard of is great; trying to manufacture a contribution graph reads as inauthentic.

Resume specifics for SWE

Conventional, scannable, one-page (unless you're staff+ with 10+ years). Bullet pattern is action + thing + measurable impact: "Built a Redis-backed rate limiter handling 5K requests per second, replacing a Python service that maxed out at 800." Quantify when honest, skip when not. The Skills section should be what you can actually use under interview pressure, not aspirational.

Application strategy by career stage

New grad

Apply early (August-November for following year's start), apply broadly (200-500 roles across the season), lean on campus recruiting and university-relations programs at your top targets. The internship-to-return-offer pipeline is the single highest-conversion path to a new-grad role; if you have an internship offer in hand, prioritize that company\'s full-time process.

2-5 years experience

100-300 applications across an active search. Referrals matter more here than at new-grad level; spend time activating your network alongside the cold-application volume. Target a mix of mid-size companies (Stripe, Databricks tier) and FAANG, not exclusively one or the other.

Senior (5-10 years)

Fewer applications (50-150), more referrals, more inbound from recruiters if your LinkedIn is current. The funnel is narrower (senior roles are gated more carefully) but conversion per application is higher.

Staff+ (10+ years)

Mostly inbound and network-driven. Cold applications still work but the most productive time investment is reactivating your network. Engineering managers and skip-level engineering leaders at companies you'd want to work at are the people to talk to first.

Applying at volume without burning out

At 100-500 applications, the per-application friction is what makes or breaks the cadence. Each Greenhouse, Lever, or Workday form takes 5 to 10 minutes manually. Stretched across weeks of search, this is where most candidates lose momentum.

Lentra fills each form in about 20 seconds. Free, no quotas, drafts the essay questions from your real resume and profile. Built for exactly this volume problem.

Install Lentra

Free, takes one minute.