Back to all Articles
Recruitment forms rarely win design awards, but they reveal something far more telling: the maturity of a company’s product mindset. A single dropdown field — often dismissed as “just a tiny UI detail” — can expose how fragmented, improvised, or outdated the design system truly is.
Recently, I came across a textbook example of such a mismatch.
A dropdown field titled “How Did You Hear About Us?” displayed a text input on top, as if it supported search. Naturally, I typed LinkedIn. And naturally, nothing happened.
No filtering.
No suggestion highlight.
No “No results found.”
No confirmation that the option even exists.
Visually, the component promised one behaviour.
Functionally, it delivered another.
This is not a minor inconsistency — it is a UX failure with measurable consequences.
1. Let’s Look at the Interaction: What Actually Happens
At first glance, the component looks like a standard searchable select:
- There is a text cursor.
- The user can type.
- The dropdown opens with a list of predefined options.
Everything about the affordance — what the UI suggests you can do — signals “Type to search.”
But underneath, the component behaves like a static select list:
- The list does not filter.
- Typing does not highlight relevant options.
- The system provides zero feedback.
From a user perspective, it feels like the field is broken.
It’s not “slightly confusing.”
It’s not “suboptimal.”
It’s not “could be improved.”
It’s misleading.
2. Why This Is a UX Problem (Not a Developer Corner Case)
This is exactly the kind of micro-issue that non-designers overlook — but senior product designers recognise instantly. When the affordance does not match behaviour, users lose trust in the interface.
The issue creates several UX risks:
a) It creates cognitive dissonance
The UI invites the user to type.
Typing does nothing.
Mismatch → friction → frustration.
The brain registers it as a “broken” interaction.
b) It forces the user to guess how the system works
Should I type?
Should I scroll?
Should I click?
Does the option even exist?
Forms are not the place for mystery.
c) It increases the chance of erroneous submissions
If the option exists (e.g., LinkedIn), users may assume it doesn’t, simply because the filtering doesn’t work.
This generates:
- Wrong data in the recruitment system,
- Misattributed marketing analytics,
- Distorted source-of-hire reporting.
Tiny UI. Real business cost.
d) It violates the basic principle of consistency
A dropdown that behaves inconsistently with its own affordance creates friction across the entire user journey, not just this screen.
Consistency isn’t a “nice-to-have.”
It is the backbone of usability.
3. What the User Thinks vs. What the System Does
To illustrate the gap:
User expectation, based on the design:
- “I can type to filter.”
- “If an option exists, typing will help me find it.”
- “If the option doesn’t exist, the system will let me know.”
System reality:
- “You can type, but it won’t do anything.”
- “If an option exists, good luck spotting it manually.”
- “If it doesn’t exist, you’ll get no feedback.”
The UI sets an expectation that the system cannot meet.
This is UX debt — the silent kind that accumulates unnoticed until it becomes expensive.
4. How This Should Be Designed — The Two Valid Solutions
There are only two correct patterns here.
Solution A: Remove Text Input (Classic Select)
If the field is meant to be non-searchable, then:
- Remove the text cursor.
- Remove the ability to type.
- Display only the predefined list.
- Make it a clean, predictable select component.
This respects the mental model of fields with fixed answers.
This pattern is ideal when the number of options is small
(3–10 items).
Solution B: Implement Real Search (Searchable Select)
If the goal is to help users find options quickly, then:
- Typing filters the list dynamically.
- Matching options appear immediately.
- Non-matching input produces “No results found.”
- The system highlights the best match.
- Selecting closes the menu and updates the field clearly.
This pattern is ideal if the list is long
(10–200 items, e.g., countries, job titles, departments).
What is never acceptable:
A searchable input that doesn’t actually search.
This is the UI equivalent of a door handle that doesn’t open the door.
5. The Business Impact: Why Micro-UX Matters More Than You Think
Companies often underestimate how these “small bugs” influence behaviour.
Here’s what this micro-issue can cause over time:
1. Form abandonment
Any friction in a recruitment form increases drop-off.
Candidates are impatient by definition.
They owe nothing to your company.
2. Contaminated analytics
“How did you hear about us?” feeds:
- Marketing attribution
- Advertising ROI
- Source-of-hire reports
- Budget allocation decisions
Bad data → bad decisions.
3. Brand perception damage
A sloppy form is interpreted as a sloppy organisation.
Users don’t separate the UI from the company.
When an applicant’s first experience with a company feels broken, their trust drops — often permanently.
6. What This Reveals About Design Systems
This tiny UX failure signals deeper issues:
- Components that look unified but behave inconsistently
- No clear definition of interaction states
- Weak documentation
- Lack of cross-functional alignment
- Patchwork implementation where design and development diverged
As a Senior Product Designer, I’ve seen this pattern in many organisations. This is how design systems begin to erode: not through one major bug, but through dozens of micro-incoherences that quietly accumulate.
7. Lessons Learned (and Why I Document These Cases)
Every time I notice such a mismatch, the same truth becomes clear:
UX is not about making interfaces pretty.
It’s about making behaviours predictable.
Users don’t want to “discover” how a form field works.
They want it to work the way it looks like it works.
Consistency is not cosmetic.
It is functional integrity.
8. Final Thoughts: Why I Pay Attention to Details Like This
This example is small, but the principle behind it is huge.
Design is the discipline of eliminating friction.
Product design is the discipline of eliminating confusion.
UX design is the discipline of eliminating guesswork.
A micro-interaction, when broken, stops the flow.
A micro-UX fix, when implemented, elevates the entire experience.
And that is why I document these cases:
because behind every “tiny” detail, there is a user trying to move forward.
When we design responsibly, we help them get there.
