Sr Analytics Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only if posting has real content. We need to parse the posting: It includes "ABOUT THIS POSITION" (intro), "WHAT YOU’LL DO" (responsibilities), "WHAT YOU’LL NEED" (requirements/qualifications), "BONUS POINTS" (maybe skills?), "ABOUT ACEABLE" (company description maybe not needed?), "ABOUT THE BUSINESS INTELLIGENCE & DATA ENGINEERING TEAM" (team description maybe part of About the role?), "ACEABLE PERKS" (benefits), then compensation line. We must not repeat job title as heading. We should not include Job ID etc. Remove boilerplate: EEO, equal opportunity, scam warning, application instructions, cookie/navigation/legal. Also remote hire location list maybe considered metadata; we can fold into short p or drop. Probably drop location list as it's not essential? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So location list is minor metadata; we could drop or include in a p. Safer to drop. Compensation: we have a Pay section: "Compensation: $140,000 - $154,000". So we need a Pay section with that content. Benefits: ACEABLE PERKS list many benefits. So Benefits section. Schedule: Not explicitly mentioned; maybe flexible work schedule mentioned under perks. Could include Schedule section if there is content: "Flexible work schedule" and "hybrid work environment". That's schedule info. So we can include Schedule. Qualifications vs Requirements: The posting has "WHAT YOU’LL NEED" (requirements) and "BONUS POINTS" (nice-to-have). Could map WHAT YOU’LL NEED to Requirements or Qualifications. We'll use Requirements for must-have, and Skills for bonus? Or Qualifications for must-have and Skills for bonus. Let's decide: Use
Requirements
for WHAT YOU’LL NEED. UseSkills
for BONUS POINTS (nice-to-have). Also maybe include Qualifications? Could combine but better to have Requirements and Skills. About the role: Could be the introductory paragraph "ABOUT THIS POSITION" plus maybe team description. We'll put About the role with that content. Responsibilities: WHAT YOU’LL DO. Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit details. So we need to include all bullet points etc. We need to format lists using- . For prose use
. We need to avoid filler like "commensurate with experience". Not present. Now produce HTML. Let's extract content. ABOUT THIS POSITION paragraph: "Aceable is looking for a Sr Analytics Engineer who likes solving holistic data problems. This is a hands-on role that sits on a small team at the intersection of Data Engineering and Business Intelligence. In this role, you’ll be empowered to solve high-visibility data architecture and pipeline problems from beginning to end. One week you might build a new data pipeline or troubleshoot why data isn't landing where it should. The next week, you could be designing a dbt model, creating a semantic view or AI agent in Snowflake, building a Power BI dashboard, or partnering with a stakeholder to turn a fuzzy business question into a data product people can actually trust and use.We don't expect you to be an expert in every tool we use. We do expect meaningful technical depth in multiple areas, strong problem-solving instincts, experience and excitement around AI, and the curiosity to jump into unfamiliar territory when the problem calls for it.If you like variety, autonomy, solving messy problems, and building things from source data all the way through to the person making the decision, you will love working with us." We'll keep as prose. WHAT YOU’LL DO (Responsibilities): List items: - Own data products end to end. Take a problem from source data all the way through to the dashboard, metric, or workflow someone actually makes a decision with. Design, build, test, deploy, and maintain the whole path rather than handing it off at each layer. - Turn fuzzy questions into things people trust. Work directly with partners in Marketing, Product, Finance, and Engineering to figure out what they're really asking, then build something reliable and maintainable enough that they stop asking you and just use it. - Own quality from source to screen. Build the testing, documentation, monitoring, and data quality controls that keep trust high, and when something breaks, chase it wherever it actually lives: pipeline, transformation, model, metric, or report. - Leave the platform better than you found it. Improve architecture, simplify workflows, and automate repetitive work, including using AI well to move faster on coding, investigation, testing, and documentation, while holding the line on accuracy and human review. We'll put each as
- .
WHAT YOU’LL NEED (Requirements):
List items:
- 7+ years of experience in Analytics Engineering, Data Engineering, Business Intelligence Engineering, or a similarly technical data role
- Advanced SQL and hands-on experience building production-scale transformations in a cloud data warehouse, ideally Snowflake, dbt, and GitHub or close equivalents
- A strong understanding of dimensional modeling, data marts, data quality testing, documentation, version control, code review, and software development lifecycle practices
- Experience with at least one data integration, ETL/ELT, orchestration, or event-data platform, plus a solid understanding of how data moves from source systems through transformation and into downstream reporting
- Experience building semantic models, DAX measurements, dashboards, and self-service data products using Power BI or an equivalent modern BI platform
- The ability and judgment to take a highly ambiguous business problem, ask the right questions, and turn it into something reliable and maintainable, plus the communication skills to do that with deeply technical partners and stakeholders who just need the data to make sense
- Experience building semantic layers, AI agents, or automated workflows that support generative AI and natural-language analytics and a willingness to use AI responsibly to accelerate technical work, automate repeatable processes, and continuously expand your capabilities
We'll keep as list.
BONUS POINTS (Skills):
List items:
- Hands-on experience with Matillion or Segment
- Experience supporting digital event instrumentation and transforming customer journey, product usage, and marketing data into trusted, analytics-ready datasets, especially in support of Marketing, Product, Finance, or executive decision-making
- Familiarity with APIs, JSON, Python, Git, CI/CD, and automated deployment workflows
- Experience with data observability, lineage, governance, privacy, role-based access, and warehouse cost optimization
We'll keep as list.
ABOUT ACEABLE (company description) maybe not needed as a section; but could be part of About the role? The instruction: include a section ONLY when posting has real, specific content for it. About the role we already have intro; we could also add About the company but not required. We'll skip.
ABOUT THE BUSINESS INTELLIGENCE & DATA ENGINEERING TEAM: could be part of About the role or maybe we could add a section "Team". Not in allowed headings list; we could incorporate into About the role.
ACEABLE PERKS (Benefits):
List items:
- Join one of Austin's Best Places to Work in 2024 & 2025
- Competitive total rewards (base salary + bonus/stock options, if applicable)
- 401k match
- Robust medical, dental, and vision benefits
- Generous paid time off programs + 19 paid holidays per year
- Flexible work schedule
- Wellness programs
- Our own space on the top floor of a downtown Austin building with free parking
- Weekly lunch, a fully stocked fridge, and plentiful snacks
- Company events and activities (holiday events, happy hours, volunteering)
- #PursueGrowth Reimbursement ($600 per year for full-time employees)
- Free Roadside Assistance subscription
- Passionate teammates excited to help you succeed and learn
We'll keep as list.
Compensation: Pay section: "$140,000 - $154,000". We'll put as
. Schedule: we have "Flexible work schedule" already in benefits; also hybrid work environment note. Could create Schedule section with that info. But we already have flexible work schedule under benefits; maybe better to keep schedule separate: "Flexible work schedule; hybrid work environment (ability to work in office or remote based on role/department and location)". We'll include Schedule section with that. We must not include location list (Remote Hires I Aceable is only able to hire employees in the following locations: ...). That's minor metadata; we can drop. Now produce HTML. Structure:
About the role
... (intro paragraph)
Responsibilities
- ... ...
Requirements
-
...
Skills
-
...
Benefits
-
...
Schedule
Flexible work schedule; hybrid work environment with ability to work in office or remote based on role/department and location.
Pay
$140,000 - $154,000
Check we didn't miss any substantive info: The intro also mentions "We don't expect you to be an expert in every tool we use...". That's included. We omitted the sentence "We don't expect you to be an expert in every tool we use. We do expect meaningful technical depth in multiple areas, strong problem-solving instincts, experience and excitement around AI, and the curiosity to jump into unfamiliar territory when the problem calls for it." That's in intro; we kept. We omitted "We move fast, ship to real students in weeks, and give our people genuine end-to-end ownership." That's in About Aceable; we omitted About Aceable section; maybe we should include that as part of About the role? It's substantive about company culture. Could add to About the role paragraph after intro. Let's incorporate that sentence into About the role. Also "We’re proud that our students consistently outperform competitors on pass rates." That's also in About Aceable. Could add. Also "Our courses are mobile-first, fully accredited, and built around one obsessive question: what's the most effective and engaging way to get someone to actually learn this?" That's also About Aceable. We could add a short paragraph about Aceable mission etc. Since we have About the role section, we can expand it to include company description. That's allowed. Thus About the role will contain: - Intro about position. - Company description: Aceable helped 20 million people..., profitable, growing, investing in AI, courses mobile-first..., students outperform competitors, move fast, ship to real students in weeks, give people genuine end-to-end ownership. We'll combine. Now ensure we didn't miss any bullet: "Our own space on the top floor of a downtown Austin building with free parking" included in benefits. "Weekly lunch, a fully stocked fridge, and plentiful snacks" included. "Company events and activities (holiday events, happy hours, volunteering)" included. "#PursueGrowth Reimbursement ($600 per year for full-time employees)" included. "Free Roadside Assistance subscription" included. "Passionate teammates excited to help you succeed and learn" included. Now check for any other substantive info: "NOTE: Our team is currently working in a hybrid work environment with flexibility