I'm a computer science senior at the University of Evansville, graduating May 2027. Most of what I know I picked up by building things for other people — a couple of internships, a year-long research partnership, and a lot of evenings working out why something wasn't behaving. Backend services, AI agents, integrations, data tooling.

What I've been working on

At Guidepath Consulting I work on AI agents and the plumbing underneath them. The project I've learned the most from is an AI sales agent that lives in Outlook: it reads incoming orders and answers questions about products and order status right in the reply thread. Behind it are the Model Context Protocol servers I built to give it live Dynamics 365 data instead of a stale export. Getting to work on both halves was the useful part — I could see what the agent kept reaching for and go change the data layer to match.

Alongside that there's been a steady stream of integration work: a Shopify to Dynamics 365 Business Central order pipeline on Celigo, Power Automate flows keeping Azure DevOps and Planner in sync, and more recently Boomi development for a telecom client's ERP rollout. None of it is glamorous, but it's the kind of work that quietly takes a recurring chore off somebody's plate.

The research year

Through Purdue's Data Mine I spent 2025 on a student team working with AstraZeneca on their manufacturing data. We built an Intelligent Data Model to turn unstructured equipment data into something the business could actually query, and replaced paper Quality Control logbooks with a digital system. The regulated-environment part was the real education: digitizing a record is the easy half, and keeping an audit trail that holds up is where the actual requirements live.

How I like to work

I like following something from requirements all the way to deployment, mostly because that's where I find out which of my assumptions were wrong. I've been lucky to work on small teams, so a lot of the job has been asking questions early and checking my read of a problem with the people who use the system every day. And since whatever I build usually gets handed off eventually, I try to leave it in a state someone can pick up without me in the room.

What I'm looking for

New-grad software engineering roles starting after I graduate in May 2027 — backend, AI tooling, platform, or something near those. I'd like to keep working on things with real users and real data, on a team where I can learn from people further along than me.