Jordan Schaenzle

Software Consultant & Developer, Grand Rapids

Jordan Schaenzle

Ever since my dad brought home our first computer (a Packard Bell) back in the early 90's, I have been intrigued by computers. Electronic devices in general have always excited me and, as a child, I was filled with curiosity of how they work. I used to take apart every remote control car, FM radio—you name it. If I could open it up with a screwdriver, I would!

My curiosity continued throughout high school, and I decided to pursue a degree in electrical engineering. I went to Calvin College and received a B.S. in Electrical and Computer Engineering. While attending Calvin, I had the opportunity to participate in an internship at Schrader Electronics. Schrader is a tier-2 automotive supplier of TMPS (Tire Pressure Monitoring Systems). Their headquarters is in Ireland but I worked in the Rochester, MI office as a technical liaison between Schrader and Chrysler. I also had the opportunity to test a lot of Schrader's new products on pre-production vehicles.

My first job after college was at Innotec in Zeeland, MI. At Innotec, I designed machines that assemble automotive components in an automated fashion. The goal of every machine was to have the least amount of human interaction as possible. I enjoyed working at Innotec, but I was doing a lot of mechanical engineering there and I really wanted to use my electrical degree more.

I decided to accept a position at Optec Inc, in Lowell, MI. Optec is a small company of about 9 employees and at that time they were in need of an engineer. While working there, I was essentially a one-man engineering team. I designed circuits, laid out PCBs, wrote embedded firmware and PC software, and even did some production circuit assembly. After a couple of years at Optec, I started feeling the desire to work with a slightly larger team of people. I wanted to work more closely with experienced software developers that could help me to continue to grow in my field. A friend recommended that I check out Atomic Object.

I joined Atomic Object in 2011 and since then my eyes have been opened to what it means to write clean, well-architected code. I have worked on a wide range of projects from complex embedded systems to full-stack web and mobile applications.

I am passionate about writing effective, clean code. I love automated testing and getting my hands into hardware. I look forward to working with you on your next project!

Papers and Presentations

The Atomic Team