February 23, 2006 at 9:46 am
The last thing is that I tend to go into jobs at this stage of my life looking for a long term fit. I want a job to last me forever, so I really am open and honest to try and ensure I make a good decision. If you are looking for a shorter term engagement, you may or may not disclose that. A one year target might end your interview immediately, but I have told interviewers that I was looking for a 3-5 year job and I'd evaluate it as I went along.
I may have misunderstood the lines above, but the world has definitely changed if 3-5 years is considered 'forever'.
February 23, 2006 at 10:53 am
Thanks for the complements and hopefully this will help some people.
David, you missed it slightly. Early in my career I had a 3 year time frame, looking to gain different types of experience, new industries, etc. The last 7 or 8 years I changed and have been hoping to find a job that I can do for 20-30 years. Hasn't worked out yet, but I'm still hopeful.
November 13, 2009 at 5:33 am
Hi ladies and gents, sorry about digging up an oldie...
sheepoo (2/23/2006)
Here are my two cents:We spent the last 4 months looking for a Business Analyst who would come with a strong SQL Server background. We came across a person who was the Vice President of the local SQL Server Group. He was very fluent in his replies and came with a tonne of experience. However, one thing which nagged me during the interview was whenever he was asked a technical question he would circumvent around the techincal details(and we realized later that he was very good at doing that ).So we called him in for a techincal interviews and it transpired that other than knowing some simple SQL he was not able to answer <i>any</i> question <img src='images/emotions/shocked.gif' height='20' width='20' border='0' title='Shocked' align='absmiddle'>.
Needless to say, we did not hire him and were more strict in our question from that point onwards. We ended up hiring a person with a lot of <i> Oracle</i> experience and he is picking up really very well in our environment, which is purely SQL Server
Lesson Learned: Do not go by technical experience only; good candidates can usually use their experience on one tool to master another.
This is really interesting to me. We're currently looking to recruit a SQL Developer and two guys so far have made it through to the second stage. I have one this afternoon and one on Monday. Monday's guy has a typical set of SQL skills and experience, mostly in finance and I'm looking forward to meeting him, however, the guy I'm seeing this afternoon is mostly a skilled DB2 DBA...
I was told by someone who's seen him in the first round that he 'understands data'. Is that enough? We're looking for someone who can pretty much hit the ground running in a couple of projects with aggressive timeframes, one of which is a complicated BI development where getting your hands dirty in lots of complicated SSIS ETL is unavoidable if we're to get it out the door.
Some points to note, one of our legacy systems (and an early main source for the DW) is on AS/400 / DB2. And the last guy that filled the post started in March and is gone already, so anxious to get the right person.
What do you think?
--------
[font="Tahoma"]I love deadlines. I like the whooshing sound they make as they fly by. -Douglas Adams[/font]
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply