How to prioritize backend tasks when multiple requests arrive simultaneously: front-end blocker, client system crash, future blocker in 2 weeks, and a feature request from the CEO?

Backend task prioritization in a situation with multiple simultaneous requests should be based on impact and urgency:

1. System crash at the client — a critical situation requiring immediate response, as it affects the client's business.
2. Frontend blocker — if the frontend is not working, it directly affects users, so this task is also high priority.
3. Feature request from the CEO — important from a business perspective, but if there is no urgency, it can be scheduled after critical issues are resolved.
4. Future blocker in 2 weeks — a planned task that can be postponed but should be considered in planning to avoid future problems.

Thus, first address emergency and blocking tasks, then important business requests, and finally planned tasks. It is also important to communicate with stakeholders to align expectations and timelines.