QuoteOriginally posted by: mynetselfI'm also not claiming I am a Fortran guru since I am not.How do you know you are not?QuoteWhat I'm trying to convey is that I know the basic stuff and am working on improving it.There's no need to convey that. If you have a physics Ph.D. and have done QFT and have done Fortran programming, then I can assume you can learn some C++. You do need to talk about exactly what Fortran programming you have done. If your Fortran experience includes working on 100,000 line QCD code, then I'll assume that you can pick up C++ even if you know nothing about it now.I should point out that the reason C++ skills are in demand has nothing to do with C++. It may be that you are not going to be programming in C++ at all, and it may be that we have a fortran system for you to babysit. The reason people look for C++ is that it's assumed that if you know C++, then I can hand you a language that you've never heard of, and you won't freeze.QuoteAnd I guess I'm waiting to find the hiring manager that will be happy with that.You have to remember that it's not a game between you and the hiring manager. The real competition is between you and the other resumes in the stack. Why should the manager pick your resume over the next one? The odds are that if you get picked it's *NOT* because you are willing and able to learn C++, since it's likely that the eight other candidates in the list are willing and able to learn C++. If it's a job that requires C++ coding skills, you don't have them and some other person does, you lose. On the other hand, if it's a job that requires the ability to do QFT, you are going to beat out someone that just knows how to code C++.QuoteI guess I'm just too honest about my skills I really am not comfortable in claiming I can do something that I can't. I might be wrong and missing opportunitiesState facts. Don't state conclusions. Let the reader figure out the conclusions. Something that you need to be aware of is that you will frequently be asked to fix problems that you have no expertise in, and part of what people in this field are looking for is for people that can learn quickly. You may be asked to debug a computer algebraic system written in common lisp, and the fact that you know nothing about computer algebraic systems and common lisp is not an excuse. What you don't know, learn.The other thing is don't dwell on what you *don't* know. Dwell on what you *do* know.QuoteAnd once you stick to those principles, a number of other factor beyond your control come in.You chances of getting any particular job is quite low. Maybe one in 20. However, if you put out enough applications and there are enough open positions, the randomness factor decreases considerably. Whether you will get a *particular* job is largely a matter of luck, but luck is much less important a factor in seeing that you get *a job* out of the hundred or so you interview for.QuoteAs for the job description and the hiring attitude, it seems to me that it's a bit like saying: I want a smoking hot woman who is also smart, funny, knows how to cook fantastically and is great in bed;And the key bit of information is that you know that someone is looking for something, and here is the e-mail address. Everything else is unnecessary information. Any time, you post any sort of job ad, you are going to be *FLOODED* by resumes, and the vast majority of those resumes (80%+) are going to be from people that are clearly unqualified for the position. This is why its sort of useless for companies to post exact requirements, and why companies don't even try. If I post *PH.D. REQUIRED*, then you are going to get a flood of resumes that have bachelors degrees. Since I'm going to have to dig through those anyone, it's sort of pointless to post any requirements.QuoteWas just trying to say that it seems to me that a bit of hype on the resume seems to be more successful as an approach than just by being very honest about it.It a communication issue, and not an honesty issue. You have to be very honest, but there is a particular way of communicating information in resumes, and it's like mastering a new language. You also have to look at things from the point of view of the person reading the resume. You are just a piece of paper to them, and just one resume in a stack of twenty. This is why hype doesn't work. If you just write C++, stochastic differential equations, and monte carlo in your resume, then it's just going to look exactly like every other resume in the stack, and if you write C++ with no other supporting information, then I'm going to assume that you just picked up a book on Amazon and did a few exercises here and there and you read Hull.As far as communication, you have to put in the resume things that people can't just randomly add. If you put that you are learning C++, that's not useful information. Who *isn't* learning C++? If you say that you are an "expert" then I have to rely on your judgment, which is hard thing to do because I really don't know you. If you say that you've worked on CFD systems with 100,000 lines of code, that's something people just can't make up at random.The other piece of FYI, information is that traditionally physics Ph.D.'s are very strong in differential equations, but rather weak on statistics. If you have done anything statistical in your Ph.D., that would make your resume more interesting.