PDA

View Full Version : Resume question



Zughiaq
04-10-2003, 05:40 PM
Hi,

How much of a programming language does one need to know before they can put it on their resume? For example, if I put "C" or "Java" on my resume, what kind of things do they expect I can do?

Also, I've seen some example resumes with TCP/IP on it. What is expected of someone who puts this on their resume? Socket programming or just familiarity with the protocols or something in between?

And what about operating systems? What does one need to be able to do in Unix or Windows before they can put that on their resume?

Thanks in advance.

dP munky
04-10-2003, 06:02 PM
>>How much of a programming language does one need to know before they can put it on their resume?

it just depends on how much you know, if youre new, i would put, something like learning c++ prog. lang. if not, and yorue pretty familiar w/the language go ahead....its not really a time thing, i would be prepaired to write a bit of code if youre going for a programming nothing extrememly difficult, they test to see how much you know about the language....they gradually build....the interviewer uses these to see how you think through problems

>>Also, I've seen some example resumes with TCP/IP on it
tcp/ip is just 1 particular network protocol, i gues i would put it, but the more different protocols you know the better......just an assumption(im not a networking guy)

blitzkrieg
04-10-2003, 07:44 PM
it's useless bud. No jobs anywhere :(

beege31337
04-10-2003, 08:38 PM
If you have to look up any standard constructs in the language I wouldn't put it on the resume.

But if you can write complex programs in the language and only use a reference manual for the rare stuff; then put it on the resume.

Some people put everything language,protocol,OS,etc. that they have ever used and they look like idiots when the interviewer asks them about it. Or even worse, they get a job and the first day they are expected to use what they listed.

I've written programs in Prolog, but Prolog is not on my resume.

Xei
04-10-2003, 11:18 PM
I don't list Protocols or RFC's etc.. in my Resumes. I just put what I'm qualified for, I don't believe in the sucky $$$$ like "and I want to work for your company because I have great respect for it, and I am easy to get along with, and I am a super leader" seriousely, screw it. All they want to know is what your qualified for, they know you want money, and they want service. On my resume, I put something like: "Experience with C/C++, Windows API, and am capable of producing Win32 applications for small business solutions. Limited knowledge in x86 Assembly." Things like that. Go ahead, put it on your resume; I assume that you likely arn't going for a Programming job if you're asking about 'if' you can put it on, but if I go for any computer-related job I put that on. Then they say something like "You're determined and we would love to have you, but you're too young and honestly it doesn't look good on our insurance(which is true). Please, come back when you're 18." Or else they(the employees who are 'supposed' to forward your resume) just kindof throw your resume in the garbage because a job is lined up for another employees friend.

BTW: The TCP/IP thing usually has to do with people who have taken a course on it for Unix or something, usually has to do with their qualifications on Networking.

Zughiaq
04-11-2003, 11:16 PM
Actually, I'm a soon-to-be college graduate (CS major). I just used those as examples. The problem is that in almost every semester I've worked in a different language (C++, C, Assembly, Scheme, python, perl, java) and the only one I can do any substantial programming in is C, so my confidence in my programming abilities is not so high. And, aside from never learning how to do any OOP (even in my C++ class), I used Java in probably the most advanced project ever (a secure socket server for migrating clients, used the java for it's built in SSLsocket class, much easier than importing toolkits in C). I have taken a networking class, I was curious as to what is expected of someone who puts that stuff on their resume.

I'm still curious about the OS's. I can do a bit with Unix, I just want to make sure it's enough. What about Windows, since all the PC's I used have that?

I probably will wind up with a programming job (software engineer most likely) since it's the only job I've seen that doesn't require 2-4 years experience (which I don't have).