serenity courage wisdom
Usually it's serenity that gets me, but I'm working on the courage part at the moment.
I had a phone screening/interview yesterday with a *really* cool company. It's a small team, with everybody on site(the company is global, about 3000 employees total), it's closer to the type of work I used to do than what i'm doing now. The guy I talked to on the phone seemed nice, we communicated easily and seemed to be on the same page. The catch is that it's more software oriented than the rest of my background. You can approach chip verification as an extension of a hardware project, or you can approach it as a software project. Most of my experience has been the former, although I do code in Perl, C and C++ on occasion. As well, even the "hardware-y" verification languages are starting to use software concepts. So I *know* how to do this, I just haven't really done it, per se. The suggestion is that I study up on my software/C++ knowledge and go for a real interview. Which is freaking me the heck out. But I did it for my Intel interview: I hadn't a clue about processor architecture when I applied for this job. So I read some papers on verifying CPUs and read a lot on processor theory and I aced a 4 hour interview. So can someone please tell the scaredy-cat little person in the back of my mind to stop running around screaming like a maniac!! :)
I had a phone screening/interview yesterday with a *really* cool company. It's a small team, with everybody on site(the company is global, about 3000 employees total), it's closer to the type of work I used to do than what i'm doing now. The guy I talked to on the phone seemed nice, we communicated easily and seemed to be on the same page. The catch is that it's more software oriented than the rest of my background. You can approach chip verification as an extension of a hardware project, or you can approach it as a software project. Most of my experience has been the former, although I do code in Perl, C and C++ on occasion. As well, even the "hardware-y" verification languages are starting to use software concepts. So I *know* how to do this, I just haven't really done it, per se. The suggestion is that I study up on my software/C++ knowledge and go for a real interview. Which is freaking me the heck out. But I did it for my Intel interview: I hadn't a clue about processor architecture when I applied for this job. So I read some papers on verifying CPUs and read a lot on processor theory and I aced a 4 hour interview. So can someone please tell the scaredy-cat little person in the back of my mind to stop running around screaming like a maniac!! :)