With nearly 10 years of experience, the fact that you are not getting interviews suggests the problem may be less about your ability and more about how your experience is being translated on your resume. If you are applying to Business Intelligence Analyst, Data Analyst, and Business Analyst roles with one general resume, that can hurt you. Those titles overlap, but employers still screen for different keywords and tools. O*NET’s current posting data for Business Intelligence Analysts shows SQL appearing most often, followed by Power BI, Python, Tableau, and Excel; for Management Analysts, Excel, SQL, Power BI, Jira, Tableau, and Visio show up prominently.
So no, Python is not mandatory for every BI or business analyst job, but it absolutely helps, especially for BI and Data Analyst roles. If Python is missing, that alone usually should not block interviews if your SQL, Excel, and dashboard skills are strong and clearly visible. For BI roles, I would make sure SQL, Power BI or Tableau, Excel, dashboard development, KPI reporting, stakeholder communication, and business impact are easy to find in the top half of the resume. Microsoft’s current Power BI Data Analyst certification page also makes clear that Power BI-focused analyst roles are expected to work with data preparation, modeling, visualization, Power Query, and DAX.
I would probably make three targeted versions of your resume instead of one:
Business Intelligence Analyst: SQL, Power BI/Tableau, dashboards, DAX/Power Query, reporting automation, KPIs.
Data Analyst: SQL, Excel, Python if you have it, data cleaning, reporting, analysis, visualization.
Business Analyst: requirements gathering, process improvement, stakeholder management, Jira, Visio, documentation, workflow mapping.
Also, make sure every bullet shows results, not just tasks. For example, instead of saying “built dashboards,” say what changed because of them: reduced reporting time, improved forecast accuracy, supported executive decisions, identified cost savings, or improved operational visibility. That matters because O*NET describes BI analysts as people who generate reports for stakeholders, maintain dashboards and BI systems, and manage the flow of business intelligence information to users.
If you have been searching for three years with almost no interviews, I would strongly suspect one of these issues:
your resume is too generic for ATS screening,
your title/summary does not match the jobs you want,
your strongest tools are not obvious in the first third of the page,
or your experience sounds like support work instead of analytical impact.
A practical next step would be to pick one lane first instead of chasing all three equally. In your case, if your background is strongest in reporting, dashboards, and stakeholder-facing insights, BI Analyst may be the cleanest target. Then add Python if you can, but do not wait on Python before fixing the resume. SQL and one major BI tool usually need to be unmistakable first. If your resume is light on Power BI, the current Microsoft Data Analyst credential may also be worth considering because it is specifically tied to Power BI, Power Query, DAX, modeling, and visualization.
You are also applying across several Texas metros, which is reasonable, but I would tighten the message further by adding a location line such as ‘San Antonio-based, open to Austin, Dallas, Houston, and remote/hybrid roles’ so employers do not wonder whether location is a problem.
If you want, post the top section of your resume summary and your core skills list, because that is usually where the issue shows up first. Right now, what are the first 10–15 skills listed on your resume?