![]() ![]() If you want serious interview level feedback, you should post whatever you had at the 30 minute mark (or if you finish early, great) even if it's an incomplete solution. I would encourage anyone who wants to practice for a real interview to attempt doing these challenges in 30 minutes or less and then post your result here. Moreover, our interviews are capable of answering any question the candidate may have about the problem. ![]() Whether or not the code compiles is not actually that important compared to whether the candidate is getting the gist of the problem and is able to get to a solution that probably works, even if there are some compilation issues that would be easily fixed once you paste it into Xcode.Īlso, we always emphasize and encourage the use of "whatever tools you use in your day to day development", including but not limited to Google, StackOverflow, etc. ![]() Depending on how the interview is conducted exactly, we will typically use a tool like but we have also let candidates simply work directly in Playgrounds. More difficult than FizzBuzz, but not so hard that it shouldn't be doable in 30 minutes or so. I try to keep the live coding exercises down to easy-to-moderate difficulty. I figured users of this subreddit might enjoy seeing some interview code challenges and get some feedback from interviews. I have been conducting an unusually large number of interviews for iOS positions at my company lately, and I've been coming up with (or finding) coding challenges for the candidate to work through during the interview. ![]()
0 Comments
Leave a Reply. |