Analytics engineering + applied AI

I build data systems people can trust.

I'm Josh Bickmeyer. I've spent more than 12 years building data products that help teams answer real business questions. Lately, I've been applying the same discipline to AI workflows.

Josh Bickmeyer working at a laptop in a modern data workspace
Josh BickmeyerData + AI systems

I work where data engineering meets
business decisions.

12+years in data
4analytics engineers led
$2M+opportunity surfaced

Selected work

Projects built around
how work actually happens.

These projects show how I work. I start with the workflow. Then I make the boundaries obvious and keep the evidence needed to debug what happened.

01 / 03Selected project

Mission Control

AI-assisted software delivery without pretending every decision should be automated.

Mission Control coordinates the work between an idea and a live release. It keeps research, PRDs, implementation, review, and deployment in one system.

Why it matters

I built approval gates into the places where an agent should stop and ask. Releases reuse the same artifact, so testing and production do not quietly drift apart.

  • AI orchestration
  • Product systems
  • Release engineering
02 / 03Selected project

AI Analytics Engineering

One pipeline, from raw data to a dashboard someone can use.

This personal platform ingests data with dlt, transforms it in dbt, runs through Airflow, and publishes BI-ready models for Power BI.

Why it matters

I use it to test whether AI can speed up repetitive analytics work without weakening model tests, lineage, or code review.

  • dlt + dbt
  • Snowflake / Redshift
  • Airflow + Power BI
03 / 03Selected project

Personal AI Assistant

An assistant is only useful if I can tell what it did.

This system uses specialized agents and Postgres-backed memory to handle email triage, calendar digests, and outbound calls.

Why it matters

It is where I test the unglamorous parts of agent work. I limit permissions, require a human check, and make failures recoverable. If it is not worth maintaining, I cut it.

  • Agent systems
  • Postgres memory
  • Workflow automation

These are working personal projects, but their active repositories are private. My public repos and open-source contributions are on GitHub ↗.

What I bring

I still write the SQL.
I also care who has to use it.

I've spent more than a decade taking messy business questions back to the data. That work has included dbt models, Python pipelines, and dashboards used by business teams.

These days I spend a lot of time on AI. I care less about demos than whether the workflow can be trusted in production. I like staying close to the code. When a pipeline fails at 6 a.m., someone should know what changed and where to look.

01Data engineering

SQL, Python, dbt, Airflow, Snowflake, Redshift, AWS S3

02Delivery systems

GitHub Actions, CI/CD, Docker, testing, monitoring

03Analytics

Power BI, Tableau, semantic models, KPI design, forecasting

04Applied AI

Agent workflows, RAG, AI-assisted engineering, human review

Experience

The titles changed. I stayed close to the data.

Insurance, consulting, consumer goods, and retail analytics.

2022 to presentAnalytics Engineer

AAA Life Insurance

2021 to 2022Data Analytics & Engineering Contractor

Independent

2014 to 2021Data Analyst

Kellogg Company

2012 to 2014Data Analyst

Schwan's Consumer Brands

Start a conversation

Have a hard data problem?
Or an AI idea that needs discipline?

If you're working through a brittle data platform or trying to put an AI workflow into production, I'd like to hear about it.