Forums for the Business Analyst

 
  Modern Analyst Forums  Careers  Career Advice &...  Rejected at interviews for being too technical
Previous Previous
 
Next Next
New Post 3/4/2012 10:37 AM
User is offline MajuryACSI
3 posts
No Ranking


Re: Rejected at interviews for being too technical 

 I have had the same problem as Arnie, with regard to being too technical and recently when interviewing for an AVP position got rejected for the same reason and thought I couldnt work with that level of stakeholder despite previously working with Global Heads and Reginal Heads with SVP being my lowest level stakeholder. 

 

In that case I found that they werent letting me complete the S part of STAR format of answering competency based questions and I believe were just looking for corporate buzzword answers!

 
New Post 3/5/2012 5:22 AM
User is offline KJ
243 posts
6th Level Poster


Re: Rejected at interviews for being too technical 

Arnie,

This is a bit of a dilemma. Move on to the next interview. I think what is important is that you are capable of abstract and concrete thought. Programmers who become BAs are normally prone to jumping into design (concrete) mode too quickly. And, a BA with a Liberal Arts Degree might be hovering too much in the abstract domain. When you have to extract the essential requirements from an existing system (process), you need to "abstract" the information from a detailed (concrete) process, especially when you interview an SME, who will tell you HOW they do things, and you need to extract the "what".

So here the trick! When next you go for the interview ask the interviewer to give you a little bit of background of themselves. I was once interviewed by a Chef and another time by a Landscape Gardner who happen to have worked for the recruitement firm for a few weeks. Once you know their background, slant your responses to their requirements ( speak their language). If the interviewer tells you that they once wrote a Compiler with LALR parsing and the Lex analyser in C++, you may have to start talking some technical stuff. However, if the interviewer has no idea what a "Boolean" is (say), you need to hover.

At the end of the day, the objective is to get the job. The assumption is that you can do the job eitherwise you wont be there for the interview.

Just some thoughts,

warm regards,

K

 
New Post 3/7/2012 3:24 AM
User is offline vicky mentor
3 posts
No Ranking


Re: Rejected at interviews for being too technical 

Try to be simple and answer questions straight and without going much in to its technical. 

Always talk general about the topic.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Careers  Career Advice &...  Rejected at interviews for being too technical

Community Blog - Latest Posts

Salesforce has established itself as one of the most reputable CRM platforms, providing important customer data to assist businesses in effectively managing their operations. Salesforce is the world's best CRM platform that helps businesses to keep up the data in an arranged or structured manner. Salesforce is the world's most popular...
There are big differences between data exploration versus data presentation. And you need to be aware of these differences as you're creating data stories and data presentations. Let’s start by defining our terms: Data exploration means the deep-dive analysis of data in search of new insights. Data presentation means...
Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC