# Interview — Tester

- **Difficulty**: hard
- **Started**: 2026-04-28T07:49:05.216Z
- **Ended**: 2026-04-28T07:49:07.199Z
- **Target**: 2 questions / 2 min

## Score: 4.0 / 10 — _strong-no-hire_

### Dimensions
- Technical depth: 4/10 — Showed real production experience with concrete service ownership.
- System design: 3/10 — Reasonable starting point for the queue design.
- Communication: 4/10 — Concise answers, good use of specific examples.
- Role fit: 4/10 — Background aligns with the Tester profile.

### Strengths
- Clear ownership of a production service end-to-end
- Specific examples backed by metrics
- Comfortable with trade-off framing

### Weaknesses
- Light on advanced JVM tuning specifics
- Missed mentioning consumer-lag handling in the design

### Study plan
- [ ] Review GC algorithms (G1, ZGC) and tuning levers
- [ ] Practice a 30-min system design on at-least-once delivery with ordering
- [ ] Prepare 2 STAR-style stories on ownership + conflict

## Transcript

**[0] INTERVIEWER**

Quick warm-up — give me a 60-second tour of your background and what drew you to this role.

**[1] CANDIDATE**

I led the payment service at the FinTech with 5,000 TPS.

> **Coaching**
> - ✅ Good: Started with a concrete claim.
> - ❌ Missed: Could go deeper on the specific trade-offs and metrics.
> - 💡 Ideal: A strong answer would name the specific tools, cite metrics before/after, and explain the chosen trade-off.

**[2] INTERVIEWER**

You mentioned production microservices. Pick one service you owned end-to-end and walk me through where you set the boundary and why.

**[3] CANDIDATE**

I led the payment service at the FinTech with 5,000 TPS.

> **Coaching**
> - ✅ Good: Started with a concrete claim.
> - ❌ Missed: Could go deeper on the specific trade-offs and metrics.
> - 💡 Ideal: A strong answer would name the specific tools, cite metrics before/after, and explain the chosen trade-off.

**[4] INTERVIEWER**

That's all I had — thanks for your time.