Ian Klosowicz
A humanities or liberal arts degree doesn't disqualify you from data analytics. Most people who break into data without a technical background spend time worrying about the wrong thing. The degree on your resume matters less than what you can demonstrate you can do. SQL is learnable. So is Excel. So is Tableau. What's harder to learn is how to ask a good question, how to structure an argument from evidence, and how to communicate a finding to someone who doesn't share your context. A humanities education builds all of that. The technical gap is real but specific, and it closes in months, not years.
The same reframe applies if numbers are your worry rather than your degree: breaking in without a math background comes down to the same job-ready skills, not your transcript.
The real barrier for humanities graduates breaking into data isn't the degree. It's the absence of demonstrated technical skills and a portfolio. Hiring managers aren't running degree filters the way they used to. What they're filtering for is evidence that you can pull data, analyze it, and present something useful. A philosophy major with 3 SQL projects on GitHub is a more competitive applicant than an economics major with no portfolio and no demonstrated tool experience.
I don't have a degree in data. I broke in by teaching myself the technical skills, building things worth showing, and putting myself out there before I felt ready. The credential question almost never came up in the interviews that mattered. What came up was: walk me through a project, how did you approach this problem, what would you do differently. That's a conversation you can have regardless of what your diploma says.
The thing most humanities graduates get wrong is assuming the degree is the problem and spending months looking for ways around it rather than just building the skills. The degree isn't the problem. The missing portfolio is.
Liberal arts and humanities programs aren't purely theoretical. The core skills they build are in high demand on analytics teams, and they're much harder to teach than SQL:
The technical gap for a humanities graduate with no data background is real. Here's what to build and in what order:
The sequence matters. SQL first, then spreadsheets and visualization in parallel, then statistics informally alongside everything, and Python later if the role requires it. Most humanities graduates try to do everything at once and end up functional in none of it.
The gap for humanities grads is almost entirely technical, and how much SQL you actually need defines most of it.
Some entry-level data roles are a better fit for a humanities background than others. The ones that draw most on communication, research, and domain context alongside technical skill are the right starting targets:
The instinct for many humanities graduates is to pick a dataset with no connection to their background and try to look as technically generic as possible. That's the wrong move. Use your domain knowledge. It makes the project more interesting and makes you more credible when you talk through it in an interview.
Document every project in plain English. Explain what question you asked, what data you used, what you found, and what a business or organization could do with that finding. That write-up is what the hiring manager reads before deciding whether to interview you.
When I built Month 1 of Analyst Hive, the project sequence was designed so that each one demonstrates a different capability: SQL on raw data, cleaning and analysis, then a dashboard. For humanities graduates, anchoring those 3 projects in topics you can speak to with genuine knowledge makes the portfolio significantly harder to dismiss.
The worst thing you can do is apologize for the degree. Hiring managers read that as a lack of confidence in your own qualifications, and they're right to. Your degree is your background. The portfolio is your qualification. Lead with the portfolio.
On the resume, the order matters. Portfolio projects and technical skills go above the education section. A hiring manager scanning your resume should see SQL, Tableau, and 3 project titles before they see where you went to school. If they get to the education section already interested in you, the degree is an afterthought. If they see the degree first and have a STEM bias, you never get the chance to make the case.
On LinkedIn, make your transition direction explicit. Your headline should say what you're going for, not what you did. Something like "Aspiring Data Analyst | SQL, Tableau, Excel | Former [field]" tells a recruiter in 10 words what they need to know. Then post content about what you're building. A brief walkthrough of a SQL query, a screenshot of a dashboard, a note on what you learned from a messy dataset. That content builds credibility faster than any credential update.
In interviews, the career change narrative is 30 seconds. You became interested in data because of X, you built Y skills, here's what you built. Then move directly into the portfolio. Interviewers aren't looking for a perfect origin story. They're looking for evidence that you can do the work.
For a humanities graduate starting with no data background, the realistic timeline to a first analyst role is 6 to 12 months of consistent effort. The range is wide because consistency is the variable that matters most, and it's the one most people struggle with.
A realistic breakdown:
The people who take longer are usually doing one of 2 things: spending too long in learning mode without building anything, or applying broadly without targeting roles where the humanities background is relevant. Both are fixable.
10 hours a week of focused effort is enough to move through this timeline alongside a full-time job. I built Analyst Hive alongside a full-time data engineering role and a family, so I understand what building something real inside a schedule that's already full actually looks like. The constraint isn't time. It's focus and sequence.
These are the ones that slow humanities graduates down most. Avoid them:
If you want a structured daily program that handles the skills, the portfolio, the resume, and the job search in a clear sequence, join Analyst Hive. The program is built for people breaking in without a technical background, and it tells you what to do each day so you aren't piecing together a curriculum from scratch.
Can you get a data analyst job with a humanities degree?
Yes. The degree matters far less than the portfolio. Hiring managers at most companies are looking for SQL proficiency, demonstrated analytical thinking, and the ability to communicate findings clearly. A humanities graduate who builds those skills and has 3 portfolio projects is competitive for entry-level analyst roles. The degree comes up less in interviews than most people expect.
What data analytics skills should a humanities graduate focus on first?
SQL first. It's the most universally required skill and the one with the widest gap for most humanities graduates. Get functional in SQL before adding anything else. Then add Excel analytical depth and a visualization tool like Tableau in parallel. Basic statistics can be built informally alongside the technical work. Python comes later if the role requires it.
Do I need a statistics background to become a data analyst?
No, not at the entry level. Basic statistical concepts, averages, distributions, correlation, statistical significance, come up regularly and are worth knowing. But you don't need a formal statistics background or coursework to get your first analyst role. Most of what you need can be picked up informally while building your SQL and visualization skills. The bar is comprehension, not expertise.
Is a data analytics bootcamp worth it for a humanities graduate?
Usually not, for a few reasons. Most bootcamps are expensive, move faster than the retention rate justifies, and produce the same certificate as every other graduate in the cohort. The skills a bootcamp teaches, SQL, Excel, Tableau, are self-teachable with free or low-cost resources. What matters to hiring managers is the portfolio, not the bootcamp name. A self-built portfolio of 3 strong projects is more compelling than a bootcamp certificate with no supporting work.
How do I explain a humanities degree when applying for data analyst jobs?
Lead with the portfolio and technical skills, not the degree. On the resume, put skills and projects above education. In interviews, give a 30-second career transition narrative and then move immediately into the work you've built. The degree becomes irrelevant once you're talking through SQL queries and dashboard decisions. Most interviewers stop caring about the degree 5 minutes into a portfolio walkthrough.
What liberal arts majors are best for data analytics?
Economics and psychology have the most overlap with quantitative methods used in analytics. Sociology, political science, and history involve significant research and data interpretation work. English and communications build writing and synthesis skills that are undervalued on analytics teams. Honestly, any humanities or liberal arts major works if the person builds the technical skills. The major isn't the differentiator. The portfolio is.
The analysts who get dismissed because of their humanities background are almost always the ones who lead with the degree and follow with the apology. The ones who get hired are the ones who lead with SQL, a dashboard, and 3 projects that show they can do the work. The degree becomes a footnote once the portfolio is doing its job.
If you want a structured daily path that walks you through exactly what to build and in what order, join Analyst Hive.
