- Do you ask clarifying questions?
- Can you identify different testing types?
- Do you consider edge cases and real users?
- Can you prioritize instead of listing everything under the sun?
If you skip structure, you look unprepared - even if you have years of experience.
Step 1: Ask Clarifying Questions (This Is Non-Negotiable)
If you start “testing” immediately, you've already lost points. Good testers don't assume requirements. They extract them. Start with questions like:
- Who is the end user? (Students, office workers, artists, children?)
- What's the primary use case? (Writing notes, signing documents, sketching?)
- What environment will it be used in? (Office, outdoors, school, lab?)
- Are there any specific requirements or acceptance criteria?
- What does "working correctly" actually mean?
This shows maturity. You're signaling that you understand testing starts before execution, not after.
Step 2: Identify Relevant Testing Types
Now you demonstrate range - not randomness.
Functional Testing
Cover the basics without sounding basic:
- Does the pen write?
- Is ink flow consistent?
- Does the cap fit securely?
- Does the clip hold onto paper or pockets?
- If retractable: does the mechanism work reliably?
Usability Testing
This is where weak candidates forget real humans exist:
- Is it comfortable to hold for long periods?
- Is the cap easy to remove?
- Can left-handed users write without smudging?
- Is the grip effective or slippery?
Performance Testing
Yes, even a pen has performance characteristics:
- How long does the ink last?
- Does it write after weeks of inactivity?
- Does it work in different temperatures?
- How many pages can it write before running out?
Security & Safety Testing (Yes, This Matters)
This is where interviewers start paying attention:
- Is the cap a choking hazard for children?
- Are the materials non-toxic?
- Could broken parts become sharp?
Compatibility Testing
Context matters:
- Does it work on different paper types?
- Does it write on glossy or recycled paper?
- Does it write underwater - if that's a stated requirement?
Don't force categories. Apply what makes sense.
Step 3: Prioritize Like a Professional
You cannot test everything in an interview - and pretending you can is a red flag.
State your priorities clearly:
- Critical functionality - does it write?
- Primary user scenarios - typical daily use
- One or two edge cases - to show depth of thinking
This proves you understand risk-based testing, even if you don't name it explicitly.
The Real Takeaway
This question has nothing to do with pens.
It's about whether you:
- Gather requirements before acting
- Think in testing dimensions, not checklists
- Keep the end user in focus
- Make smart trade-offs under constraints
Once you understand that, it doesn't matter if the object is a pen, a coffee cup, an elevator, or a smartwatch.
The object changes.
The mindset doesn't.
So next time you hear, “Test this object”, don't panic.
Slow down.
Structure your thinking.
And let your process do the talking.