A credit analyst who builds the tools, and writes down what went wrong.
The Case Studies say what the work was. This page says who was doing it — what I am studying, what I have been doing and when, what I can actually operate, and why every one of those Case Studies ends by reporting a problem.
How I got here.
I am a Finance and Accounting student at the University of Wisconsin–Eau Claire, graduating in May 2027. Since May 2026 I have been embedded with the credit team at a community bank in the Upper Midwest, first as a summer analyst and now remotely, and the work has had two halves from the first week: I do the standard credit analyst work — spreading financials, writing risk assessments — and I build the tooling that changes how that work gets done.
The second half was not what I was hired for. It started because the process nobody had written down turned out to be the thing slowing everybody else down, and the fastest way to describe it was to build something that did it properly. That is the pattern the whole site is about: go into an undocumented process, find where it actually breaks, and close the gap with a tool built under constraints somebody else set. The constraints are the interesting part. At the Bank nothing may reach a cloud service and nothing may require a server, which rules out most of what a developer would reach for first and rules in a much smaller, much more deliberate set of choices.
The rest of my time goes to independent research — equity analysis, a portfolio framework, and a faculty-advised study on whether AI-generated language in filings predicts anything — and to Division III track and field. Those run at the same time as a full course load, not instead of it.
Why every Case Study here reports a problem.
Every Case Study on this site carries a What I Learned section, and it is never decorative: a defect I found in my own work, an assumption that turned out to be wrong, a perspective that changed. That is deliberate, and it is universal rather than selective, because work that never reported a problem is the work to trust least — either nothing was checked, or something was found and quietly left out. Reporting the problem is how I check myself, and it is the part of a record that is hardest to fake. It is also the part an interviewer can actually use.
What I have been doing, and when.
Exhibit 1 Four of the seven are still under way, and the newest is the bank work, now carried on remotely
Select an entry to read what it was; the current role is marked.
View the data
| Role or Engagement | When | Where | What it was |
|---|---|---|---|
| AI Integration Phase | Autumn 2026 — present | A community bank in the Upper Midwest · remote · ongoing | The relationship did not end when the summer did; it moved. The work is remote now, and pointed at AI integration and new tooling rather than at credit analysis. Engagement 02 is therefore ongoing rather than concluded. It is carried alongside a full course load and a varsity track and field season. |
| Engagement 02 — Credit Process Rebuild | Jun 2026 — present | A community bank in the Upper Midwest · on site through the summer · ongoing | Loan origination rebuilt as local-only browser tools: intake, tax-document extraction, spreads, and the approval presentation restructured into a Three-Stage Review. Begun on site over the summer and not concluded — it is what the AI Integration Phase above is a continuation of. |
| Engagement 01 — Customer Intelligence | May — Jun 2026 | A community bank in the Upper Midwest · on site | Browser-based mapping and profitability tools that gave leadership a spatial and demographic view of a customer base it had only ever seen as rows in a spreadsheet. |
| Chamber of Commerce business liaison | Apr 2026 | University of Wisconsin–Eau Claire | One of a small group of Bloomberg-capable students sent to represent the university at a Chamber of Commerce breakfast, talking to regional executives and business owners about AI, financial analysis and careers. |
| The Competition | Jan 2026 — present | Four-person team · hedge fund case competition | “Operational AI Adoption in a Winner-Take-Most Economy.” I built the language-processing and machine-learning pipeline behind the paper, and reported the two earlier periods in which the same signal pointed the wrong way rather than only the one in which it worked. |
| Merchandise and community outreach lead | Nov 2024 — Mar 2025 | Bonds Social Club | Outreach to stakeholders across 35+ institutions, a go-to-market plan for 35 merchandise items, campus bookstore placement, and 5+ partner meetings out of it. The least technical thing on this list and the one that taught me the most about getting a decision out of somebody who does not report to me. |
| Independent research | Jan 2024 — present | Self-directed, and faculty-advised | Equity analysis across US markets on Bloomberg and FactSet, a portfolio framework built on full-market sentiment signals, and The Research — the faculty-advised study on whether AI-generated language in SEC filings predicts abnormal returns, which I withdrew after catching my own false positive, and then rebuilt from the ground up. |
What I am studying, and where.
-
Bachelor of Business Administration
University of Wisconsin–Eau Claire
-
Artificial Intelligence: Implications for Business Strategy
MIT Sloan School of Management and MIT CSAIL
-
MIT Open Learning certificate
Massachusetts Institute of Technology
What I can actually operate.
The first three groups are the ones the resume uses. AI is split out of Technical here, because on this work it stopped being one more tool in the Technical list and became the thing the work was about.
Consulting
- Current-state assessment
- Process mapping
- Requirements gathering
- Roadmap development
- Stakeholder communication
- Operational excellence
Financial
- Credit analysis
- Financial modeling
- Equity research
- SEC filing analysis
- Risk assessment
- Bloomberg Terminal
- FactSet
Technical
- Python
- SQL
- HTML, CSS and JavaScript
- VBA and Excel
- Document extraction
- Automated test harnesses
AI
- AI implementation in regulated environments
- Agentic AI systems
- Prompt engineering
- Claude Code
- Language-processing pipelines
Division III track and field.
I have been on the varsity roster since September 2023, and a captain. It matters here for one reason: the academic load, the research, the Competition and the Bank work were all carried at the same time as a full training and competition schedule, not in the gaps around it. Most of what I know about protecting an unglamorous routine from a busy week, I learned there rather than at a desk.
Happy to walk through any of it.
I am seeking consulting and finance roles starting May 2027. If something here is relevant to a role or a problem you are looking at, email is the fastest way to reach me.