<hr/>**评论：**<br/><br/>lansellot: <pre><p>Ask them?</p></pre>jrv: <pre><p>It depends. In Google interviews, you usually could choose the language (or they asked you before the interview how you'd rate yourself in various languages and then choose one that you rate yourself highly in). I once made the mistake of trying to solve a whiteboard coding interview problem in C, when the problem was mainly about parsing strings and managing a stack. So by choosing such a low-level language, I actually made the problem much harder for myself. The same could happen to you with Go for certain problem classes. Luckily, I was allowed to switch to Python in the middle of the interview, which made things much easier for this problem.</p></pre>mwholt: <pre><p>Google and Microsoft do not allow Go to be used for interviews :(</p>
<p>(Source: Me, 6 months ago.)</p></pre>jewishobo: <pre><p>Must be on a case by case basis. I used it 1 year ago.</p></pre>media_guru: <pre><p>Probably. I know someone who also asked to use Go in Google's interview and they said no.</p></pre>brogrammingsins: <pre><p>Case by case. I've applied for a DevRel job at Google and I used Go in the whole process. </p></pre>FrenchDonkey: <pre><p>They do... Source: Me 2 months go</p></pre>bradfitz: <pre><p>False. I work at Google and let candidates use any language they'd like. They just have to be ready to explain the language if I don't know it.</p></pre>izuriel: <pre><p>Normally, in my experiences, you'll be directed to use a specific language or given the option to use "any language you're most comfortable with."</p>
<p>So, I'm going to hazard that your answer will most likely be no unless the latter situation happens. Speaking from the perspective of an interviewer, I told a candidate to a project in X language (99% chance it relates to what we're hiring them for) and they rebuttal with "Can I use language Y instead?" I would already be skeptical of whether I'll see a desirable outcome.</p>
<p>Interviews are a two way sales process, you're selling yourself to the company and they're selling themselves to you. You look a lot better in that process if you're willing to follow the instructions you're given without changing anything.</p>
<p>This is all just my opinion though, both as someone who's been an interviewee and interviewer. I once asked a candidate to write a regular expression for me, they told me they could only do if they could use a tool like one of the many online live regex testing tools (and usually have a reference) which I was fine permitting. I use tools in my daily work, if that's what they need, then let's see how they do. After a few minutes the candidate instead just Google'd for a far more complex regular expression to submit for the interview. That was my limit there.</p></pre>rco8786: <pre><p>Why force a candidate into a language they're not comfortable with? Seems like you're setting them up for failure.</p>
<p>Or does your company require experience in specific language(s) to get hired? That severely limits your hiring pool.</p></pre>Yojihito: <pre><blockquote>
<p>Or does your company require experience in specific language(s) to get hired?</p>
</blockquote>
<p>Isn't that that the case in most cases?</p>
<p>Why hire some Golang guy if you have a Java/.Net-Stack in your company?</p></pre>rco8786: <pre><p>I'd much rather see a candidate express their ability solve difficult problems using tools their familiar with, speak intelligently about a language they have experience in, etc...</p>
<p>It's like not hiring a mechanic because they don't use the same brand of tools your shop does. </p>
<p>FWIW, this is also the philosophy of Google/FB/etc that the OP question was about.</p>
<p>Unless you're interviewing for a team that does a very specific thing(like an interview for the OS team would likely require you to write C in the interview) you can use any language you like. They ask hard questions, the last thing they want is the candidate to be constantly tripped up because they wrote toString instead of ToString or to_s or str.</p></pre>Yojihito: <pre><blockquote>
<p>I'd much rather see a candidate express their ability solve difficult problems using tools their familiar with</p>
</blockquote>
<p>If those tools are not used in the company .... well, like I said, hiring a Go guy that has to learn Java/C# from scratch + all the required frameworks ... have fun wasting 4+ months for this one employee.</p>
<p>Or take the one that knows the tech stack and can start right away.</p></pre>rco8786: <pre><p>If you're hiring people who take 4+ months to be productive in a new language...well I've found your problem.</p></pre>Yojihito: <pre><p>Productive with the companies technology stack? Yes, that takes time and man power to get the person into the source code. Add 2-3 frameworks in an unknown language, like Spring ... I would definitly need 2-3 months for that.</p></pre>izuriel: <pre><p>If we're an "X" shop (where X is a language) then I see no issue expecting a candidate to perform in X. If they can't write something simple for a whiteboard question, or refuse to attempt it in the expected language or on a take home assignment can't learn enough to get by -- then I can assume the first several weeks I'm going to be paying them to learn. </p>
<p>If I'm hiring a junior level engineer that's probably acceptable. But from a senior level candidate I'd say no. I would expect a senior level engineer to adapt quickly, make good assumptions and/or ask good questions. I expect this because I would do no less in the same situation. Hell, I learned iOS and wrote a Twitter app for iOS (before the interview) when going to an iOS shop. Demo'd what I could learn and do in a few hours and landed the job easily. </p>
<p>If I can do it, I don't settle for less (again unless hiring for a junior spot). </p></pre>rco8786: <pre><p>I guess we just have differing opinions. There are some specialties out there that I would want a candidate to use specific things(mobile being one of them..to your point). But the questions/problems you face in Google/FB/etc interviews are general algorithms and they're difficult. They let interviewees work in any language because they're looking for the person to demonstrate the ability to solve tough problems using tools they're good at. They trust that good candidates can adapt to new tools once they are hired.</p></pre>izuriel: <pre><p>When I was interviewing at Apple I was asked both C and Ruby algorithmic questions because that pertained to the job. When I was being interviewed at Facebook I had to write everything in JS because that was relevant to the position. </p>
<p>I was never given the option to "choose" a language. </p></pre>cavaliercoder: <pre><p>I interviewed at Facebook using Go on the whiteboard. The interviewer was not familiar with a few of the implementation specifics like maps so be prepared to explain some of the language and stdlib internals correctly. They also took photos to review later with other Go developers.</p></pre>storm14k: <pre><p>I wonder why companies want problems solved in any language at all. Outside of needing someone with very specific knowledge of a specific language I'm more concerned with logic and thought process. A language can be learned. When I conduct an interview and give a problem I like to see diagrams and pseudocode and the more language or framework specific stuff I see the more red flags go up for me. We do a lot of polyglot stuff on my gig so maybe that's tainted my view.</p></pre>__amit__: <pre><p>Without coding its liking you are in Olympics and standing next to a swimming poll and explaining how to swim. The one who can explain best wins.</p></pre>lovetocode: <pre><p>I have to tend to agree with you. I was never asked to whiteboard any code in my interview and have never personally seen it on any interview board I have been on.</p></pre>dlsniper: <pre><p>Uhm, yeah, if you ask before hand. It also depends on their needs and also on the interviewers.
If you apply for a role that says C++ / Java might be a bit hard to sell Go as a language to do the interview in, might not be.</p></pre>
