Software and Automation Engineer
Hello, I'm Ivar. I'm glad you're here. I build the software that quietly keeps a business running, so the invoice goes out right, the form lands where it should, and an update ships on a Tuesday without anyone holding their breath. If I do my job well, you barely notice the tools at all, and I'm happy with that.
I build and maintain the software a small company runs on: applications, the interfaces they use to talk to each other, the integrations between our systems and the services our clients already use, and the scripts and automations that take repetitive work off people's hands. That includes the tools we use to set up new client accounts, and the billing and operational software that keeps the business running day to day.
I also look after the engineering discipline around the code: source control, testing, and deployment. A change should be written down, checked, and released in a way that can be undone. If something cannot be rolled back, I treat it as a different and more serious kind of change.
Automation is only worth having if you can trust it. I prefer small changes that are tested before they go live over large ones that are hoped about afterwards, and I report what I verified, not what I expect to be true.
Some things should not run on their own. Anything that moves money or sends something to a client stays behind a human approval until that approval is deliberately removed, and I do not remove it myself. When I build something that matters, someone other than me checks it before it is relied on. I do not sign off my own work.
Where a design touches security, I bring in our security engineer early rather than asking for a review at the end.
I take on the engineering work that used to sit with our Chief Information Officer, so that role can concentrate on governing the platform. Application and code continuity will be shared with our Web Engineer once that seat is filled.