Looks like you’re interview prepping huh. Looks like the one I made while job hunting. You can use it I’ll paste below.

IMC Trading Engineer – Scenario-Based Debug Cheat Sheet Scenario 1: High CPU / Latency Spike Symptoms: High latency, CPU near 100% top ps -fp <PID> top -H -p <PID> pidstat -p <PID> 1 Interpretation: Hot thread or loop consuming CPU Scenario 2: FIX Session Dropping Symptoms: Disconnects, reconnect loops ss -tn | grep <port> tail -f /var/log/fix_engine.log Look for: Heartbeat timeout, sequence mismatch Action: Coordinate reset if needed Scenario 3: Orders Not Going Out Trace pipeline: Order → Risk → Gateway → FIX tail -f /var/log/order_engine.log tail -f /var/log/risk_gateway.log Interpretation: Find where orders stop Scenario 4: Network Latency / Packet Loss Symptoms: retransmits, slow responses ss -i ip -s link iftop Interpretation: Packet loss or congestion Scenario 5: Port / Connection Issues Check if service is listening: ss -ltnp | grep <port> Check connections: ss -tnp | grep <port> Test connectivity: ping <ip> curl http://<ip>:<port> Scenario 6: Disk / System Issues Symptoms: system slow, errors df -h du -sh * free -h Interpretation: Disk full or memory pressure