Dismiss Notice
Join Physics Forums Today!
The friendliest, high quality science and math community on the planet! Everyone who loves science is here!

What exactly am I qualified for?

  1. Sep 24, 2012 #1
    Here's a picture of my resume:


    I tried to black out some things but you can probably figure it out if you do a lot of digging. Anyway, it doesn't. I just don't know what kind of jobs to apply for. No, I did not finish graduate school. I flunked out. That was almost a year ago as you can see. From then, any job I've looked at I just didn't feel I was qualified for. Oh sure, I applied anyway, but never heard back.

    Engineering? Programming? Data analysis? No idea where to even look.

    Currently I am learning more programming and will jump on an open-source project so I can tell potential employers that I'm actively learning on my own, enjoy programming (which I do), and hopefully it will show that I am capable. But this can take a long time before I can make any real contribution to a project I think, and I don't even know if that's my best option.

    Can anybody please help? Or at least point me somewhere where I could figure this out? I did career counseling in my alma mater a few months ago. Nothing specific came out of it, just general resume building techniques and job search strategies. But nothing like "Oh yeah, with your skill set you should look at [career X]."

    I'm not picky. I went into physics because I enjoy so many different things and physics let me experience a bit of everything. But I just don't know what I should be doing at this point.
  2. jcsd
  3. Sep 24, 2012 #2
    Well, start with your first job. You fixed low noise amplifiers. That should get your foot in the door for RF design work. You might also get some traction working with industrial engineering processes. Places like nuclear power plants are always looking for entry level engineers to pick up from the previous generation.

    The truth is that a physics degree is very broad. Your skill set could serve very well, however, in an engineering/maintenance environment. Many graduate from schools who know nothing about how to solder, let alone how to configure an oscilloscope properly.

    Consider working at a radio station or at a telecommunications provider of some sort.
  4. Sep 24, 2012 #3
    Here's the thing: it wasn't so much a job as it was undergrad work over the summer. "Fixing" the pre-amps was a matter of my supervisor telling me "Replace these parts here with this new set I'm giving you."

    I've been told the RF industry is in desperate need of people, but when I look at jobs in the field, say this one:

    https://ericsson.taleo.net/careersection/usa_corporate/jobdetail.ftl?lang=en&job=897888&src=JB-202 [Broken]

    I just feel woefully incompetent. Sure, I know a good chunk of those things, but nowhere near all. Most jobs in this area specifically require knowledge of how WiFi or some other protocol work and I have absolutely no experience there.
    Last edited by a moderator: May 6, 2017
  5. Sep 24, 2012 #4
    Bring that resume to a career fair at your university. That's where the entry level jobs are. Look for big companies first. Larger companies will often advertise their career fair attendance schedule.

    Look, you're coming in at the bottom. Your degree is simply a foot in the door. Where I work we would train someone for at least a year before we would give them tasks to do on their own, and then we'd monitor and guide them for an additional two years before we'd even think of giving them a significant project to work on by themselves. There is lots of mundane things to train you with: First aid, CPR, Arc Flash, confined space atmospheres, SCBA gear, climbing and rescue, defensive driving, financial policies, procurement card use... This stuff gets ridiculous after a while. And then there are the technical courses we take every year. Nevertheless, after having seen friends get hurt or killed, sometimes through no fault of their own, you begin to understand why this stuff is so necessary.

    You owe it to yourself to learn for a few years, perhaps move laterally or up in the organization, and then consider how you might want to do a startup of your own or whether you want to do something completely different.

    Contact the HR departments of some major employers. Tell them you're fresh out of college with these sorts of skills, and then see what they may have.

    You might be surprised where you land.
  6. Sep 24, 2012 #5
    Your resume (not your skills or abilities) STINKS!

    Take off the soldering, o-scope, and power tool stuff. Makes you sound like a lab technician/machine shop monkey.

    ONLY put the high level work, nuclear publications etc.

    Get help rewriting the CV, it's really bad.

    If this were Faraday's resume would you expect it to say "proficient with a coil winder and anvil"??
  7. Sep 24, 2012 #6
    a resume =/= CV. No one cares about publications in industry. What they care about is the ability of you to provide profit to the company. You show that with specific skills that you have. Machine tool use is a specific skill. If you can provide profit to the company as a lab tech, then you're a lab tech.

    On the other hand a publication shows *literally nothing* in industry. What are they going to do with a publication? Put you as a BS holder into research? Its like joining the army and wanting to be a general. And then you leave out the entry level stuff and you're *totally* unemployable.
  8. Sep 24, 2012 #7
    Agreed- the point was do you want to be drilling holes in the machine shop or doing algorithm development for a commercially useful simulation?

    The publications are evidence of a high-order technical skill. Knowing how to drill holes isn't.
  9. Sep 24, 2012 #8
    Consider dropping the tools/oscilloscopes down to the bottom under a new header "other skills" or some such. I don't think you want them displayed so prominently for the types of jobs you seem to be seeking, but they're definitely valuable skills to have.

    As far as that job description, it's kind of whack. I mean they're asking for an entry level engineer that "leads large engineering teams", "provides direction... for engineering projects/programs," etc. The job functions don't seem appropriate for the desired education/experience. Looks like a "wish-list" to me. Might as well apply and tell them what you know and what you can do. They will never find someone that can actually do that job description fresh out of school. Maybe they'll like you enough to throw you in the fire... which is a wonderful way to learn.
  10. Sep 24, 2012 #9
    What you put on the resume is going to depend a lot on what sort of jobs you are applying for. If you are mainly applying for software jobs, your resume isn't all that good (Note: I'm physics PhD that now works in software). Too much of it is spent discussing lab-work related physics skills, which to be blunt are basically useless in this context. Emphasize the programming aspects of your different roles in both grad school and undergrad would be more helpful.

    Some other things among many that would be useful to convey:
    - Did you work on any code with others? That is useful experience to emphasize if you have it. A key aspect of software development is producing maintainable code that others can work with.
    - In a similar vein do you have any experience with version control systems (e.g. subversion, git, etc)
    - How many years experience do you have with the languages you know?

    Also if you didn't take any basic data structures or algorithms classes in undergrad try to pick up a at least some textbooks to go through. You're to get a lot of questions related to this in interviews.
  11. Sep 26, 2012 #10
    Thanks for the resume tips. I'll update it and give you guys round 2 if you aren't sick of me yet. :P

    This is what I'm talking about. I have to make up for months of education that I didn't get in something like a few weeks? That's what makes me think maybe programming isn't the bet career choice for me. I'm just too far behind.
  12. Sep 26, 2012 #11
    Fear not!

  13. Sep 26, 2012 #12
  14. Sep 26, 2012 #13
    Is that going to fly on a job interview?

    "Have you taken any classes on algorithms?"

    "No, but I studied on my own."

    Or will they give me an actual test? You really have to understand here, I want a job ASAP. I don't have 10 weeks to sit around and do homework problems.
  15. Sep 26, 2012 #14
    Not likely...

    Generally it will be questions or tests. Every (in person) programming interview I've ever been through involved questions about my knowledge, doing code on a whiteboard, and some sort of actual programming test.
  16. Sep 26, 2012 #15
    Is it something reasonable or something very specific? Like... when programming in C++ I always have MSDN open. I know there exists some function call that I'm looking for... but I can never remember the details like what to pass it or whatnot.
  17. Sep 27, 2012 #16
  18. Sep 27, 2012 #17
    It's not usually silly questions like the signature of some random method in some library that can be answered by google.

    I've gotten some questions like "Can you explain the difference between allocating something on the heap versus the stack in C++". Most question are more like you are given a problem and they ask you how would you solve it. The interviewers want to see how you solve problems, and how you design software.

    For the algortihmish questions it is usually something like:

    They give you a sorted binary tree and you have to write on the whiteboard code for printing out the values in the nodes in order. Using recursion and then not.

    Design a stack for holding values where you can always get what the maximum value is in constant time.

    This usually only has to be done in pseudo code or language of your choice.

    There is basically always a real coding test to where they give you a set of requirements and some time limit to complete it. In my experience you can choose the language as long as you provide instructions for compiling/running it. Sometimes there are platform requirements of some sort (e.g. Linux/OS X vs. Windows). Note: I've worked in basically a purely Linux + OS X environment (both in grad school and afterwards), so I don't have a good feel if its different in the Windows world.
  19. Sep 27, 2012 #18
    Okay looks like software engineering is out of the picture.

    I'm mostly at lvl 0 or 1, with a few on lvl 2 and I think 2 might even hit lvl 3.

    So it looks like I shouldn't even bother with professional software development. I guess I'll look at QA testing, though I've seen requirements for that field too and the stuff they use is even more foreign to me.
  20. Sep 27, 2012 #19
    I think that the message to take away from those good advices, is that it would be wise to prepare adapted CV's for different types of job applications (assuming that you are interested in more than one type of job).

    Still, that is not what you were asking. It appears that you are qualified for a number of generic engineering jobs as well as for assistant jobs in teaching (electronics or mechanics lab?). However, you seem to be more interested in programming. My guess is that there is a mismatch between what you're most interested in and what you really would like to do.

    And perhaps there is a misunderstanding: in many places general jobs are not advertised, because some companies and universities receive plenty spontaneous applications (compare post #4). Did you try that?
  21. Sep 27, 2012 #20
    No no no, I'm not more interested in programming, I just thought that's what I was better at. I think I was wrong.

    I only briefly attended a career fair once because I was notified of it very late (I wasn't a student at the time so nobody really told me). Next time there is one, I'll be sure to go.
Share this great discussion with others via Reddit, Google+, Twitter, or Facebook