Getting an Interview
Getting an Interview
Interviews for Top Jobs at Nintendo of America
- Software Engineer (2)
- Training Specialist (1)
- Administrative (1)
- Senior Manager (1)
- Assistant Manager (1)
- IT Program Manager (1)
- Software Developer (1)
- Human Resources (1)
- Coordinator (1)
- Order Picker (1)
- Engineering (1)
- Retail Representative (1)
- Marketing Assistant (1)
- Systems Administrator (1)
- Tech Support (1)
- Consumer Service Representative (1)
- Creative Development Specialist (1)
- Bilingual Product Specialist (1)
- Marketing Position (1)
- Category Development (1)
- Bilingual Localization Coordinator (1)
- Product Testing Lead for Associate Staffing (1)
- Digital Business (1)
- Bilingual Project Coordinator (1)
- Aerotek Shipping Associate (1)
- Buyer (NES Merchandising NYC) (1)
- Localization Writer/Editor - Contract (1)
- Level Designer (Contract) (1)
- Corporate Services Lead (1)
Helpful (1)No OfferPositive ExperienceAverage Interview
I applied online. The process took 2 weeks – interviewed at Nintendo of America (Redmond, WA) in April 2015.
The interview was pretty simple. The pre-interview began with a 2-hour timed writing test that involved localizing some game dialogue (four sets of dialogue from the same game). This took me the full two hours as I made sure everything was as clean as possible and all the parameters were met. I didn't hear anything for a week or two after the writing test, so I sort of assumed the hiring managers had moved on. However, I received an email from the recruiter that they wanted to set up an in-person interview with two of the hiring managers. I spent 15 minutes with a different recruiter (super nice guy who showed me around the campus a little bit, then asked some basic questions). I then met with two of the hiring managers (half an hour each) and they asked me questions about my history, gaming likes, what types of things I think make for good game dialogue, and how I went about the writing test. Nothing too outstanding (and not a single question about my strengths or weaknesses - thank goodness! Who even likes those questions??). It really seemed more like a fluid conversation between two adults getting to know one another. I can tell they are a tight-knit group and they were looking to see if I would fit into that group. I was also pleasantly surprised to see that they were about my age (late 30s/early 40s), unlike what I had heard that they were all young gamers. They were just people - and that was really pretty awesome. I felt very comfortable and they were all very pleasant, kind, and engaged. I knew by the end of the interview that I was not what they were looking for, but I'm glad I had the chance to interview. It was a very relaxed atmosphere and everyone was really great. The recruiter called me later the same day to say they managers were going to pursue other options, but he wanted to see if I would like him to forward my resume onto another recruiter for a full-time benefited position. Yes, please! :) It was a great experience.
- No OfferNegative ExperienceEasy Interview
I applied online. The process took 2 weeks – interviewed at Nintendo of America (Redwood City, CA) in February 2015.
Initial phone screen with an internal recruiter. Then another phone call with the hiring manager and lastly being invited to the office to meet and interview with the team. Overall process was simple and they were very fast at responding. However, after final 1:1 interviews there was never any input even after a follow-up email asking about the status. Left a bad taste that after going to meet with them and spending 4 hours in their office the HR team cannot even be bothered with a "thanks but no thanks" email letting me know that they are not interested. Very disappointing end to what seemed like a great company and working environment.
- Nothing particular or out of the ordinary. Everyone seemed intent on wanting to know "why Nintendo"? Answer Question
- No OfferNegative ExperienceEasy Interview
I applied online. The process took a week – interviewed at Nintendo of America.
Folks were nice enough, although a bit disorganized. Interview questions were reasonable, but on the easy side. Walked through some real world problems. One interviewer did ask puzzle questions which I thought were passé.
- One question was how to test a particular system. Goal was to find all issues that had been found in the real world. Answer Question
Helpful (1)No OfferNegative ExperienceAverage Interview
I applied online – interviewed at Nintendo of America (New York, NY) in June 2014.
I applied via LinkedIn. An interview offer was extended via phone. I spoke with Jodi. The interview lasted roughly thirty minutes. The questions were very boilerplate but engaging. I ended the call asking when I should follow up. Jodi emphasized she would let me know whether or not I was hired, that she lets "everyone" know. I never heard from her again.
- What company culture do you thrive in and how do you expect Nintendo's company culture to be? 1 Answer
- No Offer
I applied online. The process took 2+ months – interviewed at Nintendo of America.
Initial phone interview; 2nd phone interview with supervisor; 3rd interview was in person with the entire department
- What sets you apart from the other candidates? Answer Question
- No Offer
Information interview with some folks on the HR team. Provided a tour of thier fabulous office building and the opportunity to ask questions about working in HR there and company culture.
- Nothing difficult. Answer Question
Helpful (1)No OfferNeutral ExperienceAverage Interview
I applied through a recruiter. The process took 5+ months – interviewed at Nintendo of America (Redmond, WA).
I was initially contacted by a recruiter via LinkedIn for this specific position. He wanted to speak over the phone, so I agreed. I didn't hear back from him for about a week so I contacted him back on LinkedIn and it turned out he was out of town. That was fine.
We set up a phone conversation a week later and spoke briefly. During this time he told me about the overall requirements of the position and made sure this was something I wanted to pursue. Since it was, we set up a time for me to go to the offices in Redmond to take a translation test. That was set up for the following week.
I went in, took the translation test, met with the recruiter briefly, and that was that. He just made sure again that this is something I wanted to pursue, made sure that all my questions were answered, et cetera. The translation test involved translating one article-length text from Japanese into English and one from English into Japanese. Both had to be completed in an hour.
About a week after that I was contacted by the recruiter again telling me that I passed the translation test and was to go in and interview with a manager. That was set up for about a week or so afterwards.
The interview with the manager was in both Japanese and English and seemed to go fairly smoothly. I was given a document in Japanese and given 5 minutes to look over it before the interview asked me questions about it in English. The entire interview took about 30-45 minutes.
After that, it took another week or two before I was contacted for another interview. This was pretty much the last round interview. I went in, incredibly nervous, and probably botched the interview because of that. I was told that they would make a decision within a week or so but the recruiter seemed to have high hopes for me so I was hoping for the same.
A week or two passed and no word so I emailed the recruiter. No word back - again, a bad thing. Finally he called and said they went with someone else. He told me he sent my information to another / similar department for consideration.
A week later I was sent the translation test for that. I completed it, sent it back in, then went on a vacation for a couple of weeks. When I got back, I still hadn't heard back so I emailed the recruiter. No word back. I called him and he informed me that they decided not to go forward with my application but suggested another job that was now further off from what I wanted to do. I told him I'd think about it, and after considering it, I decided that I would not pursue it.
Over the next couple of months whenever something cropped up again, I'd apply for it, let the recruiter know, and then never hear back. It was disappointing, to say the least, and I was stuck in interview limbo for quite some time. While I was being considered, the process was great, but before I realized it my foot was back out the door and I had no way in, despite getting to the last round interview for the first position I applied for.
- Describe in Japanese how you would approach working as a "child" company under Nintendo's parent company in Japan differently than working at an independent company. Answer Question
- No OfferNeutral ExperienceAverage Interview
I applied through college or university. The process took a week – interviewed at Nintendo of America.
Interview process is pretty much getting pulled into their building and interviewed by a few different people. The ask everything from basic c/c++ questions, questions about projects you have worked on, logic puzzles, and they have you write a little bit of code. The interview is generally laid back and casual. The interviewers also share a bit about themselves and what they do at Nintendo of America.
- The hardest part of the interview would be for me recalling all the little facts about c/c++ that they ask. Study up on these. If you aren't good with logic puzzles make sure you go over those before you go to the interview. The hand written code they have you do is pretty simple though and should be no problem for anyone. Answer Question
- No OfferPositive ExperienceAverage Interview
I applied online. The process took 3 weeks – interviewed at Nintendo of America (Redwood City, CA) in February 2014.
My first phone interview was with the hiring manager. I thought it was odd I skipped talking to a recruiter but seemed like a good sign. Hiring manager was very nice and interesting to talk to. I was told not long after that I'd be brought in for an on-site interview. When I asked about public transportation options I was told to avoid it at all costs - it basically was not an option. This wasn't very appealing to someone who lives in San Francisco and doesn't ever feel the need for a car. I had to borrow a car to get to the interview in Redwood City and the location of the office was pretty remote. I couldn't even figure out where you could go for a coffee or a sandwich on a break. It felt very caged in, and the office was really unimpressive and very eerily quiet for a gaming company. I just didn't get a great vibe being there. The staff was very nice though, and I think I could have worked nicely with them if I could get myself to go into that bland office park every day. A few of the interviewers mentioned how strict Nintendo policies are, making it hard to be completely creative each day. That was a big red flag for me. When the recruiter called me to tell me their decision she said they were going with someone with more experience, but wanted me to come back to interview for a smaller role. This kind of bugged me since it was obvious from my resume how much experience I had, but they still brought me on-site anyway. In the end, taking the smaller role was not worth the commute for me, and I thought it was a little silly I'd have to interview with the same department all over again.
- How would you get more young children to play Nintendo games? Answer Question
- No OfferNeutral ExperienceEasy Interview
I applied through other source. The process took 5 days – interviewed at Nintendo of America (Redmond, WA) in November 2013.
Contacted by HR through email. Had initial technical phone screen, then brought in for an interview with the developer lead. The developer was very friendly, but the HR person didn't seem to like me for some reason and seemed determined to not change from that position. Sat in a room with the two of them during the interview process.
- The questions seemed very fair: stack manipulation and some knowledge-probing questions about XAML. There were no "puzzles" or "tricks" coding questions, they were all questions that might actually apply to a real situation. Answer Question
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review