Honourable sir /mam, i am graduate in electronics and communication engineering but i can't find core job can anyone suggest me what to learn to on electronics so that i could do my job perfectly and correctly.
My advice would be to go off and do a Ph.D. in Physical Chemistry. Winfield Hill started off doing a Ph.D. in Chemical Physics.
I doubt that this would actually work for you - the problem comes more in finding the job than in finding out the extra information on electronics that you need to learn to solve the problems that the job you find requires you to solve.
What do do you means by a "core job"? If anybody is prepared to hire you at a rate of pay that reflects your training, they will probably want you do do something that exploits that training. You are unlikely to see the connection until the nut and bolts of the job are spelled out to you, and some new graduates do have very unrealistic ideas about what a job in their speciality involves.
During the university milkround, one interviewer asked me my interests and the threw a question I wasn't prepared for: "are you just saying that because you think that's what I want to hear?"
After a short pause I answered something to the effect that "no, but that's what I enjoy and I am looking for a job like that"
I spent 3.5 years at that company, and was thrown in at the deep end :)
UK University milk rounds may be done by more competent people than their Australian equivalents.
I got my first job after graduation with a company called Plessey Pacific. I'd had a milk round interview with their personnel officer, who started the interview by reading out their company brochure, which I'd already read, When I pointed this out, he took this as a hostile reaction and ended the interview.
I got the job by reacting to an ad in the newspaper, and got interviewed by the people I ended up working for. The first question was "How does Xerox machine work". When I told them, the reaction was "you've got the job", which I took to be a joke, but wasn't. The personnel guy seemed to have forgotten the milk round interview when I did get to talk to him.
Probably not; only one interviewer raised that question.
An excellent bozo filter - for you.
I went to a company and spent a long time explaining all the hardware and software I had done, and why straddling the boundary was necessary. At the end the bozo asked me whether I was "really hardware or software", and offered me the minimum he thought I would accept.
IIRC I applied for 11 jobs, got interviews for 19, including one letter that I interpreted as "we'll give you a job".
The excess interviews were, unsurprisingly, for GEC/Marconi who just wanted warm bums on (cost-plus) seats. I went to half a dozen and they were very useful: I /knew/ which company I didn't want to join, and why others were better :)
I had two job interviews in succession. First one, I said that I preferred using tubes because they were cheaper and harder to blow up than transistors. The guy sniffed and said "That won't do" and dismissed me. I told that story to the second interviewer who knew the first guy, laughed, and hired me. I designed $200 million worth of stuff for him.
I always regarded interviews as two-way processes. I always found it strange that some interviewees presented themselves as supplicants. interviewees that asked me interesting/difficult questions got job offers.
I was once offered a job, declined, they increased the offer by 10% then another 10%, and I accepted a different job for less than they offered. Never regretted that decision!
Oh, you have a polite anodyne conversation with such droids. All they can do is ask the standard bullshit questions such a "why do you want to work here?". Sometimes it was /very/ tempting to give "unexpected" answers.
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.