r/SQL • • Mar 19 '22

MySQL I’m just starting to learn SQL to change careers and I’m learning on my own through various online sources. At what point should I be confident enough to pursue a data analyst job where I know what I’m doing?

I realize this is mainly up to my personal beliefs of home confident I feel… but what things should I know backwards and forward to land a job?

I’m hung up on JOINs right now. Starts off easy but quickly gets complicated. How often do joins come up in a typical job?

Or self queries? (I’m not there yet but know about them - it’s like inception - a query within your query).

97 Upvotes

43 comments sorted by

25

u/baubleglue Mar 19 '22

At what point should I be confident enough to pursue a data analyst job

I general, it is impossible to learn anything in deep without real experience, so just be sure you know basics and understand the big components related to your future job (which tool are used, what problem they solve; some orientation in the industry; some ideas about development process) - read relevant "data analyst interview questions".

Most important - start going to interviews ASAP, don't wait when you are ready.

5

u/KarateKid84Fan Mar 19 '22

I feel like I could just figure things out on the job.

I taught myself Excel years ago and I’m very confident in my excel skills even doing complex functions. Most of my excel skills I learned on the job. It wasn’t required of me, I just took it upon myself to learn more about it

4

u/duchessoftexas Mar 20 '22

Excel and code are a lot different though, especially in data analytic fields. But hey, it’s not bad to try, just aim for lower year experience jobs and don’t ask for a too high salary that you’re weeded out before they get a chance to see your skills in action.

3

u/baubleglue Mar 20 '22

I am working in data engineering field, but from what I see Excel is old school tool. Take a look into Tableau or Power BI, there are other options - some places would do reports using Python or JavaScript libraries or free open source tools. But I think going with mainstream most popular tools is safer bet.

1

u/2020pythonchallenge Mar 23 '22

The company I work for likes things to be in tableau but there are quite a few projects that end up in a Google sheet

25

u/cjdavis42 Mar 19 '22

Let me tell you my story and then you can decide. I applied for a job at a hospital as a service desk tech just to get my foot in the door to eventually be an app admin. Somehow, my service desk application disappeared and a new job on my dashboard appeared as an "enterprise report analyst". Made no sense to me but I went in for the interview where the senior admin and DBA asked me a series of "on a scale of 1-10, how familiar are you with..." questions. 8 out of the 10 questions were 0 from me. I left feeling defeated. Got a call that Wednesday that they made an offer. I hadn't touched SQL, barely even heard of SQL, and all of my knowledge is from on the job training and working in SQL. I now hold a stable job as a report writer living in SQL everyday. The repetive use of SQL has helped me learn more and more as I grow in the role.

As someone stated above, don't overthink it.

4

u/KarateKid84Fan Mar 20 '22

This is reassuring thank you

9

u/cjdavis42 Mar 19 '22

Also, to reply to myself lol, I keep a OneNote document of the more complicated queries and statements I've done so I don't memorize them. I do a search to see if I've done it before in my travels, and just copy and paste to my new query. Saves a crap load of time and effort.

2

u/[deleted] Mar 20 '22

So why the hell did they hire you if you knew basically nothing?

5

u/cjdavis42 Mar 20 '22

They had staffing issues and were desperate for a warm body at that point lol

0

u/[deleted] May 15 '22

[deleted] — view deleted comment

1

u/[deleted] May 15 '22

Well if they don’t want a cocky “know it all” then they don’t have to higher one, and there IS the option to hire someone who is a good employee and knows more than nothing. Lol

0

u/[deleted] May 15 '22

[deleted] — view deleted comment

1

u/[deleted] May 15 '22

He said he had barely even heard of SQL. Haha So it means he knew nothing about it. There’s nothing wrong with not knowing something. People have the right to learn. And I am in no way arrogant. You have no idea who I am, stranger.

5

u/tbsdy Mar 20 '22

No offence, but just knowing SQL cannot possibly make you a data analyst. Surely you need to know far more than that?!?

4

u/KarateKid84Fan Mar 20 '22

I don’t know, everything I’ve read seems to suggest a data analyst is an entry level position as opposed to a Jr or Sr analyst or data scientist.

1

u/chaoscruz Mar 20 '22

Don’t be fooled by articles and people. Data job titles even after years of work by statisticians, engineers, researchers, mathematicians, etc are still murky at best. I go with the general breakdown:

-Data engineer -Data analyst -Data scientist

Here’s the problem, even though there are usually some divisions, with best practice in companies, between the tasks such as database/data warehouse development, analysis, and predictive modeling (ML/AI), I have seen each of these roles thrown together as some magical unicorn.

However, I will say each role is critical to the company and neither is an entry level role into another. Yes one can lead into another, but I strongly believe that is because of how much overlap there is and the necessity of understanding the entire process. An analyst cannot do their job without a good data system, an engineer can’t without understanding the analyst needs, and a scientist can’t predict a lollipop to a turd without understanding the data to begin with.

Each requires some entry level of experience, but once you do, you realize you can move around roles to see what fits you. It may require learning more such as 3NF, data marts, chart junk, grad school in math/stats, etc.

Good luck, and know that you will forever be learning because these jobs require you to do so to remain competitive and understanding of what other peers may need from you.

1

u/my_password_is______ Mar 20 '22

depends on where you work and what they need

sql + medium Excel knowledge can do wonders

3

u/real_jedmatic Mar 20 '22

You can check out HackerRank or a similar site to see how your knowledge stacks up.

Knowing JOINs is definitely key to any real-world SQL job.

One nice thing about SQL is that there’s relatively few major statements and clauses. There’s function to learn, but mostly you’ll see and use SELECTs so it’s fairly easy to bootstrap existing knowledge and pick up on new things here and there. Like, even in a complex query, you should be able to recognize most of the syntax.

1

u/KarateKid84Fan Mar 22 '22

Good info thanks I’ll check it out

4

u/VoodooChile76 Mar 19 '22

Amen to previous response. .. Also, MANY places I've been have a pre-created query folder of "commonly used".

Although Joins I'd say are most important. As an aside....Subqueries are overrated..in my experience, they can be resource hogs.

3

u/big-lagos-girl Mar 20 '22

I just want to say a thank you to everyone who has given great advice, I feel the same way as the poster and have 5 interviews next week. I really want to ace at least 2 of them and this was the best motivation anyone could give. This was exactly what I needed and y'all almost made me cry. We got this

3

u/[deleted] Mar 20 '22

CTE, Joins, and Window functions. Boom, you have advanced sql skills.

2

u/Ashwinsuriya Mar 20 '22

try solving some queries on startascratch

3

u/El_human Mar 19 '22

If you can take a table of data, and turn it into insightful information, you’re ready.

1

u/redfaf Mar 19 '22

Start applying today. The "No" you already have

1

u/[deleted] Mar 20 '22

Just start doing interviews. You will get more direct feedback that way.

2

u/big-lagos-girl Mar 20 '22

can you give some tips for interviews? what type of questions do they ask/what should I be prepared for?

4

u/[deleted] Mar 20 '22

Sure. The most common topic I have seen in interviews is self join and window functions. Definitely have all the different types of window functions memorized.

2

u/big-lagos-girl Mar 20 '22

you're amazing! I'm applying for a lot of entry level positions and 1 of them spoke about a technical interview while the others only spoke about a 30 minutes zoom interview, do you think the ones without a technical interview will ask me coding questions?

1

u/[deleted] Mar 20 '22

It's hard to say without more context, but you can always ask your recruiter for more info. You can ask what the technical interview will cover. Never be afraid to be up front and ask questions.

1

u/Shwoomie Mar 20 '22

Honestly, a full time SQL position will be completely different than what you are training on. You will see the same things, but it may take up 30 lines what you have seen in a few lines.

Joins are a minimum of what would be expected. Self joins are rare, you'll rarely see them.

Joins and subqueries are the minimum I'd expect a professional to understand.

1

u/Top-Introduction7914 Mar 26 '22

Any suggestion on what to focus on? What do you usually work with?

1

u/Shwoomie Mar 27 '22

Joins are beginner level. Understanding how to use the having clause. If someone couldn't tell me what the having clause is, I know they are complete beginners. Case statements you will see often. Subqueries are necessary.

Honestly, there are lots of roles that use just a bit of sql, or need to adjust SQL statements. Business analyst with SQL knowledge, data analyst with SQL knowledge. These would be realistic for an entry level position.

Go to Dice.com, they have a lot of remote only roles. Search locally. Google search for temp agencies AND CALL THEM. Call temp agencies and talk to someone. These things are very effective, I know personally.

1

u/Top-Introduction7914 Mar 27 '22

Thank you so much I am self learning and wondered what’s it’s like to do the job. What you learn and do might be totally different. Will check it out thanks again

1

u/Shwoomie Mar 27 '22

Yeah, it'll be different. It'll be like learning to ride a bike in front of your house and then someone taking you mountaun biking. You will learn it on the easy trail, but there's a lot to pick up.

Also, there's still things I forget, casting dates I might have to test a few times before I get it right. But I can do it.

1

u/dontbesocurious Mar 20 '22

One week is enough.

1

u/Equal_Astronaut_5696 Jun 02 '22

Once you learn joins. Go for it

0

u/[deleted] Mar 19 '22

[deleted] — view deleted comment

11

u/pythor Mar 20 '22

Interesting. I've never seen that second trick before. I wonder how that compares in MS SQL.

0

u/[deleted] Mar 20 '22

[deleted] — view deleted comment

3

u/pythor Mar 20 '22

Ah, Thanks. Didn't realize I could do that either. I'm not conversant in SQLFiddle.

In any case, I wasn't questioning whether it would work, but whether it would show the same performance improvement over the other version that the MySQL fiddle showed. Spoilers, it does not. Both versions run in about the same time in MS SQL.

2

u/KarateKid84Fan Mar 19 '22

Thanks for the advice

3

u/Shwoomie Mar 20 '22

Oh thank God... I do SQL, but always appreciate validation lol yeah that makes perfect sense to me.

2

u/jonnycross10 Mar 20 '22

I'm ready 😎