Skip to content
Wade WildboreContact

About

Wade Wildbore.

I’m a senior solution architect and software engineer based on the Horowhenua coast.

I started programming at 13 and have kept the same interest in creative work, solving problems and building software. I earned a Bachelor of Information and Communications Technology from UCOL in 2015.

My career has taken me from software development and technical leadership into solution architecture. I work across applications, APIs, data, infrastructure, operations and connected devices, and I care most about software that’s still easy to change years later.

I like owning a problem end to end: working out what’s actually needed, designing it, building it and keeping it running. I can find my way around design tools, but engineering and architecture are where I spend my time.

Outside work I enjoy working on anything with an engine, riding motorcycles and spending time with my family. My own projects include Bluu CMS, which powers this site, and My Ride. Since 2009 I’ve also done client work under the name Bluu Interactive, mostly websites for local businesses.

What I work with

Architecture and design

Solution design across web applications, mobile, backend, cloud and embedded systems. Domain modelling, distributed systems, event streaming, identity, multi-tenancy, APIs, data modelling and legacy modernisation.

Engineering and delivery

JavaScript and TypeScript, Java, Kotlin, Rust, Go, PHP, Python, C and C++. Cross-platform mobile, web applications, REST and GraphQL APIs, serverless and container backends, firmware, connected devices, automated testing and continuous delivery.

Platform and operations

AWS, Azure, GCP and on-premise systems; infrastructure as code, provisioning, containers, orchestration, Linux and Windows administration, networking, CI/CD, observability, performance, availability and incident response.

Technical leadership

Technical direction within delivery teams, mentoring, code review, engineering standards and requirements analysis, and writing architecture decisions down so the whole team knows why. I lead by staying hands-on.