A bit about me

I studied computer science at Central Michigan University and joined Ford right out of school. Early roles had me in data supply chain and AI engineering: Angular dashboards, computer vision on vehicle imagery, high-performance compute pipelines. That background still shapes how I think: observability, data quality, and whether something scales beyond a demo.

Mobile clicked when I started shipping customer-facing software that millions of people touch. I moved into Ford Credit's mobile team and gradually specialized in iOS, eventually focusing on Swift, SwiftUI, and the native rewrite alongside a large distributed engineering org.

I'm one of two local iOS developers on a team spread across time zones, so clear communication and solid code review matter. I'm comfortable owning a slice of architecture, especially analytics and instrumentation, while staying honest that big platform moves are team efforts.

I like pairing with design and backend early, writing tests where they earn their keep, and leaving the codebase easier for the next person. Enterprise constraints (compliance, release trains, legacy RN alongside native) are part of the job, not excuses to ship sloppily.

Useful product outcomes over resume bullet theater. Reliable payments and auth flows. Analytics that product and engineering can actually trust. Mentoring newer mobile engineers when I can.

I'm happiest when I can point at something in the App Store and say I helped make that experience better for real customers, not just that I attended the meetings.

I tinker with SwiftUI samples to try patterns before bringing them into production work. I'm always up for a good conversation about iOS architecture, GraphQL on mobile, or where Detroit's tech scene is heading.

Off the clock I keep up with Apple platform updates, spend time around Metro Detroit, and prefer small side projects over chasing every new framework. If you want to talk shop or compare notes on mobile, reach out through the contact page.