Upgrade your account to a Community Supporter account and remove most of the site ads.
Rocket your D&D 5E and Level Up: Advanced 5E games into space! Alpha Star Magazine Is Launching... Right Now!

Reply to thread

Message: <blockquote data-quote="Elodan" data-source="post: 3349684" data-attributes="member: 8006">I had an interview this past Monday which turned out to be a mini disaster (it felt that way to me).  The internal recruiter was supposed to send me the official job description and some additional information before the interview.  I had called and left a message reminding her that she was supposed to send me that information.  She never did.Monday morning I put on the suit (with the new shirt and tie my wife bought me.  I really hate dressing up; it's not me) and go to the company.  I'm supposed to meet with the recruiter and two gentlemen who run parts of the department I could be working in.  I meet with the recruiter and ask her about the company culture and benefits.  She tells me I'm not supposed to ask about benefits at the first interview, although she tells me this may be the only interview they may do before they hire me.  O-kay.  She is very nice and seems to be overwhelmed.  The company is planning on doubling it's size in the next few years.  Based on her description of the culture, I'm getting the feeling that this is not the place for me (I tend to make those types of decisions fairly quickly based on what my gut tells me).  The recruiter then goes to get the gentlemen.Both guys come into the room and I get the tag team interview.  Neither one is a database person.  They give me a brief run down of the department and then start asking questions to test my DB knowledge.  It was pretty funny as some of these questions were exactly the ones I used when interviewing DB candidates at my old job.  Then they start throwing out some questions about database administration (not my strong point and not what I want to do).  A little aside here, it's very easy to specialize in various aspect of database development and administration.  Some people just do design, some do development and some do administration.  I want to do design and development.  I'm getting the feeling that this job is not what I want to do nor is it what I was told it was by the recruiter.I then get to ask questions about the job itself.  I find out that the job is mostly checking the code that others write and doing database administration (something I told the recruiter I was not interested in doing when she first called).  There is already have an architect on staff and it sounds like the people pretty much are stuck in their silos.  The company is a little too corporate for my tastes.  Also, one of the big draws to this company is that they used SQL Server and Oracle, but they're doing away with Oracle (I want more Oracle experience).  By this point the gentlemen are pushing me to ask more questions but I've sort of realized that we're now wasting each others time and really have nothing else to ask.  Again, nice people.On my way home I stop at a local Walmart that's supposed to have Sugar Free Kool-Aid.  Can't find any on the shelves.  For some reason it's become increasingly difficult to find in eastern MA.  Just a little annoyance after the frustration of the interview.  I get home and send them a thank you letter emphasizing my strong points.  No acknowledgment to date.  That afternoon, I pull out my learn VB.NET book and start reading.Stan and Kyle I learned something today speech:I took this as a learning experience.  I realized that I always want to have a very clear understanding of the position description before I agree to an interview.  Another plus is that I had some interview practice.I'm not one to post much on message boards but I've found posting these things somewhat therapeutic (I can see why bloggers do what they do), so I'll probably update this post when something interesting happens.</blockquote>

Verification