Re: Case study for interviewing Oracle DBA

>...he decided that recruiting me would be a good thing for his
>current company. Okay, fair enough, we skipped the HR initial crap,
>saved the company money (no recruiter's fees). EXCEPT, HR still has to
>be in the process at some point, and now they are annoyed with both me
>and my friend because "we did this backwards". Do I start the
>interview with HR at a disadvantage? You bet. Will it hurt me? Still
>to be determined, we are still in the "trying to find a date that
>everyone can manage for the interview" stage.

I guess I'm not sure what your point is.

The hiring manager has decided to hire you. HR might gum it up, might not.

Had you gone the other path (send resume to HR and hope friend ever saw it), do you think your odds would have been better? Couldn't HR have mucked that up too?

People and organizations do **not** have von Neumann (sp?) architectures that support algorithms that guarantee the same result for the same input. As a profession, we just need to "get over it" when it comes to this issue.

No matter what course of action you take with another person or organization, there's a chance that it will go well and a chance that it will go horribly. It's all a matter of determining what improves the odds and adapting to circumstances - particularly when event outcomes don't match what you expect or want.

So, when the HR interview comes around, smooth those ruffled feathers, be charming, point out the advantages to the company that you mentioned earlier, and don't give them an excuse to reject you. And hope for the best, because it's possible that no matter what you do, they'll screw it up for you.

--
http://www.freelists.org/webpage/oracle-l