I admittedly have not experienced many interviews. But my most recent one had a couple interesting questions that I did not really anticipate. Everyone expects the “leetcode” style of questions in programming interviews and when under the pressure of time and getting a job, I would not describe them as easy. But the two interesting questions that did not relate to programming stuck in my mind. Luckily, I had seen these logical teasers before. I cannot imagine trying to handle them otherwise.
The first: a man goes to a hardware store to buy something for his new home. He asks the clerk “How much for 9?” and is told “$3”. Then he says “I’ll take 925 then” and the clerk replies “That will be $9.” What was the man buying? Doesn’t really make sense until you think about him buying the “6” “0” “0” individually, and theoretically can indicate how you can think outside of the box, but really seems more like a test of whether you have encountered the questions before.
The second without getting into specifics gave 3 seemingly random but related items, saying each one cost $5, $10, and $15 respectively. Then it gave you another related item and asked you to guess how much it cost. To find any pattern amongst the items, you had to not look at the items themselves but think about the words, basically how many vowels each word contained. Each vowel cost a fixed amount. Ultimately, I got these right (I think) but I hope in general these parts weigh low in the process for software engineers at least.
The more interesting section in a positive way involved answering questions based on a made up programming language. I liked how it allowed you to apply the rules and methods you learn in CS 225 and some of less “programming” related courses.
As far as the project goes, just slow and steady progress recently. Getting Unity to do what you want or expect seems to be a constant cycle of either a) trial and error or b) google. We did finally start getting to the point where we start merging some of our code and I forgot how much of a headache that can be. So far it doesn’t seem to have created too many issues, but I can admit I forgot one of the lessons from previous courses. Commit early and commit often. By waiting 3-5 days before committing I definitely got to the point where I worked on code that a teammate edited. Luckily it only led to a little cuts and edits to get everything back in working order. I also think I need to communicate a bit more with my team. I got off easy and learned my lesson.
