The interview started with a brief introduction and quickly transitioned into a rapid-fire round of questions: 1. What is Git? 2. What is the cherry-pick command in Git? 3. How can we revert to a previous commit? 4. What is the practical use of branching? 5. What is Git stash? 6. How does .gitignore work? 7. Where does Git store all the data? As I mentioned JavaScript in the introduction, the interviewer then asked related questions: 8. Is JavaScript compiled or interpreted, and why? 9. What are the differences between JS, React, and Node? 10. Are React and Node compiled or interpreted? 11. If there is a form on a website, how would you validate the data? 12. What would be different in client-side and server-side verification? 13. What happens if JavaScript is disabled in the browser? 14. How could data be verified using only HTML? 15. What are the different ways to store data on the client side? 16. How does the session store data? 17. If I do not accept cookies, will the session still work? 18. How does session data communicate between the client and server? 19. How can we store user passwords in the database? 20. What is salting, and what is its use case? 21. How are WhatsApp messages end-to-end encrypted? 22. How do they use encryption and decryption? 23. Can we use hashing instead of encryption and decryption? The interviewer then moved on to database-related questions: 24. What is indexing? 25. Does indexing affect performance? 26. What is a rainbow table? 27. Can we hash images?