Wagner Osborne
Memphis, TN
ABOUT
PROJECTS
EXPERIENCE
RESUME
MENTORSHIP
SKILLS
HONORS
CONTACT
LIFE
Wagner
Wagner
Osborne
Full-Stack
Engineer
$ whoami --verbose
Wagner Osborne_
name: Wagner Osborne
location: Memphis, TN
role: Full-Stack Engineer
employer: International Paper
education: MIS @ University of Alabama
origin: Naperville, IL
interests: [ai, web, running]
$ cat bio.txt

I'm Wagner, a full-stack software engineer based in Memphis, TN who genuinely loves to build things... at work, for friends, and just for fun. For me, coding has always been less about the technology and more about the people it connects and the problems it solves.

I grew up in Naperville, IL as a creative kid who loved art but couldn't quite find her medium. Turns out it was code. My first real project was a fan site for The Office complete with quizzes to tell you which department you'd work in, and something just clicked. By high school I was building mood-based song lyric generators and running trackers just for fun. I went on to study Management Information Systems at the University of Alabama, and found so much more than a degree there. I spent three years as a Teaching Assistant mentoring 240+ students, helped pioneer the Southeast's first female-led hackathon as UA Innovate's Hackathon Operations Lead, and discovered that I love helping people grow just as much as I love building things.

What drives me is building things that actually matter to real people. Dingerz started because my friends needed a better way to run a home-run-only fantasy league, and now they use it every single baseball season. I've built a beer mile prop bet app, AI-powered training tools for my own running, and countless side projects just because a problem felt worth solving. That instinct — seeing a need and building the thing — is what I bring to work every day too.

Working on real enterprise systems has taught me that good engineering goes way beyond writing clean code. Digging into legacy architecture at International Paper showed me why those monolith decisions were made. Tradeoffs are real, context matters, and it's easy to judge a codebase until you understand the problem it was solving at the time. As AI continues to evolve, I believe our role as developers is shifting toward something more like architects and orchestrators — thinking deeply about non-functional requirements, system design, and the bigger picture. It's honestly one of the most exciting times to be in this field, and I think the developers who thrive will be the ones who embrace that shift.

$ _