Interview archetype

The Pressure Tester

Questions every decision. Keeps asking "why not the other way?"

Set The Pressure Tester as your interviewer and the app will pick follow-ups in their categories and weight your rubric their way.

How they behave

You say "I would use a cache." They say "why?" You explain. They say "why not just a bigger database?"
They will push back on answers that are correct, to see whether you fold. They are not disagreeing. They are testing whether you know why you chose.
They rarely move on quickly. Expect three or four rounds on a single decision that other interviewers would accept in one.
They often argue for a position they do not hold, just to see whether you can defend yours.

What a failing answer looks like under this style

You change your answer the moment they push. If you switch from a queue to a direct call because they raised an eyebrow, you have told them the first answer was memorised.
You repeat the same justification louder. "Because it scales better" three times is not a defence, it is a stall.
You cannot say what you gave up. Every choice costs something, and not knowing the cost suggests you did not really choose.
You get defensive and treat the question as an attack rather than a request for reasoning.

How to survive them

Have a number or an access pattern behind every decision. "40 writes a second" ends an argument that "it scales" cannot.
Name the alternative you rejected and why, before they ask. That converts a challenge into a discussion.
When they are right, say so immediately and adjust. Conceding a good point is a strength signal, not a weakness one.
Distinguish between "I chose this and here is the cost" and "I would need to measure that". Both are strong. Bluffing is not.

Say this

"I chose X. The main alternative was Y, which is better when [condition], and that condition does not hold here because [number]. What X costs me is [cost], and I am accepting that because [reason]."

How they weight the rubric

Same design, graded differently. This is why the archetype changes your score.

Requirements

×0.9

Lifecycle

×0.8

Numbers

×1.0

Design

×1.1

Tradeoffs

×1.6

Defence

×1.6

They reach for:Question the choiceForce the costAttack consistency

Three-question drill, in their voice

Same rule as everywhere else: you answer before you see anything.

You said you would add a cache. Why not just buy a bigger database instance?

0 / 30 characters

You partitioned by user id. Why not by time? Time is simpler.

0 / 30 characters

You are using eventual consistency here. What if I told you the business needs it exact?

0 / 30 characters