跪拜 Guibai
← Back to the summary

505 Chats to 8 Offers: A 6-Week Java Job Hunt in the AI Era

Java is Dead? First Job Hop: 505 Boss Chats, 8 Offers in 6 Weeks

Java backend social recruitment first job hop success, let's talk about some questions everyone cares about.

505 Boss interactions, 8 offers, battle over in less than 2 months. Did not apply to AI positions, only backend.

My Record

From mid-August to satisfied exit: 6-week timeline

Started preparing projects + eight-part trivia + algorithms in June.

Mid-August, T started sending first resume (T is a particular day).

T+5 days: small companies started scheduling interviews. First social recruitment interview, no feeling at the time, most failed at first round.

T+2 weeks: first satisfactory offer (small foreign company), submitted resignation, last day after National Day.

T+2 weeks+2 days: started applying to big tech internet companies.

T+3 weeks: big tech started scheduling interviews, still nervous, plus some on-site coding nervousness, failed at big tech.

Pressed pause, did not submit for a week, continued advancing current other processes, supplemented relevant knowledge and skills.

T+5 weeks: resumed applying to big tech, big tech processes advanced, started entering second and third rounds. Due to approaching last day, kept pushing processes.

T+6 weeks: got one or two big tech offers, satisfied exit. Some big tech still in process, only sent offers after joining the new company. Couldn't wait any longer, keeping warm...

In less than 2 months, social recruitment ended. Recalling campus recruitment from June to December was painful; social recruitment reduced the pain time significantly.

505→115→22→8: My Conversion Funnel

Used only Boss, no other recruitment software.

Boss interactions: 505

[image]

Resume exchange: 115. Interaction to resume submission: 115/505 = 22.7%

First-round interviews: 22 (12 failed). Resume submission to first-round interview: 22/115 = 19.1%

Second-round interviews: 10 (2 failed). First-round to second-round: 10/22 = 45.5%

Third-round interviews: 5 (some have no third round, none failed).

HR interviews: 8. Second/third-round to HR: 8/10 = 80%

All who reached HR got final offer calls.

Interaction to offer conversion rate: 8/505 = 1.6%

[image]

How did I prepare for interviews?

Now with AI, preparing for interviews is extremely easy.

Write your resume well, throw it to AI, let it generate questions for you. Answer each one, then have it evaluate and give suggestions. Document every question, output an interview question bank. For repeated questions, have it combine them into one. For understanding gaps, keep correcting.

I used Codex, directly using speech-to-text or direct voice chat.

Before starting, you can create a skill, codify your planned steps into a skill, and follow it through the rest of the process.

Of course, this is more about project experience interviews, i.e., interviews based on your resume content.

For algorithm questions, just practice LeetCode Hot 100; they hit most of them.

Any regrets?

Yes, some well-known companies never even offered an interview.

Social Recruitment Related

Best time to switch jobs

Work experience under 5 years, preferably ≤3. Avoid making it 3 years with 2 jumps or 5 years with 3 jumps.

High-level switch: within 6 months of promotion/raise/high performance/high year-end bonus, leave from a high point. Ethically a bit low, but if you are loyal to your boss, will your boss trust you?

Timing: avoid mid-year. Generally it's "Golden 3, Silver 4" (March-April), most people leave after getting year-end bonus, then headcount opens. Or September-December, when headcount is also reviewed. But the positions might be similar to campus recruitment. If you get an interview, the chance of offer call is higher because few people move at this time.

Turning point: once you feel you're about to be the scapegoat, don't think, you probably are. Start writing your resume, try to leave before the next performance review. If you already took the blame, leave before the payroll report comes out.

How to schedule interviews while employed? I had 6 interviews in one day

First, clarify your goal: is it just to casually interview, or must you leave?

If you want to leave from a high point, casually interviewing, don't take more than 3 per week, otherwise it's easy to be discovered. Schedule for 8-10 and 20-23, non-working times.

If you must leave, then that's the priority. Nothing else matters; focus on getting an offer. Schedule interviews at least 3 days in advance, otherwise it might be hard to book a meeting room. Coding interviews need a meeting room because you need a computer. Some interviews without coding can be done on the phone; just find a quiet place near the company.

Start with small companies; most don't have coding tests and interviews are under 40 minutes. Once well-prepared, start scheduling aggressively. If you have more than 4 interviews, consider taking a day off.

How to pack a full day: book 3-4 big tech companies for morning, noon, and evening; their interviewers are busy, so times are uncertain. Then fill gaps with small/medium companies. If a big tech interview exceeds one hour, say you have another meeting and end it quickly; don't waste time. (Not fully tried, but theoretically feasible.)

Best interview time slots (not tried, theoretical):

Challenge: 6 online interviews in one day. Took a day off specifically. Earlier, when scheduling, packed them together.

After 4 interviews, I felt physically drained. The prolonged tension and stress is exhausting.

Online or offline? How?

After the interview, how to judge if you passed?

If you think you probably passed, you might still fail. But if you think you probably didn't pass, you basically won't. Even if you get lucky, you'll fail later in horizontal comparison.

Objective signs of failure:

My feeling: once you pass the second round, the rest is stable. The second round is usually your future +1 manager. If that person wants you, you're good. Many third-round director interviews are just chats, asking how you did things, how you designed them, not drilling into details.

Does a failed interview record follow you? ByteDance/Alibaba/Didi test

Most have a "resurrection round" and interview feedback has little impact. Most feedback stays within a large department; if you switch departments, they can't see it.

ByteDance: unlimited resurrection, but cannot run two processes simultaneously.

Didi: unlimited resurrection, but cannot run two processes simultaneously.

Alibaba: unlimited resurrection, can run multiple business units simultaneously.

How to push the process: Make HR more anxious than you?

Already resigned: directly say you mentioned leaving verbally a few months ago, submitted in system last month, last day is basically fixed.

Start date: directly ask the fastest onboarding time. Say you won't travel, go directly for seamless transition, show you can start immediately.

Give HR the illusion that if they offer, you won't back out: your backup offer's HR is pushing hard, start date is fixed, but our platform/business is better, so you prioritize here; once an offer is given, you'll definitely come.

Frequency: best to push every 2-5 working days. If you're anxious without an offer, first interview at small companies with fast processes. Big tech taking a week to give an answer is normal, and they like to rank candidates: they give high offers to those they want, drag average ones, and give a low offer when they can't hold them anymore. The best time to push is when you're about to leave but not yet, because then HR is anxious, afraid of missing a good candidate.

How to resign?

  1. Pre-resignation preparation:

In the current environment, a long gap is not recommended. Of course, some colleagues took 3-6 month gaps and still landed big tech offers, even those who just quit to rest got 25%+ raises upon joining. Those are exceptions, usually requiring high vertical domain match (high match means less competition).

  1. Tell your TL verbally: suggest 1-2 weeks before the legal one-month notice. Saying it early doesn't mean you stop working. After telling your TL, you can spread the news so that demand side won't push for progress out of embarrassment.

  2. Submit the formal one-month notice in the system: formally start the resignation countdown. Now you can slack off openly, start the handover group, and for tasks say you'll review with the handover person, but actually only reply to messages and don't do work (intense interview phase).

  3. Clean up and leave: company physical exam, use all benefits. Be aware that security software on your computer may be heavily monitoring file transfers, sending files, and downloading knowledge base content.

Reasons for resignation:

Salary negotiation: Big tech caps at 30%, but every detail is negotiable

Take more, negotiate with confidence.

Don't worry about fighting it out; apply to multiple companies of the same type. Going all-in on one makes you a clown.

Before the offer is given, respond that any increase is fine (e.g., 10-20% increase is enough), mainly because you like their business, flatter them.

After the offer comes out, if others haven't come yet, wait a bit. Once they come, directly state what other companies are offering, but their business is problematic, devalue them.

Once the offer is down, it's basically locked.

Before the offer is down, you can negotiate:

Increase cap:

Age considerations:

I used to think job hops were always 30%+ increases, but when I started playing the offer game, no one offered above 30%.

Speaking of which, let me praise AI: many AI-direction offers are 50%+ increase, even doubling is common (envious; backend is still too saturated).

How to keep offers warm?

To-be-or-not: once the process reaches later stages, go slow. First and second rounds should be quicker; third round and beyond can be delayed, e.g., saying you have a handover this week, a sudden family trip, or a closed-door development sprint.

After the interview, proactively pull:

Delay start date:

These usually can't delay more than 2 months.

Before or after joining, you can keep several companies warm: don't think that just because you've passed HR interviews you're locked in. Cases of withdrawing after collecting payroll records, or backing out of verbal/written offers, are everywhere. Big tech might be better, small companies are disaster areas.

Sometimes both sides are keeping each other warm: maybe 1 headcount, the process is all done but they don't advance, likely waiting for a previous candidate to join; only when that person leaves will they move you forward.

Joining also has potential pitfalls. If there's a trap, you can quickly leave for the next place, so keeping warm broadly is right.

Regarding social security: most likely they won't check, and if they do they won't ask for screenshots. Just make sure you don't join the next company in the same month you paid it; you can't pay twice in one month.

But with broad keeping warm, don't tell the company the day before you're supposed to join; that'll get you blacklisted as an integrity issue.

Interview Related

Java dead? Are there still pure Java jobs?

My feeling is yes, and there are still many positions, given the sheer volume of Java backend services. But after AI came out, the number has visibly shrunk, which is also true.

Due to business, I had no AI Agent implementation experience at my original company. My resume had no AI-related projects, so I targeted pure backend directions. This included Java and golang, mostly Java, a few Go.

AI questions I encountered:

Just be honest about your implementation experience, but expand a bit: say what you've done and your understanding.

Interview Process

  1. Early simple communication: usually a recruiter or HR checks interest, fit, and reason for leaving. Once satisfied, schedule technical interview.
  2. First round: usually a senior in the team. If suitable, advance. At small companies, it's likely your future team lead. This round focuses more on fundamentals, coding, 408, project, and eight-part trivia are all asked.
  3. Second round: usually your direct manager. Whether you pass depends largely on them. Usually also has coding, but mostly project-based, asking your approach and eight-part abilities.
  4. Third round: big boss, usually department director, your +2. For a regular engineer, this round usually has no coding. It's about personality, expression, whether you can explain something clearly, because the boss is largely detached from frontline tech. Being able to impress them matters.
  5. Fourth round (most don't have it): some add one. This is the head of the large department or a CTO at small/medium companies. Purely about thought process. Only a certain Universe Factory gave me an extra round.
  6. HR round: communication about personality, e.g., strengths and weaknesses, plans for city and work, future outlook, the usual. You can check my earlier articles.

Reasons for failing first, second, or third round

First: usually team lead or senior. Fail usually means mismatch or weak fundamentals.

Second: likely direct manager, the most decisive person. Fail means your manager doesn't want you.

Third: usually +2. This round is largely about personality, or from the boss's perspective whether you fit. Usually doesn't fail.

Fourth and above (if any): could be cross-functional, +3. If it's an SSP cross-functional, you might still fail; if it's +3, it's similar to +2, mostly chat.

HR round: unless there's a psychological issue, generally doesn't fail.

No offer after HR round isn't because you failed the interview, but because you were cut in horizontal comparison: someone with better cost-effectiveness was chosen.

Do social recruitment interviews still have coding tests in 2026?

Small companies generally don't.

Big tech have too many candidates and need filters, so they do coding tests. Most are in an editor with no hints.

Even if everyone uses AI coding and 95%+ of code is AI-written, to get into big tech you still need to code on the spot. Building rockets or tightening screws: the interpretation is in the company's hands.

Moreover, many companies now require AI coding to deliver entire projects directly. Alibaba might have 1/3 of projects as AI-coded. Is that harder than on-the-spot coding? I haven't experienced it.

Better to switch jobs while it's still in the coding-test stage. In the future, you won't even know why you failed if it's AI coding.

However, if a social recruit gets a hard problem, that's just harassment, an excuse to fail you. If you haven't practiced it, just end the interview. Even if you solve it, it's often a waste of time. Many who give hard problems will likely fail you even if you AC.

What is asked in the first round?

Self-introduction: keep it under 3 minutes, giving the interviewer time to read your resume. The content doesn't matter much; just clearly state the platform and what you did.

Coding: although everyone uses AI now, most big tech still have it, usually easy/medium difficulty, and often original problems.

Project: usually based on what's on your resume. If it's a vertical domain, they'll ask more, mostly how you did it and why. If not, they ask based on the interviewer's knowledge.

Whether it's a vertical domain aside, being able to explain something from background to solution to results is key. Background is crucial for telling a good story. Why did you do it? What would happen if you didn't? What benefits or metrics improved?

Eight-part trivia: if not vertical domain, they ask a lot: Java basics, concurrency, GC, 408 basics, databases, middleware, high availability, high concurrency.

Reverse questions: when the interview hits 50 minutes, there are a few minutes for you to ask. Ask about the team's work and future plans, and show your interest level.

Why did you leave?

Note: each point must be said with confidence, especially the last one; basically once you say it, you're stable.

What to ask in the reverse question slot?

Interviews usually have a 5-10 minute reverse question segment.

Company's emphasis on the department: e.g., ask how long this area will be pursued? Try to get the interviewer to reveal if it's a whim or long-term. If there's horse racing, pay attention: departments can easily be merged or dissolved, and then you might as well have switched.

Expectations for new hires: infer the landing difficulty, guess if it's broad hiring or specific matching. For example, most of my business directions weren't a great match, which basically meant broad hiring. In a batch, there might be 2-3 headcounts, which also avoids one person becoming the scapegoat.

Start date: can it be seamless? Reduce your own uncertainty.

Finally, express your long-term commitment. Most companies want candidates to stay at least 2-3 years. (My girlfriend/wife is in this city, family is here, plan long-term development, etc.)

In Closing

Java Devs: Don't Panic Yet

After going through 505 → 8, the biggest feeling is: the market isn't dead, there are still many opportunities.

How Big Is the AI Impact?

The impact is real, no self-comfort:

But I judge the upper limit of the impact is "efficiency rewrites job slots," not "eliminates the profession." Code production has become cheaper. What's valuable is judging whether code is correct, whether systems can hold up, and who takes the blame when things go wrong. In my understanding, that's still backend's home turf.

So for ordinary backend devs, my advice isn't to force a switch to algorithms or Agents. Become an expert in your vertical domain plus someone who uses AI to boost efficiency; the premium is actually more stable.

The wind keeps blowing, and those who can swim aren't afraid of cold water. Keep going, everyone.