June 7, 2013 at 7:55 am
Hey guys! First, I apologize if this is an inappropriate question for this subforum, but I could use some advice. Next Wednesday I have an interview for a junior level SSRS reporting job, and I was curious if anyone has been in my shoes with such an interview. I will be interviewing with the project manager and a SQL developer, and this will be my first technical interview I have ever had. I nailed the phone interview (~25min conversation) with confidence and ease, and I know I'll be able to build up a personal rapport as I'm all around a great interviewee. Right now, though, I'm primarily concerned with the possible questions they may ask.
I have over a year and a half experience in creating SSRS reports and writing complex stored procedures, and I am very confident in my skills and abilities (I have singlehandedly developed the entire report catalogue my current company uses, and it employs 200+ complex statistical and auditing reports), but I am worried that I will not be able to articulate when they ask particular questions. I am very much so a hands on person, and I know incredibly well how to DO the tasks and I can work my way around SSMS and BIDS fluently. However, I can't help but worry I'll fumble over my words and not seem as knowledgeable as I really am, or that they'll ask a very simple question and I'll just be dumbfounded while I know the intricacies when it's in front of me.
So, is there anyone out there that has interviewed for a Jr. SSRS developer position or someone versed in the interview process that can offer me some tips for the technical interview? What exactly should I expect?
Also, should I print out a few of the reports I have created and bring them to the interview as examples, or should I can that idea?
Thanks everyone!
June 7, 2013 at 8:10 am
Grats on the interview and I hope it goes well for you.
I can't say I've ever interviewed for a SSRS job but I would think the usual interview policies would still be effective.
Be honest, don't sugar coat. If you don't know, say you don't know but also provide a way you might go about solving the problem.
Provide answers that communicate an understanding of the subject, implementation of ideas, and problem solving. They might have a test environment for you and ask that you create a quick report for them. If that's the case, great! If not, use some past work as examples ("When I ran into a similar problem in the past, I solved the issue by _____").
You can bring a few reports, provided it's not proprietary or sensitive information, and keep it in your planner/briefcase/folder/pocket. If they ask for some of your work, viola! But I wouldn't offer it up front.
That and donuts help. Bring donuts for them.
Good luck!
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply