Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For Employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      Glitch

      Engaged Employer

      About
      Reviews
      Pay & benefits
      Jobs
      Interviews
      Interviews
      Related searches: Glitch reviews | Glitch jobs | Glitch salaries | Glitch benefits
      Glitch interviewsGlitch Software Engineering Intern interviewsGlitch interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Center
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy & Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent Posts

      Copyright © 2008-2026. Indeed, Inc. "Glassdoor," "Worklife Pro," "Bowls," and logo are proprietary trademarks of Indeed, Inc.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalized job recommendations and updates by starting your searches.

      Software Engineering Intern Interview

      Feb 13, 2014
      Anonymous Interview Candidate
      No offer
      Positive experience
      Average interview

      Application

      I applied online. The process took 4 weeks. I interviewed at Glitch

      Interview

      Emailed them my resume and cover letter, a robot responded asking for some additional information which I provided and was contacted some time afterward (forget exact time frame). I went through 2 or 3 phone screens, each one following the typical format of experience, coding question, then my turn for questions. Each interviewer was fun to talk to and the process was smooth. Their follow up time was quick (1-2 days after each interview) but not the quickest. I was flown out to New York and put up in a fairly nice hotel for the on site interviews (try the fish and chips from the in-hotel restaurant!). They went alright and covered things you'd expect (cs questions involving graphs and such). I had a serious problem with jet lag and adjusting however, I also messed myself up by agreeing to come up the day after my last final. The day of the interviews my body was about as angry at me as it could be, and I was absolutely not performing at my best. Here is what I absorbed from my visit though: * That office is swanky. It's so incredibly nice I was actually a little put off by it. There is a guard and greeter at the bottom floor who printed out a name tag for me, and you have to be buzzed in to get into the office. The couch in the front area is insanely expensive and artsy. I wouldn't take anyone to visit the workplace because I'd be embarrassed. Over-the-top in my opinion. * The people there are very nice and laid back, definitely all people I could imagine hanging out with after work and playing video games with. They all seemed very intelligent as well. You will definitely be among great people if you work there. * Their whiteboards are tiny. Not even close to big enough. Sure they're extra nice because they're made of glass but I would definitely prefer size and functionality over the prettiness factor there. * Their food is incredibly delicious, and they have a ton of snacks. Didn't get to try their coffee but I bet its amazing because the machine was apparently bought from some fancy coffeeshop that went under. * They did not seem very familiar with C++. That could have been a trick to get me to explain C++ concepts to test me but I think that most of them are much more familiar with C. * A lot of their work is done with Windows. If you come from a Unix world like me this can be a little off putting. * Gorgeous view from the office. I could stand and look out that window for hours, and I'm betting many of them do when thinking about particularly challenging problems. * Center of wall street, prepare to be hassled a lot in front of the entrance by tons of solicitors. * New York is a very different time zone from the west coast, did you know? If you're going for an onsite interview, prepare yourself for the incredible jet lag if you're coming from far away. Try to convince them to let you stay more than one night to get acclimated. I know it would have helped me immensely. I was a total mess internally for the interviews. * I did not get anywhere near the feeling of passion I get when talking to engineers from other companies. Ask each of your interviewers why they chose to work for Fog Creek, I did not get a lot of motivating answers to that question unfortunately, most of them could be summed up by "well I applied and they took me". * A sign hung on the wall that said "no fun allowed" would not be out of place. The atmosphere felt very much like a corporate office (albeit a totally decked out and beautiful one). Lively is not a word I'd use to describe the office environment. This could have been a quiet day though (it was a Friday).

      Interview questions [1]

      Question 1

      Typical questions like the ones presented in Cracking the Coding Interview. Know that they're very creative and organized though, so don't plan on getting a question you've heard anywhere else before (which is perfect imo). If I wrote an exact question down here you can be assured they wouldn't ask that question again. They will almost certainly test you on your ability to use pointers.
      Answer question
      1