# Invalid Transactions: Study Guide

Invalid Transactions shows up often in coding rounds. Here is how I talk through it when the interviewer is watching.

## Key idea

A transaction is invalid if amount > 1000 or another transaction with the same name happens in a different city within 60 minutes. Group by name and, for each transaction, scan the same-name list for a time/city conflict (n is small, <= 1000).

## Steps to say out loud

1. Restate the input and the exact ask, and nail down constraints and overflow.
2. Name the pattern (binary search on the answer, monotonic stack or deque, interval / interval-DP, string hashing, graph traversal, or shortest paths) and why a nested scan or naive search fails.
3. Code it, then trace a short example plus one empty or already-solved edge case.

## Complexity

O(n^2) acceptable.

## Common mistake

Marking only the later transaction invalid (both are invalid) or using a 60-second window.

## Practice tip

Time yourself: two minutes to explain, ten to code, three to test edges. Disclosure: I work on Linkjob AI. I also keep a practice cheat sheet at AI job interview answers in real time.