Hiring DFT engineers in Poland starts with the work your project needs done. Technical experience is one requirement. Interest in moving, location and the way your company makes decisions determine which conversations can progress to an offer.
Define which part of DFT the new engineer will own
DFT means Design for Test: building testability into an integrated circuit. For recruitment, the acronym alone tells you very little. Do you need someone to define the approach, implement test structures, generate patterns or investigate a problem found when testing the chip?
The tool vendors' documentation helps explain the distinction. Synopsys TestMAX DFT addresses DFT implementation, while TestMAX ATPG generates test patterns. Siemens Tessent MemoryBIST covers testing and diagnosis of embedded memories. These illustrate different areas of work, rather than a mandatory tool list for every candidate.
When hiring DFT engineers with ATPG and scan experience, specify what they must deliver in your project. Scan-chain implementation, fault-coverage analysis and memory-test integration each call for specific skills and practical experience. “Has used Tessent” does not establish the scope of that experience or how independently the person can work.
If this is your first DFT hire, also establish who can review their decisions. Hiring someone to define the test approach independently differs from adding an engineer to an established flow under an experienced lead. Our article on stalled FPGA and ASIC searches explores the related problem of combining too much into one role.
We recommend assessing technical competence before moving on to “cultural fit”. With such a small candidate pool, an early judgement based on impressions can rule out people before you have established what they can do.
A list of names is not a pool of interested candidates
In one assignment described by our recruiter, the potential pool matching the search assumptions was approximately 30–50 people. That is an observation from a particular search, not a count of all DFT engineers in Poland. Nor does it mean that all those people were open to moving.
To understand who you could hire in Poland, map experience alongside availability. Who has worked in the required area, and at what level? Who has been contacted? Who is interested, and on which terms? Keep unanswered outreach separate from a refusal, and unwillingness to relocate separate from a skills gap.
Record the main reason each person leaves the process. If location excludes otherwise suitable engineers, repeating the same search will not fix it. If the people contacted lack the required independence, revisit how profiles are selected before increasing message volume.
High expectations need a concrete offer
Our headhunter noted high expectations on both sides: the client wanted a very strong profile, while candidates had conditions of their own. An interesting technology story may not be enough to start a conversation. Decide in advance how you can respond to those expectations; you may not get a second opportunity to interest the same person.
Before asking someone to commit to several interview stages, explain the responsibilities, available support, working arrangements and compensation budget. An experienced engineer needs to know whether they will develop new solutions or mainly take over a backlog, and who makes the technical decisions. Do not sell architectural influence if the job is to execute an approach already agreed elsewhere.
Search reporting should identify which expectations prevent candidates from entering the process. Compensation, scope and commuting objections call for different decisions from the people managing the search. Without that detail, it is easy to conclude that “candidates expect too much” or “we are asking for too much”, without identifying what needs to change.
Hiring DFT engineers without relocation
Candidates in the assignment described here were unwilling to relocate. That should prompt a review of why the job needs to be in one location, rather than another attempt to persuade people to move.
Break the need for on-site attendance down into specific tasks, such as laboratory access, work with physical silicon, test bring-up or coordination with colleagues. Separate those from work that could use approved remote access to tools and design data. You may find that hybrid work is feasible, or that the office requirement reflects company habit rather than the work itself.
If attendance is only needed at particular stages, consider agreed visits instead of a permanent move. If daily presence is essential, say so from the start and assess whether the local pool and offer support the search. Map the talent available in that location before committing to a hiring plan. In a narrow specialism, assumptions about availability can be expensive; market mapping helps you test them before they become commitments.
“Hybrid to be discussed” is unhelpful if it turns out to mean four days a week in the office at the final stage.
Is your DFT search stuck with too few candidates?
In a 30-minute conversation, we can review the required experience, location constraints and feedback that would help you decide what to change.
Book a 30-minute callHow to assess a DFT engineer and consider growth potential
Flexibility starts with identifying what can be learned after joining. Someone with relevant scan and ATPG experience in a different tool needs a different assessment from someone with no practical DFT experience. Design verification may provide a foundation for development, but it does not by itself demonstrate readiness to own DFT independently.
Ask about a specific problem rather than relying on years of experience. What failed? Which reports did the candidate examine? What did they change personally, and how did they check the result? OPM's structured interview guidance describes assessment through past experience and hypothetical situations, using common questions and criteria. The technical questions themselves should be prepared by someone qualified to assess the relevant work.
A hypothetical exercise: fault coverage from ATPG drops after a design change. What information would the candidate request, what would they check first and whom would they involve? Assess their diagnosis and reasoning. Do not ask for a previous employer's code or documentation.
If you consider someone with potential, establish who will support them, which tasks they can take on immediately and when you will review readiness for greater independence. A tight tape-out schedule does not leave room to assume that missing experience will resolve itself. It is still worth checking whether every requirement really is essential on day one.
For a senior DFT hire, be explicit about what must already be proven. For a development hire, make the learning plan equally explicit. Calling both profiles “senior” to fit the same vacancy only postpones the disagreement.
Several interviewers, clear responsibility for the decision
DFT involves technical coordination across teams, but recruitment need not become an open-ended sequence of interviews. One of our searches involved several decision-makers and delayed client responses. With few candidates available, this is a process issue worth addressing directly.
Before interviews begin, agree who assesses DFT competence, who assesses collaboration and who approves the offer. Each stage should answer a distinct question. If another interviewer wants to repeat an assessment, identify which evidence is still missing. You may find that one of the stages is unnecessary.
Reserve time for the hiring discussion and agree when feedback will be given. If a decision slips, tell the candidate why and when they will hear back. Assess the engineer's communication through practical examples too: explaining a problem to a designer, raising a risk and agreeing action when priorities conflict.
In a small professional network, assume that news of a search may travel beyond the people you approach. AESC's professional standards include protecting confidential client and candidate information. Agree who receives profiles and what can be shared about the project. Avoid circulating details that are unnecessary to establish interest. Careless outreach can damage trust across a small market and make people less willing to engage.
Change the search based on what conversations reveal
Useful reporting on a DFT search should lead to decisions:
- Suitable engineers decline relocation: review the working model or search geography.
- Tool experience keeps excluding candidates: establish whether that particular platform is essential from day one.
- Compensation expectations repeatedly exceed the budget: compare the budget with the scope and independence required.
- Candidates are waiting for assessment: improve decisions before increasing outreach.
Which requirement excludes the most suitable people? What would changing it make possible? Who can approve that change? If the report cannot answer these questions, ask for reasons behind withdrawals and rejections, not just the number of CVs submitted.
Direct search for DFT engineers is useful when you need to identify a specific group and reach people who are not applying, or whose relevant experience is not immediately obvious from their profiles. Our article on reaching passive candidates explains that work. A different outreach method cannot, on its own, resolve requirements the market will not meet. Hiring DFT engineers in Poland calls for informed choices about what can change — and a timely decision when a suitable person engages.