Because of the high maintenance needed to monitor and filter spammers from the RF Cafe Forums, I decided that it would
be best to just archive the pages to make all the good information posted in the past available for review. It is unfortunate
that the scumbags of the world ruin an otherwise useful venue for people wanting to exchanged useful ideas and views.
It seems that the more formal social media like Facebook pretty much dominate this kind of venue anymore anyway, so if
you would like to post something on RF Cafe's
page, please do.
Below are all of the forum threads, including all
the responses to the original posts.
Post subject: What should a Fresh Graduate (MS EEE)
do with no experience Posted: Mon Aug 01, 2005 4:37 pm
seem to be asking for experienced people. I recently grdauted with MS
in EEE and took Microwave and Wireless courses. The only job positions
fresh graduates seem to be getting is drive testing.
IS that really
how I should be starting my career in RF ?
Also, It would be REALLY
REALLY helpful for fresh grdautes like me if people could post the kind
of Questions they faced in job interviews or the kind of questions we
can 'expect' for a RF/Wireless position.
if not specific questions,
it would be helpful if the experienced people could post the general
areas a fresh graduate going out there in the job market be familiar
Thanks in advance and please let us make this Forum more
productive. (Complaining is good too but it could be constructive complaining
Post subject: hiPosted: Tue Aug 02,
2005 1:04 am
what makes you different than the rest?
are you special?
Post subject: Posted:
Tue Aug 02, 2005 4:43 am
Good question !
Personally, my studies in electrical engineering with specialisation
in RF were already hard for me. Although I studied 40-45 hours a week
I just finished with average marks and the few spare time which remained
I didn't want to spend with electronic stuff, that's why my practical
experience are very rare.
Other guys just studied 30 hours a week,
got all the 'A'-marks and programmed whole operating systems during
their free time (a friend of mine invented his own MP3-format and has
got patents on it....) They even had time to party ....
Post subject: Posted: Tue Aug 02, 2005 9:04 am
Joined: Mon Jun 27, 2005 2:02 pm
As I mentioned in
previous posts that discussed this common problem of fresh graduates,
drive_test is the best way to begin your RF career. Because it gives
you the opportunity to acquire hands-on experience that will allow you
to progress to R&D jobs. If you begin doing design from the start,
you will lack a lot of fundamental knowledge and experience that you
will gain from a starting position doing testing work.
Post subject: Posted: Tue Aug 02, 2005
Joined: Mon Jul 18, 2005 4:31 pm
Location: Baltimore, MD
Don't allow yourself to get
too desperate so that you take whatever crappy job comes along. Taking
a first job that doesn't give you the experience that you need could
handicap you for your entire career.
Post subject: Posted: Mon Aug 08, 2005 12:18 pm
Joined: Thu Aug 04, 2005 3:49 pm
Feel free to send me your resume. I am not a headhunter.
I am the Sr. RF MGR in charge of hiring for my team here at Sprint (see
my other post with a description of what we are looking for).
If you love
CDMA, you have to come join my team!!!!!!!
Post subject: my experiencePosted: Mon Aug 15, 2005 1:16 am
Joined: Mon Aug 15, 2005 12:55 am
I like what Kanling said. To add to it... be carefull at what you get
good at. If you take a job as a production, applications, or non RF
designer, it can be quite difficult to move later on.
that I've noticed older RF engineers are weak at is programming. Be
it test code (VEE or Labview), C++, digital stuff etc, Utilizing current
tools to improve the efficiency of the design flow can allow you to
contribute immediately where the older engineers haven't had the time
or inclination to go. Some examples:
1.) Replacing the old Qbasic
test code with a flexible, Agilent VEE or Labview interfaces. I myself
did this and was able to quadruple the efficiency of our lab almost
6 months after I was hired.
2.) Rewriting that old Fortran code
with some slick C++ Windows interfaces that run quicker and have more
In short, hit em where they aint!.