The first 6 interviews were all talking about me. Questions such as: How do you feel about EA? How did you get into gaming? What languages are you proficient in? Are you up for moving to California? The final one, the one that I failed at, was asking about Perforce. The questions are as followed: 1.) Source Control. What is source control? Why do we use it/Why is it important? There are multiple different types of version control out there, what is the differences between them? Why do you think the game industry primarily use Perforce over Git? What is Perforce good at that Git isn't? What is Git good at that Perforce isn't? 2.)Perforce Depots and Workspaces. What's the difference between a depot and workspace? How does workspace mapping work? What does the mapping "//depot/tools/...//Respawn-Nhillen/tools..." mean? Why does Perforce differentiate between these two concepts? 3.) Changelist Management. A user comes to you requesting help. They have checked in a change and realized that it has significant issues and they went to revert their changelist. They are uncertain if this is safe to do, or if it'll have ramifications (Let's assume for this question, we're only interested in if there were changes made to the files in this CL specifically). In Perforce, how would you view the files in the changelist? How would you determine if someone had edited those files after the user? How would you see what was in the changes that those new users made?
