Computers felt like magic to me growing up, and getting to build things with them never really lost that feeling. Working on customer software also taught me how quickly that feeling goes away when someone simply can’t get into their account. They don’t care which service broke. They need to know what happened and what they can do next. Making that experience work, without making the underlying controls weaker, is the part of this role that caught my attention.
At Technomancy IT, I built a client operations platform that puts support, scheduling and billing in one place. The staff and customer workflows use shared services, but they don’t get the same access. I worked on the application and API authentication, the PostgreSQL data layer, and the checks that let me see whether a deployment actually worked. At Front Range Internet, I built NOC diagnostics and handled escalations. Those shifts taught me to make problems easy to trace and to leave checks another operator can use.
Most of my recent backend work has been in TypeScript. I’d bring that experience with APIs, access boundaries and production debugging to Affirm while learning the team’s Python or Kotlin services and identity tooling. I’d like to be the engineer who can follow an account issue from what the customer sees to the service that caused it, then leave that path a little easier to operate.
Chad Koslovsky