[uhuruity]

> just something like converting numbers to strings

Isn't that the kind of thing that someone senior would typically look up? Do you think that whether or not they have that part of the language API stored in their working memory is a good predictor of their ability to do a good job as a senior eng?

[silisili]

We allow them to use Godoc, of course. That said

> Isn't that the kind of thing that someone senior would typically look up?

Not at all. There's at least two ways to do this very easily in Go(one line, no errors to worry about even), and I'd expect someone who claims to use it daily to know one of them offhand.

While I think languages are just tools, in our instance we're very clear we need people versed and ready to start.

I don't think people are dumb here, I think they just blatantly lie on their resumes.

[Double_a_92]

That skill has nothing specifically to do with Go. Most languages have some "ParseInt" function or so. And of all the languages I use for daily work I could not 100% tell you what that function is exactly called.

By doing that you are wasting a potentially good developper because they didn't happen to remember some languages exact syntax.

It's also just straight up insulting. If someone worked for x years in a related role... do you just assume that they were a fraud at that job, and they just leeched of that companies money?!

[trebbble]

Over 15 years in the industry, shitloads of code shipped in a dozen plus languages, repeatedly taken an idea all the way to being a functioning product, usually get great feedback from peers and managers, often taken point on architectural matters, et c., et c.

Yeah, I'd probably google that in any language I've written, including ones I've worked in in the last couple weeks. Even if I thought I knew what to do, and even if I tried it and it seemed to do the right thing, I'd google it (or use in-IDE docs, or similar) because I wouldn't trust that I was entirely correct.

... however, narrow the question and give me some resources ("the input will be a positive, unsigned 32-bit integer; the string should be ascii and use digits, not words, to represent the number; do insert commas every third digit [and we're working exclusively in English, so commas are all we need and you can ignore system locale preferences—one of many subtle ways one might screw this up]; here's a printout of an ascii table for reference") and I can probably do something like what's requested, without the aid of Google. As long as you don't expect the syntax to be completely perfect.

[AQuantized]

Honestly while I would agree for a lot of obscure methods, I can't imagine a senior engineer not knowing how to convert an integer to a string.