varun213,
When I graduated from university (BSc. Mechanical Engineering), I wanted to work in a field that dealt with the flow of oil/water emulsions. I loved fluid dynamics. I ultimately started off with an EPC firm that specialized in heavy oil recovery - the best field for that very thing. However, I didn't solve an emulsion flow problem since the day I was hired; 33 years later, I still haven't. I ended up doing a whole bunch of stuff that had nothing whatsoever to do with what I wanted to get into. Ironically, most of my time in my first two years was spent doing compaction tests with a nuclear densometer on irrigation canal embankment. After that, I spent about 10 years doing P&ID and systems design for Utilities and Offsites (CW / Stm / BFW / Cond / IA / UW / PW / FG / Flare, etc.). I learned CAESAR II when the latest release was V. 2.01 for DOS and to solve a 200 node system took 4 hours to code the data in and an hour to get the output from a Turbo XT with an 8087 math coprocessor after you pressed the RUN button. Interestingly, I was self-taught; my boss at the time told me to come into the office at night and steal the software and install it on my machine, since the stress guys were difficult to work with and I was just an innocent hard working dummy. Then I spent ten or so years as a project engineer running projects and coordinating the work of others, but not doing much of the hard core work myself. I migrated back into detailed mechanical engineering by forming and appointing myself as the lead of that department when it became clear that as projects grew in size to some magic TIC threshold the Project Engineer could no longer effectively execute the project without a Mechanical discipline. After 5-7 years of that, I got bored with it and transitioned into a role of a quasi-process engineer who, although I can't even *start up* HYSYS from the welcome screen, I basically serve as the check and balance between Process, Mechanical, Instrumentation and Controls.
I didn't plan any of it, and I didn't see any of it coming.
Nowadays, I find myself in a role where I might be doing stress analysis today, P&IDs tomorrow, sizing relief and control valves the next day, writing specifications the next day, and doing bid evaluations on compressors the next day - just before going into a HAZOP for a week after that. Never saw that coming either, and often by the weekend, I find myself coming home wondering what the heck happened? All I know is, when there is a problem, I'm usually involved with solving it - it doesn't really matter what the problem might be.
I have still never solved a single flow problem with oil-water emulsions. Or maybe I have. I don't know, I can't remember.
I agree with you, it's hard to figure out what to shoot for or hone in on at this stage in your career. What I can say is, just strive to be "the guy who solves problems". Pick and aim at a field of interest, certainly, but don't close your eyes to what else is out there.
When I graduated, my idea was to pick the work I wanted to do and then move to live where that work was. A good friend of mine, though, she said to pick where I wanted to live, and then go and find a job there. In retrospect, my opinion (and it won't be shared by many in these fora) is that my friend's plan was better than mine; I should have listened to her. Your posts suggest that you might be more "lifestyle" slanted than "work content" slanted - and that's perfectly fine. Again, whatever you do, just try to be involved with solving whatever problem comes your way.
I grew up just north of the border from Seattle...yes, the rain kinda sucks...but unlike where I'm at now, I never had to spend six months of the year shovelling rain.
