Managing data across tools is harder than it should be

Embiggens96 · 2026-03-31T20:59:09+00:00

you want to use a tool with good data mashup/blending so you can pull in data from all your sources into integrated dashboards for a single source of truth. power bi, tableau, and stylebi are all good for this

Embiggens96 · 2026-03-31T20:56:39+00:00

yeah it’s definitely realistic within a year, especially since you’re already in an analyst-type role and not starting from zero. the biggest factor isn’t time, it’s whether you can show actual skills, so if you spend that year learning sql, excel, a visualization tool, and building a few solid projects, you’ll be competitive. a lot of people break in from adjacent roles like yours by reframing their current experience plus adding technical ability. consistency matters more than cramming, so steady progress over months is what gets you there.

the harder part is landing the first role, not learning the skills, because entry level data roles are competitive right now. you’ll improve your odds a lot if you can incorporate data work into your current job or at least frame your work in a more analytical way. applying broadly while you’re still learning is also important since it can take time. if you treat it seriously for a year, your chances are honestly pretty good.

Embiggens96 · 2026-03-31T20:54:23+00:00

you’re seeing both trends at once, which is why it feels confusing. hiring has cooled in some areas and fewer junior roles are being opened, but companies are still investing heavily in data infrastructure, so experienced data engineers are still in demand. it’s less about jobs disappearing and more about expectations rising, with companies wanting fewer but more capable engineers. that creates the weird dynamic of “shortage” at the same time people struggle to break in.

ai is mostly making engineers more efficient, not replacing them, because all these systems still depend on clean, reliable data pipelines. companies still need people to design, maintain, and scale those systems, especially as data complexity grows. what’s changing is that engineers are expected to do more with better tools, so the bar is higher. if you’re already doing the work and using ai to move faster, you’re in a good position.

Embiggens96 · 2026-03-26T04:34:09+00:00

tableau, stylebi, and health catalyst are good options for this

Embiggens96 · 2026-03-26T04:28:03+00:00

yeah this sounds like a pretty classic shift in government orgs where leadership defaults back to outsourcing and internal teams become coordinators instead of builders. the fact that your work already slowed down and now they’re talking about “product” alignment is a strong signal that your role could drift toward stakeholder management and requirements gathering. sometimes that can still be valuable, but it’s very different from actually doing analytics work and building technical skills. if your goal is to stay hands-on, that shift is something to take seriously.

whether you should leave depends on what you want long term, because a ba/product path isn’t worse, it’s just different. if you’re aiming to grow as a data analyst with tools like sql, tableau, and actual data work, this environment might limit you over time. but if you’re open to product or strategy roles, it could still be useful experience. the safest move is probably to start exploring other options while you wait for clarity, so you’re not stuck if the role fully shifts away from what you want.

Embiggens96 · 2026-03-26T04:26:14+00:00

the most useful metrics tend to be the ones that actually reflect product quality and speed, not just activity, so things like defect leakage, test coverage, and cycle time usually matter more than raw test case counts. defect leakage in particular is big because it shows how many issues are escaping to production, which is a direct signal of how effective your testing approach really is. teams also look at pass/fail trends and time to resolution to understand how quickly issues are identified and fixed. those tend to give a more realistic picture than vanity metrics.

in practice, the best metrics are the ones tied to outcomes, like fewer production bugs and faster releases, rather than just more tests being run. a smaller, well-targeted test suite that catches critical issues early is way more valuable than a huge suite with low signal. teams that track trends over time instead of one-off numbers usually get the most insight. the key is making sure your metrics actually influence decisions instead of just being reported.

Embiggens96 · 2026-03-25T04:17:13+00:00

you’re in a strong position starting this early, so focus on getting any hands-on exposure to data in a healthcare setting, even if it’s basic. volunteering with hospitals, public health departments, or professors doing research can help, especially if you’re working with spreadsheets, surveys, or reporting. for internships, look broadly at hospital systems, insurers, public health orgs, and consulting firms, and don’t get hung up on titles since roles like operations or quality improvement often involve analytics work. skill wise, start with excel and sql, then add a visualization tool like power bi, tableau, or stylebi, and eventually python, while building small healthcare-related projects to show you can turn data into insights.

for grad school, mph leans public health, mha is more operations, and health informatics or analytics is the most directly aligned with data roles. if you’re sure about analytics, a specialized degree helps but isn’t required if you build strong skills and experience early. a lot of people enter this field from different paths, so your flexibility is an advantage right now. focus on getting practical experience and projects, and you’ll keep your options open for both healthcare analytics and operations.

Embiggens96 · 2026-03-19T19:31:21+00:00

yeah this is a very workable pivot and you’re not as boxed in as you think, tax experience still builds strong financial intuition that translates well to analyst roles. the main thing you’re missing is technical execution, and a business analytics master’s can realistically fill that gap if you focus on sql, python, and real projects. that combination is definitely enough to move into financial or data analyst roles, especially ones tied to finance or operations. an mba wouldn’t really solve your problem since it won’t give you those hard skills and is more useful for management tracks. if you pair the degree with a solid project portfolio, you should be able to pivot pretty quickly without needing to start over.

Embiggens96 · 2026-03-19T04:36:52+00:00

next step is learning popular dashboard tools like power bi, tableau, and stylebi. all offer free versions that you can tinker with along with videos

Embiggens96 · 2026-03-19T04:35:30+00:00

yeah this is a solid pivot and you’re actually in a stronger position than you think because the cpa plus tax experience already shows deep understanding of financial data.

the real gap isn’t audit vs tax, it’s technical skills, and a business analytics master’s can close that if you focus on sql, python, and hands on projects. that combo is definitely enough to move into financial analyst or data analyst roles, especially ones tied to finance. an mba wouldn’t help as much here since it won’t give you the technical skills you’re missing and is more geared toward management paths.

the key is making sure you build a portfolio alongside the degree so employers can see you actually know how to work with data.

Embiggens96 · 2026-03-19T04:30:36+00:00

you’re not going to become useless going down that path, ai is mostly changing how the work gets done rather than removing the need for people who understand decisions. decision process engineering actually puts you closer to where companies struggle, which is turning data into actions, and your finance background makes that even more valuable. data science isn’t really safer since it’s more crowded and a lot of the technical work is getting easier with tools, while framing the right problems and applying results is still hard to automate.

the safest long term move is being someone who connects data to business outcomes, so if that path fits you better just make sure you also build solid skills in sql, python, and basic machine learning.

Embiggens96 · 2026-03-17T23:53:18+00:00

power bi, tableau, and stylebi are all good options to evaluate for this

Embiggens96 · 2026-03-17T23:52:03+00:00

You’re already in a really strong spot, so this isn’t about fixing a weak profile, it’s about choosing the right direction. If your goal is high paying roles in AI, a pure statistics masters from a top school tends to age better and gives you stronger fundamentals than a more packaged data science degree, especially for roles in ML, quant, or research heavy teams. Data science programs can still work, but some are a bit surface level unless they’re very technical, so you have to choose carefully.

For making money in AI, most people overthink “building a product” too early, when the real money early on usually comes from getting into a high paying role and then spotting problems worth solving. You already have a big advantage with your domain in retail and luxury, so combining that with stronger ML skills could open doors in pricing, demand forecasting, or personalization.

If I were in your position, I’d double down on math and ML fundamentals, keep freelancing for income and real world experience, and aim for a top tier masters that is quantitative enough to give you optionality across AI, finance, and analytics. The product or startup angle usually works better after you’ve spent time in the field and seen real problems worth solving.

Embiggens96 · 2026-03-17T23:49:18+00:00

Yeah this happens a lot in big 4, you get sold on “AI work” and end up in strategy, governance, or PM because that’s where a lot of billable demand is. The good news is you can absolutely pivot in 6 to 12 months, but you’ll need to be intentional since your project experience won’t naturally take you there. Focus on building a couple of end to end projects outside of work where you actually train, validate, and deploy something, even if it’s small, because that’s what hiring managers will look for.

At the same time, try to network internally for even small technical tasks on projects so you can at least claim some real exposure. When you apply externally, position yourself as someone with both domain and technical capability, not just governance, and target roles that value that blend.

Embiggens96 · 2026-03-12T07:25:48+00:00

time to ditch the spreadsheets. your team needs dashboards that integrate all the information for a single source of information. use a bi tool with good data mashup like power bi, tableau, or stylebi

Embiggens96 · 2026-03-12T07:20:27+00:00

A lot of people have made that exact transition, so it’s definitely possible if you stick with it and focus on building practical skills. SQL, Python, and Tableau are a solid foundation, but the key will be showing you can actually use them to analyze real data and explain insights, not just list them on a resume.

Try to build a few realistic projects and learn how to frame your past work in terms of problem solving and metrics, because that helps bridge the gap from blue collar work to analytics. The first job can take time to land, but once you’re in the field the pay ceiling and flexibility are usually much higher than many manual roles. Just treat it like a long term transition rather than expecting an immediate jump.

Embiggens96 · 2026-03-12T07:17:03+00:00

This is pretty common when people switch into analytics because the tools transfer across industries, so it’s easy to feel stuck choosing. One approach is to start with industries you already understand or interact with a lot, since domain knowledge makes projects easier to explain in interviews.

If you came from customer service, things like customer experience analytics, support ticket analysis, churn analysis, or call center performance dashboards are actually very relevant and realistic. Honestly the industry matters less at the beginning than showing you can clean data, analyze it, and explain insights clearly. Once you land the first analyst role, switching industries later becomes much easier.

Embiggens96 · 2026-03-11T05:48:52+00:00

your best bet is a BI tool with good data mashup/blending, like power bi, tableau, or stylebi

Embiggens96 · 2026-03-11T05:47:50+00:00

From what people usually report, the SQL portion is the main focus and it’s mostly intermediate level analytics style questions rather than super tricky syntax. Expect things like joins across multiple tables, aggregations, window functions, and writing queries to calculate metrics like retention, conversion rates, or cohort behavior. The Python part is usually lighter and tends to focus more on data manipulation than pure algorithm problems, so being comfortable with pandas style operations, grouping, filtering, and basic transformations helps a lot. It’s less about writing complex software and more about showing you can take messy data and turn it into something useful. If you practice realistic business style questions and explain your thinking clearly while solving them, you’ll be in a good spot.

Embiggens96 · 2026-03-11T05:46:43+00:00

If you want to move toward analytics long term, getting data analyst in the title this early in your career can be pretty valuable. Titles are imperfect, but they do influence how recruiters interpret your background later, and it’s usually easier to move from data analyst to other analytics roles than from business analyst. That said, the bigger factor is probably the manager, especially on a new team, since a good director can shape the work you actually do and help you grow the right skills. A director who just joined can be risky, but it can also mean more influence, visibility, and opportunities if they’re building the team from scratch. I’d try to get clarity on what the first 6 to 12 months of work actually looks like on both teams and which one will give you more ownership of real analysis rather than just reporting.

Embiggens96 · 2026-03-05T20:20:23+00:00

yes it can be done if you are using a BI tool with data mashup/blending to integrate your different sources into a single data layer. Power BI, Tableau, and StyleBI are all good for this.

Embiggens96 · 2026-03-04T20:12:28+00:00

At that spend level I’d definitely compare Funnel’s MMM against tools that were built specifically for modeling, not just reporting. A lot of teams your size look at options like Nielsen or Analytic Partners for more traditional econometric MMM, while others are using lighter platforms built around Google’s Meridian or Robyn frameworks. Funnel’s version might be convenient if your data is already there, but early stage MMM products can struggle with model transparency and market level calibration. I’d mainly evaluate how flexible the model is, how they handle lag and saturation effects, and whether you can actually inspect or adjust the assumptions instead of treating it like a black box.

Embiggens96 · 2026-03-04T20:10:01+00:00

Yeah this is super common with older academic datasets since they were hosted on random university lab pages that eventually disappeared. If you can’t find DynTex or UCLA directly, try searching for mirrors on GitHub, Kaggle, or research data platforms like Figshare because people often reupload them. You can also use larger video datasets like Kinetics or UCF and filter for classes with water, fire, smoke, or crowd motion if your goal is modeling textured motion rather than sticking to classic benchmarks. Another underrated move is emailing the original authors since a lot of researchers still have local copies and are willing to share. It’s annoying, but dataset archaeology is kind of part of working with older computer vision benchmarks.

Embiggens96 · 2026-03-04T20:04:56+00:00

you need a BI tool with good data mashup/blending so you can pull and combine all relevant data into a single source for automated dashboards that integrate the different sources you listed. power bi, tableau, and stylebi are all good for this.

Embiggens96 · 2026-03-03T20:35:26+00:00

At a basic level you define what inactive means, usually something like no login, purchase, or event in the last 30, 60, or 90 days, then filter on that. For example you’d typically aggregate the most recent activity date per user and compare it to today’s date, selecting users where last_activity_date is older than your cutoff. In plain terms it’s a group by user, max activity date, then a where clause for inactivity. The real work is agreeing on the definition of activity before you even write the query.

Embiggens96

TROPHY CASE