I’ve been writing software for more than 20 years, across retail, banking and insurance. My full-time job is Software Development Manager at Omaha National, where I’m happily employed. In March 2026, my wife Katie and I started Wallman Solutions on the side to build websites and custom software for small businesses.
Katie Wallman and I co-founded Wallman Solutions and own it together. I do all of the architecture and development: I scope the work, design the system, write the code and run the hosting. Katie handles customer support and email, and she tests what I build. On bigger projects our kids help test too.
That’s why you’ll sometimes see “we” on this site when it’s about the business. When it’s about code, technical decisions or experience, that’s me.
Career
2020–Present
Omaha National
Software Development ManagerJun 2025 – Present
Senior Software DeveloperMay 2020 – Jan 2026
My full-time job. I joined this Omaha insurance company as a senior developer in 2020, and today I manage a team of six developers. Along the way I’ve led three of our biggest software projects:
Our claims management application, which has been central to streamlining how we handle claims.
Our underwriting application, including a configurable pricing engine that handles pricing across every jurisdiction we write in.
AI modernization, which I’m leading now: building agentic applications that streamline our operations.
2019–2020
BFS Capital
Lead Software EngineerDec 2019 – May 2020
Designed and built a REST API hosted on AWS (CDK, Cognito, EC2, RDS), plus a Swagger UI portal to onboard new API clients.
Worked with the business on the corporate website to improve lead generation.
Researched and designed an event-streaming microservices architecture and started the plan to move the core platform to it.
2013–2019
Client Resources, Inc.
Solutions ArchitectApr 2013 – Dec 2019
Lead architect for every project that came through the CRi Solutions Center: mostly Java back ends, on premises and on AWS, plus Angular and Vue.js web apps and Android apps.
Mutual of Omaha (16-month contract): led several teams as architect, including a rewrite of the Customer Access application, and designed a PCI-compliant way to store, update and play back call audio.
First National Bank (8-month contract): helped modernize the Commercial Card banking application.
2012–2013
Hayneedle
Software Engineer IIIMar 2012 – Apr 2013
Lead Java EE developer on the team building the web services behind the web and mobile storefronts.
Pushed for continuous integration and automated testing, helped write the company API best practices, and mentored developers, including students from the University of Nebraska Raikes program.
2008–2012
Oriental Trading Company
Senior Java Programmer AnalystMay 2008 – Mar 2012
Analysis, design, development and testing across all of Oriental Trading’s e-commerce sites.
Built a content management tool that let the business maintain SEO content on category landing pages.
Added Bill Me Later as a payment option, which meant reworking the existing PayPal and Cardinal Commerce integration.
Lead developer on gift cards for the web and the call center, including the redemption and balance-check web service and the First Data and Arroweye integrations.
2006–2008
Firespring
Java DeveloperDec 2006 – May 2008
Analysis, design, development and testing of the Firespring Development Platform, a Java content management system.
2006–2009
Capstone Consulting
Part-time ConsultantApr 2006 – Jun 2009
Built software test environments in VMware, including install scripts for WebLogic and MySQL on Windows and Linux.
Worked on website content and helped a project manager track resources and budgets across six projects.
University of Nebraska at Omaha, Bachelor’s in Computer Science, Internet Technology concentration, 2002–2006
You can read what these clients said about the work on the homepage.
How I use AI
I use AI every day, mostly Claude and Grok. It helps me plan, write code, review and test. It makes me a lot faster, and it’s a big part of why one developer can take on work that used to need a small team.
It doesn’t decide what’s right. Every line of code that ships is code I’ve read, tested and am willing to put my name on. The judgment about architecture, security, and what to build or leave out comes from 20 years of building production software, and that judgment is what clients are paying for.
On the blog, every post starts from my own experience and opinions. I use AI to help outline, tighten the wording and check sources, then I edit and approve every post before it goes up. When a story is a composite of situations I’ve seen rather than one real event, the post says so. The featured images on the blog are AI-generated illustrations, not photos or screenshots of real client work.
Have a project in mind?
The first conversation is with me, and so is the code if we work together.