Principal Software Engineer

• Senior individual contributor with organisation-wide technical impact across a 15-engineer team

• Hands-on: you will write code regularly alongside leading architectural direction

• Owns AI transformation of the engineering org alongside the VP of Engineering

• Leads the Architecture Guild: sets technical direction and holds the team accountable to it

• Coaches and pairs with engineers as a primary responsibility, not an afterthought

• Greenfield opportunity: evolving a live platform from monolithic architecture to an AI-ready, scalable foundation

• Lead Architecture Guild sessions: set technical direction, document decisions, hold the team accountable

• Drive Hyble’s AI transformation: LLM integrations, RAG pipelines, intelligent feature development, and AI adoption across the engineering org

• Pair with engineers on complex technical challenges, solving problems with them rather than for them

• Mentor and coach engineers through code review, hands-on collaboration, and 1:1 technical guidance

• Own the transition of the platform architecture toward a scalable, AI-ready foundation without disrupting live enterprise clients

• Be the trusted technical voice in build vs buy, platform strategy, and tooling decisions

• Identify and close technical knowledge gaps across the three product squads

• Contribute to technical hiring and assessment as the team grows

• Engineers across all three squads are visibly improving their technical judgment

• AI tools and practices are embedded in the engineering workflow with measurable adoption

• Architecture Guild is running consistently with clear documented decisions

• At least one meaningful platform architecture improvement is in production or clearly underway

• You are trusted by the engineering team and operating as a genuine partner to the VP of Engineering

• Experience with .NET Core, React, or Azure cloud infrastructure

• Background in B2B SaaS, MarTech, or enterprise software

• Experience with vector databases, RAG pipelines, or semantic search

• Track record of running or contributing to architecture review processes

• Experience in a scale-up where you’ve had to build practices, not just inherit them

• The ivory tower architect: produces strategy in isolation, expects others to execute

• The solo performer: measures success by personal output, not by how the team around them has grown

• The framework collector: leads with methodology rather than judgment

• The passenger: waiting for the architecture to be perfect before engaging

Missing a few requirements? Good roles stretch you. If you’re 70% there and hungry for the rest, we want to hear from you.