Candidate Experience in Deep Tech: What Senior Engineers Read About Your Culture Before the Offer

12.11.2026

Experienced candidates rarely argue with the hiring process – they simply stop replying. Even a late withdrawal usually traces back to something the candidate noticed several steps earlier, and most companies never find out what it was.

This is what candidate experience really measures: companies usually talk about culture with people who have already been hired: onboarding, values, ways of working. But in reality, candidates are introduced to it much earlier, during hiring, and what they see is often more accurate than any deliberate presentation.

In deep tech this gets even sharper. An ML researcher or an HFT developer usually has several processes running at once, so your process is compared with the others side by side. Every difference in speed, clarity or attitude counts as evidence about what it is like to work for you.

What Is Company Culture?

Company culture is the set of behaviours that decide how work gets done in a company: how people make decisions, what they treat as a priority, how they talk to each other, and how they handle mistakes and disagreement. It shows most clearly when nobody is checking.

Values are the part of culture a company writes down. The rest is visible only in behaviour.

There are generally three layers to any company culture:

Declared culture. What the company says about itself: values, career page, onboarding decks, founder talks.
Practiced culture. What happens day to day: how fast decisions get made, how disagreements end, how mistakes are handled, whose time counts.
Perceived culture. What an outsider concludes from the company’s behavior.

Companies put most of their effort into the first layer. Candidates cannot see the second directly, so they rely on the third: how fast you reply, whether interviews start on time, whether the interviewer has read the CV, and what happens after the last call. From these small facts, they infer what the company is like before they sign anything.

Company Culture in Deep Tech

Deep tech adds specific questions. Candidates look for signals about research autonomy, technical standards, how the team treats failed experiments, and whether engineers make decisions or take tickets. A values slide rarely answers these. A hiring process answers them whether you intend it to or not.

Work culture affects hiring in three ways:

It filters. A clear culture attracts people who work the way you do and repels those who do not.
It competes. For a senior engineer with several offers, compensation is often close, and the working environment carries more weight.
It travels. Candidates talk to each other, and in specialised fields the community is small.

Ilya Shvetsov reached the final culture-fit interview for an HR Director role at a startup. The call was set for 5:30 a.m. his time. Six people joined: both founders, a few C-level executives and HR. Every camera was off.

They opened with:

“We’re going to ask you a few questions to see whether you’re a good culture fit for us.” He answered: “Can I at least see you? Or am I the only one being evaluated here?” One of the founders turned her camera on, but she kept typing and glancing at another screen. He started on the first question, then stopped:

“Sorry, but I don’t think this is going to work. You’re trying to figure out whether I pass your culture fit but it looks like you didn’t pass mine.”

He thanked everyone and left. He explained:

“In a few minutes, I’d learned a lot about that company’s culture. How they treat someone else’s time. What their meetings look like. How present people actually are in a conversation. And, most of all, whether they see hiring as a mutual choice or an exam the candidate has to pass.”

None of this appears in a values document, and all of it is culture. In Ilya’s words: “Culture isn’t only what a company means to show. It’s also what a person manages to read from how it behaves.”

Culture Fit vs Culture Add

Culture fit and culture add are two ways to use culture in a hiring decision.

Medieval engraving of an interrogation on a wooden wheel, used as a meme about hiring interviews

Hiring Manager checking if the candidate has an "engineering mindset."

Culture fit asks whether a candidate’s values and way of working match how the team already operates. Used well, it protects what works. A team that reviews every change, documents its experiments and ships on a fixed rhythm will struggle with someone who works the opposite way.

Culture add asks what a candidate brings that the team does not have yet: another background, another method, another way of questioning a decision. The candidate still shares the values the team treats as non-negotiable.

Employer Branding

Employer branding is a set of deliberate actions that make a company more attractive to candidates. It covers what the company says, where it says it, and who says it.

It usually consists of:

The career page and job descriptions.
Technical content: engineering blog, talks, research papers, open-source work.
Employee voices: team members’ posts, conference appearances, reviews on public platforms.
Communication from recruiters and hiring managers.
The interview process itself.

Done well, it shortens the path to the right people: more relevant inbound applications, better reply rates to outreach, fewer withdrawals mid-process, and less pressure to compete on salary alone. It is also one of the tools of HR marketing, which applies marketing tools and methods to attract, retain, and develop employees.

Employer branding works with the first layer of culture, the one the company writes itself. Candidates check it against the third, the one they see in your behaviour. If a career page promises open communication but a candidate waits three weeks for feedback, the experience speaks louder than the promise. Employer branding holds only when the hiring process aligns with the principles being promoted.

Ways to Share Your Culture

There are several ways to share your company culture:

A culture page on your website. Collect testimonials and photos from the team, and ask employees for feedback so the page reads like people and not like copy. Link it from the career page so candidates actually reach it.
Job descriptions. Describe the work environment next to the tasks: how the team works, how decisions are made, what a normal week looks like. Present the role as a problem to solve, with the first year described, and not as a list of requirements.
Company profiles on job sites. Add a short culture description wherever the company has a profile, and keep it consistent with the website.
Interviews. The hiring manager explains how the team works, and team members join the conversation so candidates meet the people they would work with. A candidate who meets only HR judges the company by HR.
Social media and technical content. Team members share posts, talks, engineering write-ups and photos from work. Employee voices carry more weight than company announcements.
Process communication. Name the stages, the timing, the people involved and the feedback deadlines in the first message. Share the compensation range early.

Candidate Experience: The Hiring Process as a Demo

Candidate experience is everything a person goes through between first contact and the final decision: messages, scheduling, interviews, tasks, feedback and the offer, including the gaps between them.

Ilya puts the idea in one line: “The hiring process is essentially a demo version of the company.”

The data points the same way:

According to Greenhouse, 9 in 10 candidates expect the hiring process to reveal a company’s culture and values.
CareerBuilder research, cited by Spark Hire, found that nearly 70% of candidates judge how they will be treated as an employee by their experience in the hiring process. In CareerBuilder’s 2017 Candidate Experience Study, 78% said the candidate experience indicates how a company values its people.
In Monster’s Job Search Deal-Breakers Report, 57% of job seekers said a poor interview experience would make them withdraw, and 56% said an unclear or constantly changing hiring process would make them exit.

This works even in the most ordinary events:

Interviews keep getting rescheduled: they draw conclusions about how you plan.
The role is described differently at different stages: about how you align internally.
A week passes with no feedback: about how you make decisions.
Three more interviews appear at the final stage: about how far your early agreements can be trusted.

Ilya adds: “Maybe every one of these has a perfectly reasonable explanation. The problem is that the candidate doesn’t know it. So they fill in the gaps themselves.”

Candidates Interview You, Too

Interviewing is always a two-way street. In deep tech, specialized talent isn't short on options. Persuading a candidate to take an initial call is easy – giving them a reason to stick around for round two is the real challenge.

When top candidates drop out, they rarely complain; they just disengage. Candidate ghosting isn't an applicant problem, it's usually a reaction to a red flag in your hiring flow. As National Search Group highlights, experienced candidates disengage quietly, meaning late-stage dropouts are rarely random. Because candidate funnels register silence rather than feedback, the real problem stays hidden.

Three Real-Life Cases

We at Lucky Hunter hire technical specialists for AI and deep tech companies every day, and we see situations like these regularly. In each of the three cases below, the company had a reason for what it did. The candidate could not see the reason.

Case 1: Opening Below Market

A company opened with an offer below market rate, planning to negotiate upward: a standard negotiation tactic on their end. To the candidate, it looked like an evaluation of his worth: "If I have to fight for fair pay before day one, what happens during my first salary review?" He withdrew immediately, even though the company was fully prepared to match his market rate.

A negotiation tactic only works when both sides recognise it as one. Otherwise, your opening number is simply a statement about how much you value the role.

Case 2: An Undefined Role and a Disconnected Test Task

A startup sent a generic technical task while still defining the role's scope internally. Early-stage teams often let the position take shape during the search. Candidates don't see that internal context, they just evaluate the startup by the unrelated test task, assume the internal operations are equally disorganised, and disengage before learning the actual technical challenges are complex and relevant.

Candidates accept uncertainty when you name it. They disengage when forced to guess.

Case 3: A Comparison in the Final Stage

A final-stage offer fell apart after the candidate casually compared the company's title to a competitor's product. Inside the company, the founder required deep product ownership – a legitimate requirement for a core team member. But to the candidate, the rejection felt arbitrary because the requirement was never stated during the process. He only learned about the dealbreaker after failing it.

A hiring criterion that exists only in the founder's head cannot be met intentionally. If a requirement dictates the hire, state it early in the pipeline.

What the Cases Have in Common

None of these companies acted in bad faith, and none of the candidates were being unreasonable. The founders had valid internal logic: a negotiation strategy, an evolving role, an unspoken cultural bar. None of that logic reached the candidate.

When a company leaves its reasoning unstated, candidates fill in the blanks themselves, and they usually assume the worst.

This friction points to a missing element in the process: hiring-market fit. This is the state where role scope, compensation, seniority, assessment steps, and market expectations align and the candidate can clearly see how.

Closing that gap does not require changing your standards or over-promising. It simply requires stating your logic out loud before the candidate is forced to guess.

Auditing Your Process

Go through your hiring process as a person who knows nothing about what happens inside the company. At each point, ask what that person concludes. Each stage below is also a place where candidates spot hiring process red flags.

The First Message

The first message shows whether the sender knows the role, the team’s problem, the compensation range and the stages ahead. A template tells a specialist that they are one of many. A message that names the problem and the reason this person was approached says the company knows what it is doing.

The message usually comes from a recruiter, which makes the recruiter the first representative of your culture. This applies to internal recruiters and to agencies equally.

At Lucky Hunter, we build searches around business context, not job description. This lets us present your company to candidates with precision.

Our recent case study shows how built-up context helped us fill a complex role of an AI Researcher for a long-term client 42.

Audit question: could any company have sent this message to any engineer?

The Interview with the Future Manager

This is where candidates decide whether the process is a mutual choice or an exam. They read preparation, attention and whether the interviewer can discuss the real technical problem. They also read how much time is left for their own questions.

Audit question: after the conversation, did the candidate feel like a peer or a subject of evaluation?

The Test Task

A test task is a small version of the job. Candidates ask three things: how long will it take, does it resemble the real work, and will someone read it. A task that is far from the role leads them to conclusions about the role. A task with no time limit or criteria leads them to conclusions about respect for their time.

Audit question: can you state in one sentence why this task exists and who evaluates it?

The Feedback

A week without feedback looks like a scheduling issue from inside. From outside it looks like a statement about how decisions are made. Seasoned candidates fill the gap quickly, because other processes are running. A short message with the date of the next update prevents most of it.

Audit question: after a week of silence, what explanation will the candidate invent?

The Offer

The offer turns every earlier impression into a number. Elemed calls an offer that arrives below what was discussed a breach of trust: the candidate feels deceived, loses trust in the employer and is likely to reject it. Elemed’s advice is to state the budget during the interview stage. A withdrawn offer costs more. Axios quotes a recruiting expert warning that revoked offers damage the employer brand long-term and erode trust with candidates and current employees.

Audit question: does the number match what the candidate heard in the first conversation?

One more question applies to the whole process: what is obvious to your team and has never been said to a candidate?

How to Improve Candidate Experience: Do and Don’t

Do’s

Align internally before the search starts. Agree on the role, budget, seniority and decision-makers. Candidates find the gaps you left.
State the range at first contact. It saves time on both sides and shows that you know the market.
Explain why each stage exists. A test task or an extra interview with a stated purpose reads as a method. Without one it reads as friction.
Set a feedback deadline and keep it. “No decision yet, next update on Thursday” beats silence.
Show who decides and on what criteria.
State non-negotiables early. If commitment to the product, on-site presence or a specific way of working is required, say it in the first conversations.
Close every process in writing, rejections included. In specialized fields the same people meet again.

Don’t’s:

Open below market in expectation of negotiation. Candidates read it as a signal about budget, market knowledge or attitude to people.
Add stages at the final step. Unexpected extra interviews tell candidates that early agreements cannot be trusted.
Assign test tasks unrelated to the role. Connect the task to real work or explain why it differs.
Go silent after interviews. The gap gets filled with the worst interpretation.
Withdraw an offer. If something changes internally, say so directly and as early as possible.
Treat culture fit as similarity. Test for working style and values you can name, not for resemblance to the current team.
Describe a different role in each conversation. It shows that the company has not decided what it needs.

Conclusion

Hiring is always a two-way street. The less a candidate is forced to guess your internal logic, the higher your chances of guiding top specialists from that initial message to an accepted offer.

At Lucky Hunter, we work with deep tech companies to source talent for complex technical roles. Reach out to calibrate your hiring.

FAQ

Share

Alexandra Godunova

Content Manager in Lucky Hunter

Сontact us — we fill even the most complex and rare IT positions!

We deliver
while others search!

Contact