Forums for the Business Analyst

 
  Modern Analyst Forums  Careers  Career Advice &...  Should I get a Master's?
Previous Previous
 
Next Next
New Post 5/7/2016 6:24 PM
User is offline n00banalyst
1 posts
No Ranking


Should I get a Master's? 

So, I've landed a business analyst gig.

The thing is, I have no background in business and only a certificate from a no-name state school in IT.

I'm going to give it a year to learn the job. But for my longer term career, should I be thinking about picking up a master's in something like Management Information Systems? Or should I just sit tight?

 
New Post 5/9/2016 1:24 PM
User is offline NitWitNick
259 posts
5th Level Poster


Re: Should I get a Master's? 
Modified By NitWitNick  on 5/10/2016 10:06:17 AM)

I see places hiring non-degreed people if they have the skill set they need.

Many job ads also show that experience in years can replace that degree.

 

Update: I Found These Out There As Examples ...

"Bachelor's degree in related field OR equivalent work experience"

"Bachelors' Degree or seven years of related responsibility"

 "BS/BA or Masters Degree in Engineering, Computer Science or equivalent education/experience"

 

 
New Post 7/4/2016 4:45 AM
User is offline Tressie
3 posts
No Ranking


Re: Should I get a Master's? 

I think you must go for the masters degree because it will add value to your resume. It will also help you in your career growth.

 
New Post 7/18/2016 8:55 PM
User is offline Recoveringrecruiter
1 posts
No Ranking


Re: Should I get a Master's? 

I think you are putting the cart ahead of the horse. Do you think that you want to get a Master's because it will help your career? Because you want to get into upper management?

Most Master's programs require at least 4-5 years of working experience before you can apply. In addition to that, most companies don't seem to care as much these days about a Masters, unless it is for a job in upper management.

I've worked with many Business Analysts. Some have Master's Degrees, some don't. Both make the same money (based on how much working experience they have). So it's really up to you what you intend for the future.

If you are just starting out, I would first give it a good couple years at your current role, then look around for a new position elsewhere to diversify your resume and project experience. Once you have 3- 4 years of real BA experience and have met other people who are were once where you were, you will be able to make a more informed decision.

Once you know what you want to do, then you can make the call. 

 
New Post 10/6/2016 3:12 AM
User is offline jenson001
1 posts
No Ranking


Re: Should I get a Master's? 
Modified By Chris Adams  on 10/18/2016 1:11:21 PM)

Do the master's if you want to do it or if it is a requirement for the job you are looking for. For most jobs, a few years of work experience always outweigh any kind of masters degree. You can confirm it if you contact any professional job recruiters.  Other than for some top level jobs, most companies need graduation. Things will be different if you are looking at non-company jobs like teaching  where post graduation and PhD becomes much more important.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Careers  Career Advice &...  Should I get a Master's?

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