end program hello.Īnd here’s a hello world program in most other languages println('Hello world') Second: The one with some (but not too much) syntactic sugarįor a sense of what I’m talking about, here’s a Hello World in COBOL *> Hello, world identification division. But that involves getting familiar with the syntax, some runtime understanding like how it handles thread safety, and any other common idiomatic aspects.ĭetailed language questions (“How does Java handle autoboxing?”, “How do python Lambda expressions work inside list comprehensions?”) aren’t common, but familiarity with the lower level details of the language will come through.

The caveat here is if you spend the most time writing a verbose language, say assembly or C++, and you have a lot of time to prepare it might make sense to get comfortable in another language. That means the first, best choice is the language you spend the most time in. During an interview you don’t want to spend time fumbling with how to create a collection of type strings, you want to spend time solving the problems. Your first choice should be the language you’re the most familiar with. So how do you pick? I think there’s a hierarchy. I’ve always been given some kind of tool with syntax highlighting, and occasionally the ability to actually run the language.

Most tech companies I’m aware of do “language agnostic” interviews, meaning you can pick the language you do coding exercises in. You’re prepping for software engineering interviews, you’re psyching yourself up to hit Leetcode, and then your recruiter asks, “What language do you prefer to interview in?”

How much is microsoft teams app