--- Elaine <http://www.hotmail.com/~et> wrote: > I read through the site. It reminds me of similar things I picked up from > DBM. The key thing is to have a good sales pitch -- your selling points. > Also, the other site you gave, from the engineers, said something I've heard > many times but haven't figured out how to solve -- "find out what kind of > technical problems a potential employer faces and then contact the manager > in charge", and, of course, offer solutions. Ah, this is hard to do on-the-spot. But, it's worth a try. After the first 100 companies, we'll probably refine things. > I suppose you could find > every possible article about them but you really need to know someone inside > that department, not just someone in the the company in general. If we just > use a general sales pitch at least we'll find out for sure if they use > unix/linux, then we can hone down the list. With large companies, articles will be available. Smaller ones may not get any press in which case we'll have to ask. > I'm going to pass this by Retech -- I see him again Tuesday afternoon. He > talks to a lot of employers so I'll see what he says. You may as well. The cited book on that web site is pretty old (1993) so I'm not sure how relevant everything is to these times of despair. (On the other hand, we were still in George I's recession at that point, so...) > I would definitely figure out ahead of time exactly how to get there but I > think the possibility of a request for interview on the spot is very very > remote. They might want to talk further there on the phone but I think an > immediate on-site interview is remote unless you offer exactly what they > need. We can talk about that some more. Yeah. Actually, I was thinking about that more. With companies which are physically far away, we won't be able to interview there anyway without some logistical thinking. I suspect just racing through to find whether they have any jobs would be more fruitful for the companies that are less desireable.