3 ms·
If I quizzed engineers, what percentage of them do you think would get that exactly right? Prior to your post, I had myself thought — as Stanley seems to — thin
by deathanatos 9y ago
If I quizzed engineers, what percentage of them do you think would get that exactly right? Prior to your post, I had myself thought — as Stanley seems to — think that Unix referred to the operating system by that name. I did not know that,
> By decree of The Open Group, the term "UNIX" refers more to a class of operating systems than to a specific implementation of an operating system; those operating systems which meet The Open Group's Single UNIX Specification should be able to bear the UNIX 98 or UNIX 03 trademarks today, after the operating system's vendor pays a substantial certification fee and annual trademark royalties to The Open Group.
But if I were exchanging information with a candidate, what Stanley provides is more than I would expect from a candidate (even from industry; he seems to be a student); that he isn't exactly on the mark should have been fine. If we really wanted exacts, the recruiter had ample opportunity to explain his/her position, but instead, we get nothing. Stanley took the time to both give his view on things, and give a simple layman's answer that conforms to that view when the tech jargon didn't seem to go over well. That he might be technically wrong is incredibly nitpicky, and I am not persuaded that that was the issue the recruiter had.
It still seems like an extremely weird qualification to require, doubly so again for an intern level position: you would still be likely to pass over extremely qualified candidates who just never touched a "UNIX".
- foo101 9y agoAll I am saying is that when technology people like us are debating about terminology, we can cut the recruiter some slack, be nice to him or her and be more explicit in our communication to the recruiter. For example, instead of responding to "We are looking for experience in Linux and Unix" with "I have updated my resume with POSIX", respond with the following instead assuming you indeed have real Unix experience with a system like Solaris, "I have mentioned Linux and Unix more explicitly in my resume in the following manner: Debian (Linux), CentOS (Linux), Solaris (Unix) and FreeBSD (Unix-like).
- deathanatos 9y agoThat is something I would never do, because by doing so, I would by lying. Under the same beliefs as Stanley, I do not have experience with Unix. He does also, at various iterations, include UNIX, Linux, and UNIX-like on his resume, not necessarily at the same time. If there's a particular order, or casing of the word Unix the recruiter is looking for, he or she should just name it. > be more explicit in our communication to the recruiter. The long, technical response is the explicit response.
- foo101 9y ago> He does also, at various iterations, include UNIX, Linux, and UNIX-like on his resume. Where did you find his resume?
- deathanatos 9y agoIn the original post. I don't have his entire resume; I am relying on the image on the linked-to Imgur URL. I am interpreting the sections of the image that start with "SKILLS" as a screencap of his resume, my interpretation is that they are interspersed with the email chain in order to give us context as to what is on his resume, since it is material to the discussion.
- oculusthrift 9y agodo you want a job at one of the most prestigious companies or do you value being right on a minute detail more? I would have just added the word "unix" to my resume and moved on with my life.
- tdeck 9y agoPeople keep mentioning Solaris as a solution but as one recent college grad (2014) I can say nobody was really using Solaris anymore. Maybe other schools still have Solaris labs but we did not. Same with AIX and HP-UX. I really only know about these because I'm interested in tech history.