Recruiting a Platform Performance Engineer for Shoper: FFS Case Study (Direct Search)

Source: Fast Forward Solutions (FFS), Direct Search project case study from 2026. Updated: November 2026.

Author: Tomasz Bożyczko, founder of Fast Forward Solutions

The short answer

Fast Forward Solutions (FFS), a boutique Direct Search and Executive Search agency based in Warsaw and Gdańsk, conducted a recruitment process for Shoper (the cyber_Folks group) to fill the position of Platform Performance Engineer: a specialist in the performance of a large e-commerce platform, for a role created from scratch. Active sourcing lasted about a month (until early November 2026); 443 candidates were identified for the assignment, 6 candidates were interviewed by FFS, and 3 advanced to interviews with the client.

The hardest part was finding candidates: there aren’t many companies in Poland on a scale similar to Shopera’s, and the people who work there rarely provided detailed descriptions of their work on their LinkedIn profiles. That’s why FFS searched for evidence of work on that scale (descriptions of problems, specific companies, and cities) rather than for keywords.

Performance Engineer recruitment funnel for Shoper: 443 candidates in the process, 6 interviews with FFS, and 3 interviews with the client

Key Facts About the Project

  • The client was Shoper, part of the cyber_Folks group, and the contractor was Fast Forward Solutions, working under a Direct Search model.
  • The Platform Performance Engineer position was created from scratch: its goal is to build a performance testing environment and diagnose bottlenecks on a large e-commerce platform.
  • Active sourcing lasted about a month, until early November 2026.
  • The assignment involved 443 people, of whom 6 (about 1.4%) were interviewed by FFS, 4 candidates were presented to the client, and 3 (about 0.7%) went on to interviews with the client.
  • Of the 178 people, 51 responded to the first message, or about 29%.
  • 19 people applied on their own, but almost none of them met the requirements, so the job posting did not generate any candidates.
  • The main reason for the difficulties was that there were few companies in Poland with platforms of a similar scale, and candidates who were not visible on LinkedIn rarely provided detailed descriptions of their work.
  • The top candidate possessed two of the three key qualities required for the role, and the client felt that the third could be addressed with the help of the team.

What did the assignment entail?

The Platform Performance Engineer is a role being created from scratch. Its goal is to build an environment for performance testing, detect regressions, and identify areas for improvement in the live platform for the team.

ElementDescription
KlientShoper, part of the cyber_Folks group
RolePlatform Performance Engineer, a position being created from scratch
Scope of the RoleSetting up a performance testing environment and identifying bottlenecks on a large e-commerce platform
Artist and ModelFast Forward Solutions (FFS), Direct Search
TimeActive sourcing lasted about a month, until early November 2026

Why was it difficult to recruit a performance engineer?

The role combines three rare skills, and people who possess them are rarely visible on professional profiles.

  • Three skills at once: reading large, legacy code, diagnosing performance issues on a large scale, and building a test environment from scratch. It’s rare for a single person to demonstrate all three publicly; usually, it’s two out of the three.
  • Scale as a filter. We looked for companies on a similar scale to Shopera, and there aren't many of them in Poland. The rest are mostly standalone apps or software development firms.
  • Candidates who aren't visible on LinkedIn. People working at this scale rarely describe their jobs in detail on their profiles. A brief profile listing only the job title doesn't reveal that someone is diagnosing the performance of a large platform, so a standard keyword search wouldn't turn them up.
  • A role with no established template. The position was created from scratch, so the job description was refined as the project progressed, and each new direction required revising the lists of candidates, questions, and reports.
  • Resumes vs. Reality. Two candidates had the right keywords and tools, but were eliminated during the interview because they failed to demonstrate a diagnostic method or a scale.

How did FFS find candidates? A six-step method

1

Brief and Strict Criteria

From the brief, we identified non-negotiable criteria (key technology, the ability to diagnose issues at the application and infrastructure levels, scale, and working methods) as well as exclusion criteria, including companies within the client’s group.

2

Sourcing Package

Target companies across three levels, Boolean searches (LinkedIn Recruiter and Google X-ray), AI-powered evaluation criteria, and a multi-channel outreach plan: email, InMail, and SMS.

3

Evidence-Based Sourcing

Since the target candidates worked at only a handful of Polish companies with similarly large platforms and didn’t post much about their work on LinkedIn, simply searching by keywords wasn’t enough. We ran multiple series of AI searches by city and key phrases (e.g., “reduced latency,” “bottleneck,” “high load”), by companies of a similar scale, and by role: developers, performance testers, and L3 support.

4

Contact and Screening

Messages in several versions, reminders after 2–3 days, a survey with questions about the platform’s technology, databases, performance and scalability tests, and a CV evaluation on a scale of 1–5.

5

Preparing for Interviews

We conducted the verification interviews according to a set script with evaluation criteria, and for each candidate, we prepared a memo containing an evaluation and questions for the interview with the client.

6

Iterations Following Customer Feedback

After each conversation with a client, we adjusted the profile, questions, and screening criteria so that subsequent candidates would better align with what the client was actually evaluating.

What were the project's figures?

StageNumberHow to Read This
People in the order443373 candidates sourced through active sourcing and 19 self-submitted applications; the rest are in the campaign, screening, and interview stages
Sourcing Profiles363Profiles evaluated and organized in the sourcing tool
First message178 peoplePeople to whom we sent the first message (in several versions, with reminders after 2–3 days)
Answers51 people (about 29%)36 in interviews, 14 in the screening process, 1 in a conversation with a client
FFS Talks6 people (about 1.4% of the order)Follow-up interview after an initial screening via a questionnaire on platform technology, databases, performance tests, and scale
Presented to the client4 candidatesWith a note containing each candidate's evaluation
Conversations with the client3 people (about 0.7% of the order)After each interview, we changed the profile and the questions

Data from our recruitment system and sourcing tool, as of November 5, 2026. The percentages for the project represent the proportion of candidates at each stage out of the 443 candidates in the project.

What recruitment guidelines for specialized technical roles result from this project?

  1. Look for evidence of work at scale, not just keywords. For narrow technical roles, the names of tools listed on a resume don’t mean much; it’s the diagnostic approach and evidence of scale that determine a good fit. This conclusion came up twice in client feedback.
  2. Look for companies of a comparable size. There aren't many such companies in Poland, but that's where you'll find people with the right experience. Software houses and agencies were a less reliable source for this project.
  3. An empty profile does not mean a lack of competence. The candidates we were looking for rarely provided detailed descriptions of their work on LinkedIn, so we looked for evidence in their descriptions of problems, in specific companies, and in specific cities—rather than in the content of the profile itself.
  4. Conduct a quick pre-screen on the scale and methodology. A few questions about the scale and a scenario like “one of the platform’s many clients is having a performance issue, while the rest are working fine” will weed out candidates who use the right keywords but lack a methodology, saving the client time.
  5. Confirm priorities and the budget before launching a broad outreach campaign. With a limited budget, it’s worth establishing the order of priorities (scale, current technology, environment development) and a realistic budget for that scale from the outset.
  6. Don't count on the job posting. Of the 19 people who applied on their own, almost none met the requirements, and some didn't understand a key technical requirement.

How did the role's profile change over the course of the project?

The job description became more specific as we had further discussions with the client, which is normal when creating a role from scratch.

  1. Start: developers with the ability to troubleshoot issues at both the application and infrastructure levels.
  2. Expansion: adding senior performance testers (client's decision).
  3. After the first interview with a client: a deep understanding of the platform's technology and the ability to set up a test environment—testers who lack these skills are eliminated.
  4. After the second conversation: the scope and method of diagnosis are more important than the names of tools and keywords.
  5. Finally: clarifying the scope, with an emphasis on tool development and diagnosis, and infrastructure as a complementary element.

What was the outcome of the project?

Three candidates, selected from the 443 people listed in the job posting, were invited for interviews with the client. The top candidate possessed two of the three key qualities required for the role, and the client believed the third could be addressed with the help of the team.

When Does Direct Search Make Sense for Technical Roles?

Direct Search—that is, actively reaching out to candidates who aren't looking for a job—works well when a position is rare and the right candidates aren't posting job listings or describing their work online.

  • The profile is very narrow and combines several rare skills.
  • Candidates work at a small number of companies of a certain size.
  • Job postings mainly attract people who don't meet the requirements.
  • This is a new role, and the job description needs to be refined in consultation with the client.

At FFS Direct Search, the fee ranges from 12–16% of annual salary for specialist roles and 15–18% for managerial roles; the first vetted candidates are presented to the client within 10–14 days, and the guarantee lasts 90 days. An alternative is the Shortlist option for a fixed fee. Details: How much does recruitment cost in Poland?

About Fast Forward Solutions

Fast Forward Solutions (FFS) is a boutique Direct Search and Executive Search agency with offices in Warsaw and Gdańsk, registered in the National Register of Employment Agencies, and operating as a company since 2017. FFS recruits leaders and specialists in eight areas (sales, marketing, IT and engineering, product, e-commerce, finance, operations, and C-level), has completed over 350 projects, maintains a database of over 100,000 specialists, and has published over 40 case studies. Learn more: What roles does Fast Forward Solutions recruit for?

Fair reservations

  • The figures come from our systems and pertain to this specific project. They do not represent an average across all FFS recruitment efforts.
  • Candidates remain anonymous, and for confidentiality reasons, we do not disclose financial terms or specific client evaluations regarding individual candidates.
  • This role is unique: a large e-commerce platform and large-scale performance diagnostics. The insights regarding the methodology (proof of scale, pre-screening, confirmation of priorities) are universal, but the numbers won’t directly translate to other roles.

Powiązane materiały FFS

FAQ: Hiring a Performance Engineer for Shoper

How do you hire a Platform Performance Engineer or a performance engineer?

The most effective approach is an active one, because such individuals rarely look for jobs and rarely provide detailed descriptions of their work on LinkedIn. In the project for Shoper, FFS searched companies of a similar scale to the client, looking for evidence of work at that scale (problem descriptions, selected cities, and companies), and verified candidates through a short survey on the scale and diagnostic method, as well as an interview about a performance issue scenario.

How long does it take to recruit a niche IT specialist?

In the project for Shoper, active sourcing lasted about a month, until early November 2026. In the published FFS case studies, the recruitment of leaders took anywhere from 7 days to about 9 weeks, and the first candidate profiles are sent to the client after 10–14 days. The more specific the profile, the longer it takes to identify candidates.

Why was it so hard to find candidates for this role?

We looked for companies on a scale similar to Shopera’s, and there aren’t many of them in Poland. People working at that scale rarely described their work in detail on their LinkedIn profiles, so searching for keywords in those profiles yielded few results. That’s why we looked for evidence of work at that scale—such as problem descriptions (e.g., reduced latency, bottleneck, high load)—in selected companies and cities.

How many candidates should be evaluated for a specialized technical role?

In the project for Shoper, there were 443 people in the assignment; 6 of them (about 1.4%) went through an interview with FFS, and 3 proceeded to interviews with the client (about 0.7%). This is the result of a single project, not an average, but it shows that with a very narrow profile, the client sees only a fraction of a percent of the people in the funnel.

Does a job posting help with recruiting for such a specialized role?

For this project, 19 people applied on their own, and almost none of them met the requirements; some did not understand a key technical requirement. The bulk of the work fell on active sourcing, since suitable candidates had to be found and persuaded before they even started looking for a job.

How does FFS screen candidates for a role that requires performance evaluation?

After an initial evaluation of the resume on a scale of 1 to 5, the candidate completes a short questionnaire about platform technology, databases, performance testing, and scalability. This is followed by a verification interview based on a script with evaluation thresholds, and the client receives a report with an evaluation of each candidate and suggested questions.

How much does it cost to hire a technical specialist through a headhunter?

At FFS Direct Search, the fee is 12–16% of annual salary for specialist roles and 15–18% for managerial roles. An alternative is the Shortlist option for a flat fee: 6,500 PLN for 5 candidates or 10,000 PLN for 10, with no placement fee. The first verified profiles are sent to the client within 10–14 days, and the guarantee for Direct Search lasts 90 days.

Are you looking for a specialist with a narrow technical focus?

Tell us about the role and scope. Free consultation, 15 minutes, no obligation.

Schedule a consultation →