SSRS Interview

  • I am attending the interviews as a SSRS Report developer

    I put 3 years(2 Years Banking and 1 year insurance) experience in my CV

    I attended 4 Interviews

    In interviews I successfully completed the technical tests(2 interviews technical and chi chat other 2 only chit chat)

    in 4 interviews they are asking about what type problems you faced? and how you overcome it?

    what are the real problems we face in the job?(technically and non tech)

    can any one give the replay with 4,5 examples.

    you will be a my life saver

    Thank you

     

     

  • They are asking about your experiences and what you faced and how you addressed it. The best thing to do is give that more thought about different challenges you had on the job and how you worked through those issues. Even hitting a point where you couldn't figure something out and posted a question up here says something about how you handle some situations. Interviewers want to understand you and how you handle problems.

    Sue

  • With that much experience, you should already have encountered plenty of relevant technical and organisational issues as part of your work. Go ahead and use those!

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • Hi Sue and Parkin

    I don't have any real time experience.I  recently learned it.now I am applying the jobs with 3 years experience.please help me#

    Thanks

  • So you are asking us to invent lies for you? Sorry, but I won't do that and I doubt that Sue will either.

    Have some professional integrity and tell the truth ... you have the technical skills but not (yet) the practical experience.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • If they already know you have limited experience with SSRS development, they want to know what you are going to do when you are facing challenges or are stumped. They really don't care what Phil or I (or anyone else) would do. Firing off a list of challenges and how they were handled does a disservice to you as well as those you are interviewing with since it's not a reflection of you or how you would handle things. There is no right answer to something like that but your answer is the one they are interested in. Not anyone else's.

    Sue

  • Please tell me you're not lying on your CV.

    OK, here's a real world experience that represented a challenge to me. You can use this on your next interview to explain your CV.

    Damn, this is embarrassing. I lied on my CV.

    I was two years into the IT job and wanted to do more. I had been working primarily through word-of-mouth consulting gigs. I was making really good money, but it was inconsistent. So, I started applying to jobs I was qualified for. Most of the jobs wanted you to have a degree, which I didn't have (still don't). So, I just put one on my CV. I got an interview with a great organization for a great job. I passed the technical. I passed the personal interview. We negotiated salary and I was going to be doing cool stuff. Then, they did a routine check on my CV to ensure the stuff I put there was real. All of it was, except the degree. BOOM! No job. Despite the fact that I was qualified and, I quote, "was the best person they had interviewed." Because of the lie, I lost the gig.

    There. Use that.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • As already mentioned - you don't want to pass other people's experience off as your own. I would never hire someone who did this nor would I respect someone who hired me after doing that.

    When I was in college and working full-time as a IT help desk guy I would update my resume with any new hot technology I worked on. JD Edwards was super hot back then and we used it to manage our service tickets so I added JD Edwards to my resume. I wasn't trying to fool anyone - I thought that being a daily end-user qualified me to include JD Edwards on my resume. Once I  uploaded my resume to the job sites I was using back then (Monster, Dice, CareerBuilder) I started getting flooded with calls with recruiters and HR people looking to hire JD Edwards programmers and admins. I didn't know the first thing about either. This was a honest error in judgement on my part but it really hurt my reputation with people who felt that I wasted their time.

    I interviewed a lady once, a couple years later, who was 110% qualified for the position; she knew her stuff and was impossible to stump. I was studying Unix at the time but we did not use it professionally where I worked. At the end of the interview, while engaging in small talk, I asked what she had done with Unix. It was an awkward change in the conversation because she had no idea what Unix was - like at all. She couldn't tell me if "Unix" was a kind of hardware, software, firmware or some kind of OS. This caused me to not recommend moving forward with the next interview.

    In my experience - being honest is not enough, you need to be <i><b>perceived </b></i>as honest too. I've interviewed a lot of people for SQL/BI related work and it appears to me that 1/3rd of the resumes contain fabrications or can be classified as total BS. For this reason I exclude valid skills from my resume if I am bad at explaining them and having real examples I can use.

    You don't need years of professional SSRS experience to get a job working with SSRS. You can run SQL Server with SSRS on your PC or laptop for free. Create SSRS reports for your own use. I've done this with my music collection and video games. There's a Stairway to SSRS on this site which is pretty good. When I advanced to SSAS in 2010/2011 I spent a lot of time teaching myself MDX - I had less than a year of real SSAS experience and was honest with recruiters about that. The fact that I was taking my own time to learn it really impressed people which led to my first "BI Developer" job at a Fortune 100 company.

    "I cant stress enough the importance of switching from a sequential files mindset to set-based thinking. After you make the switch, you can spend your time tuning and optimizing your queries instead of maintaining lengthy, poor-performing code."

    -- Itzik Ben-Gan 2001

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply