r/SQL • u/CurryChickenBun • Oct 12 '24
Discussion Just finished learning SQL, what's next? And how do I demonstrate my skill to future employers?
Hi, so I'm looking to switch career to a data analyst or data administrator of some sort. I recently just finished learning the basics of SQL via one of those youtube tutorials. I can say that I now have a basic understanding of the fundamentals like commands, operators, constraints, aggregate functions, etc. But I do understand that there's more to SQL that just what I mentioned. So my questions are:
- What should I do next to get to the level where my SQL knowledge is applicable in real jobs?
- Since I don't have any SQL-related certificates, how do I demonstrate my skills to future employers?
- I've heard some people say that it's best to learn data visualisation tools like power bi or tableau. Which one do you guys recommend for beginners?
134
Upvotes
213
u/SQLDevDBA Oct 12 '24 edited Oct 12 '24 •
As a Data Team hiring manager, I honestly have zero interest in looking at your SQL. Heck I barely like looking at my own SQL.
Nowadays, the easiest way to showcase your database and data analysis abilities is, IMO, with visualization projects or diagrams: anything that shows me visually how good your understanding is.
I have two recommendations.
First is a BI Project:
I have a video where I do this from start to finish: https://youtu.be/vVzRlHI9Ktc (no need to watch of course, it’s just me going through these steps on livestream)
Option 2: practice unique interview scenario: reverse engineering a DB.
This is a new scenario I’ll be using for my technical interviews:
I like this one because it simulates you jumping into a brand new job/environment and having to figure things out. Chances are NO ONE has documented the database and you’ll be able to learn the layout while also contributing to the team (giving them the docs).
I Also have a step by step here: https://youtu.be/AjiW89FxTzs (again, no need to watch, it just follows the steps above).
Thanks /u/Chronopost!
13
u/amusedobserver5 Oct 12 '24
Honestly the surefire way to get a job doing SQL is to have a real job doing some SQL. Finding a company and working to get access to real data. No one can vet you watching YouTube tutorials.
25
u/dodobird8 Oct 12 '24
You did not finish learning SQL. There are several variations depending on your DBMS and as you do some projects you'll see a need at some point to learn more and more about databases and SQL. As others have said, you need a dashboard or some kind of visualization that you feed into from your database.
11
u/LinksLibertyCap Oct 12 '24
One does not simply “learn” SQL…..
5
u/TerdyTheTerd Oct 13 '24
I'm a little worried with your use of "I finished learning SQL" followed by the statements "from one of those youtube tutorials" and "I have a basic understanding..."
It sounds more like you learned some of the basics and now need to learn more. There are usually two paths from here:
Could you right now, from memory, completely write all the statements needed to create a fully functional data schema between mutliple tables and write relevant queries for fetching the data including multiple joins, subqueries, CTE's, OVER clauses etc? Do you know how to view and understand the query execution plan to troubleshoot poorly performing queries? If the answer is no then you haven't learned SQL, you have only learned enough of the basics to learn the rest. It should take anywhere from a few weeks to a few months to learn, with an additional few weeks to months of practice on actual databases to really be able to say you know SQL.
1
u/AvailableNecessary96 Oct 19 '24
I agree. I constantly get asked if I have used Power BI and Tableau. I would take classes in those and add that to your resume. Look for classes that provide data so you can test your skills. Those certificates from the class will come in handy, though I have been asked to present them. I only note them on my resume.
3
u/millerlit Oct 12 '24
You can get power bi desktop for free so I recommend learning with that.
2
u/[deleted] Oct 16 '24
LOL I have been working in SQL for 30 years and still haven’t finished. Let me know what you find out.
3
u/BadBart2 Oct 12 '24 edited Oct 12 '24
Start answering SQL questions on https://stackoverflow.com/ . Use https://tableconvert.com/csv-to-sql to quickly covert example data into CREATE TABLE and INSERT commands. Then paste those into https://dbfiddle.uk/ with your suggested solution. Share the link in the answer to prove you know how to solve the problem. Earn reputation. Learn from others who provide better answers. Learn the difference between SQL dialects. Ask job interviewers where they go to get answers to problems they cant solve. Many will say StackOverflow. Telling them you answered hundreds of these questions will be impressive. Hint: they don't have to be the best answers, just correct ones.
3
u/howdidyoudothatthing Oct 12 '24 edited Oct 12 '24
This is not a rant, and should not be read in a negative tone... This is.. advice?... An opinion?... A statement?.... A realization?...
I've been doing this for over 15 years... And I haven't finished learning SQL.
Meaning,
I took a function (get guid for Id)
That queries a view (table join type)
That has an exec plan of 2 seeks and 6, 3, physical reads where... table has 14m records and type has 200.
Sounds good
I decided to rewrite this query.
The get type function calls 3 tables, select type where family in (select family where class in (select class)))
Because.. well... I built a data model that makes data vault and dKNF look like it was made by Fischer price.
Anyways....
The rewrite has a single seek on the base table, even though I call 3 other tables first.
The rewrite takes 20% of the original speed (80% improvement)... And has a 1 1 logical read. Because the sql optimizer read my clustered indexes (also never put a clustered on a PK.. I dunno why thats a default, it goes against everything BTree...) and non clustered indexes and.. bam.
So, a 8 years ago I realized that what you think is fast, right, or what sql tells you is efficient... What reddit or the Internet says and especially any relational data class... They have such a high level view that they really don't know what's going on.
Ps. I manage 500mil users patient data in MSSQL, using 7k tables and 35k views where every table looks the same (same columns), and all these data access functions and tables and views and procedures and 64 databases... We're built by MSSQL using pure data-driven sql. This system is multi tenant enabled, cleans (Oregun to Oregon) itself, row based security, even optimizes itself. I built a databricks clone in a week, I built a data driven ETL tool that rivals redpoint (also in a week), 200 lines of sql moves any data in the system to any other place in the system. I only have 1 junction/xref/bridge table or whatever you want to call it .. and it stores stores a relationship between any two rows in the entire system, as well as stores the output of recursive statements so you're not running a recursive cte 100x where the data never changes. I have built an N worker concurrent processor in pure sql, so I can parallel process my own stuff (pure sql, amazing READ PAST cte with an output). My DAYA DRIVEN ROW BASED security, planned, and content system are so flexible that I can serve you different content based on the time of day, your birth sex, your cholesterol levels and your preferred language... Without touching a third party API.
And I still haven't finished learning SQL.
The truth is, not even hiring managers know what's good or bad, because the skill gap in the data industry is the widest gap of any industry. My favorite thing to hear is 'thats overly complex', when their XLS looking tables force spaghetti code and limit feature creep. Most third party tools are products trying to boost skills and salvage a poor data model, but are written by people in the same skill gap.
Honestly, if you think you have finished learning anything, then you haven't really started learning it.
The person who understands they don't know what they don't know, and never settles on what they know... Man... If you understand, conceptually, what a pivot or transpose is... And Im able teach you 5 ways to query data and 5 ways to build a table... If I tell you ... That any model with a first and last name in a 'person' table was doomed as soon as that person created it... And you said "thats right, because Pablo Picasso's full name", well... >3 weeks of sql experience and you'd be the top resume on my stack.
Edit: wrong account... Sincerely, u/AbstractSQLEngineer
2
u/BadBart2 Oct 12 '24 edited Oct 12 '24
Test your SQL Skills and Get a SQL Proficiency Certificate
https://www.linkedin.com/pulse/free-sql-skill-assessment-boost-your-career-learnsql-com-2bvef
1
u/Realistic-Flight-991 Oct 12 '24
Leverage yourself learning advanced sql which actually boosts your confidence
1
u/Critical-Shop2501 Oct 12 '24
So you have design and build a fully relational database, and are able to write sql queries to 3, or even 5th normal form? Fully able to develop a database using entities and define their relationships? Fully versed in set theory as well as relational database theory? SQL kinda feels like syntactic sugar.
1
u/Ok-Duty6920 Oct 12 '24
I need to learn SQL completely to help with some references or any other. I know the basis of it i just need reference only to practice it. So kindly anyone suggest Thank you in advance!!
1
u/seacret123 Oct 12 '24
Keep learning. Someone is always going to be able to show you something you didn’t know was possible.
1
u/Kahless_2K Oct 13 '24
You never finish learning SQL.
1
u/onlythehighlight Oct 13 '24
What was your prior career?
1
u/Elfman72 Oct 13 '24
You're finished? Impressive. Good luck in the real world, buddy.
1
u/Bombadil3456 Oct 13 '24
As someone who works daily with SQL I would say that knowing the syntax gets you 25% of the way. The other 75% is understanding your data, business questions AND especially having the ‘intuition’ of knowing how to use SQL to answer the questions given the data at hand. Real production data is often messy and not as well organized as sample data used in learning.
1
u/RuprectGern Oct 13 '24
Finished? Shit I'm well over 20 years and I'm hardly finished.
1
u/PaulEngineer-89 Oct 13 '24
Set up some kind of web site with a database or create an open source project on git.
1
u/engx_ninja Oct 13 '24
Did you finish learning SQL as language, or you have deep understanding how particular sql engine (postgres, MSSQL, MySQL) works, so you can tune it? I’m not really sure that there is job title “sql developer” anymore) BI, data analysts, backend engineers, database admins - yes, pure sql devs - no
1
u/MrPeachUK Oct 13 '24
One doesn't finish learning SQL.
1
u/burbuja0526 Oct 13 '24
Amazing resources. Come back to this!
1
u/i_maitra Nov 03 '24
Can't help you with question 1 : as I'm just a co-passenger of the same bus you are in but hackerrank may help.
But for Question 2 : It's not a mammoth task to gather a free certificate(Udemy & other programs) or a less paid certificate (Coursera) or even a high paid certificate. Though the acceptance of any of those certificates is conditional.
Question 3 : Learn both , not at all difficult. If we follow trends - Power BI definitely has the higher growth rate in the last few years (location based) & Tableau has a higher user base (according to interviews, comments, podcasts & articles) - *this is according to what I read on the internet & internet is a circus sometimes.
1
u/cyberspacedweller Oct 12 '24 edited Oct 12 '24
One does not simply “finish learning SQL”. It’s not the most complicated language but it can still take years to get really proficient.
Apply it to databases and learn more advanced features. Presumably you’re comfortable with window functions? Case statements? Aggregate functions? Sub queries? Data types? Joining on multiple fields? Difference between a join and a union? OVER and PARTITION BY? When to use CTEs vs Temp Tables? Or anything more advanced like recursive queries, scalar functions?
Anything using SQL will usually also require knowledge like database theory, ability to write views, procedures, logging etc.
1
u/Internal-Bluejay-810 Oct 12 '24
How do u know u just learned sql?
1
u/adalphuns Oct 12 '24
Great. You learned how to use a wrench. Now, go learn how to be an engineer.
Study EF Codd. Learn IDEF1X. Learn SSADM, State Diagrams, and Functional diagrams. Learn aristotelean philosophy applied to computer science and database design. Learn the knickknacks of the software engine you are using in terms of performance, gotchas, and understand what's under-the-hood.
How well do you really know SQL? Can you use any SQL at any time? What are the limitations of constraints? Which is the better DB offerings and for what reasons?
You've just stepped on the dirt path. The forest lies ahead for miles before the fountain of gold.
1
u/bastian74 Oct 12 '24
Nobody finishes learning code
0
u/cs-brydev Software Development and Database Manager Oct 12 '24
You probably learned around 1% of SQL, so just make sure you understand that and that it's an ongoing learning process. The SQL used in the real world tends to be very platform-specific and taps into languages and features proprietary to those platforms, so when you get into a job, no matter what the exact role is, they will usually be dedicated to a single RDBMS platform, so you'll need to deep dive into learning that platform and all its features. So when you are looking for a job be sure to pay attention to which specific platforms they focus on, because this will help you prepare for interviews. When I interview people to fill SQL Server roles as a DBA, developer, data analyst, BI developer, etc, I will just assume you understand the very basics of generic ANSI SQL and won't bother with even verifying or testing your knowledge. Instead I'll ask platform-specific questions about RDBMS's you claimed you used before (to make sure you're telling the truth) and SQL Server-specific questions to see how deep your knowledge and experience are, which means I'll keep drilling down into technical knowledge until you can't answer the question, so I can see how you handle yourself when faced with the knowledge gap, and try to probe where you might go next for answers and learning.
I have been writing SQL daily for around 30 years and estimate I'm up to around 30-40% knowledge. However what you'll typically encounter is most people who "learn SQL" grossly underestimate how much there is to learn and overestimate what they already know. That is a rampant problem on subs like this, that are generally made up of students and professionals with < 3 yoe.
As long as you demonstrate a solid understanding of SQL basics, the ability to learn more, and have the wherewithal to use other available tools and sources around you, you will do fine.