Principal Architect

Principal Architect

We're hiring a Principal Architect to lead Granum's Architecture team and help drive the development of our technical roadmap. This is a hands-on player/coach role in which you'll lead a small team of architects and work in the code alongside them. You'll report to the CTO and work shoulder-to-shoulder with our Platforms, Product, and feature-pod leaders.

Our products are real, mature, and used every day by landscape professionals to run their operations. That means the interesting problems aren't greenfield; instead they are about executing a clean go-forward architecture and pulling a large, living codebase toward it without stopping the business. You'll help drive the application and system architecture across the portfolio, plan and develop platform upgrade tooling and processes (Angular, .NET, shared libraries), and reduce the technical debt that spans teams. Your job will be to provide the stable, secure, scalable foundation that feature teams build on by reducing systemic friction and clarifying technical direction so teams can deliver value quickly and confidently.

We're also an AI-native engineering org. We expect agents to do a lot of the heavy lifting on code, and part of your job will be to make our architecture legible to both engineers and coding agents, which includes clear patterns, good context, and docs that live where they belong. If you think the future of this craft is orchestrating and reviewing rather than typing every line, you'll fit right in. This is a role for someone who has real opinions about architecture but holds them loosely enough to serve the team. We believe in YAGNI, KISS, boring technology, and community solutions over custom builds. Good architecture here means less complexity for the pods, not more.

What You'll Own

• Technical Roadmap Execution. Turning Granum's architecture roadmap into sequenced, visible work. That includes spotting cross-team dependencies during quarterly planning, before pods run into them mid-sprint.

• Standards and the foundation. Architectural standards and guardrails, and the patterns for how we build a component and wire it into the existing app. Each component should do one thing well and be well tested.

• Platform and technology stewardship. Planning and coordinating major upgrades (Angular, .NET, shared libraries), evaluating new technologies, and driving down cross-team technical debt.

• Deployment and delivery enablement. Deployment patterns and shared CI/CD guidance that let teams own the deployment of their own code with system-wide consistency and safety.

• Security posture. Application security and how identity and access work, and how our APIs are exposed and secured.

• The AI-native development model. Defining how humans and agents interact in our process, and making sure our architecture supports agentic development.

• The Architecture Pod. Leading, growing, and setting the operating rhythm for the Architecture Pod, and keeping it focused on foundation work.

What You'll Need

• A track record as a hands-on architect. You've led the architecture of a non-trivial, production SaaS platform and driven a real codebase from where it was to where it needed to be. You can still read and write code credibly; you're a leader who architects, not an architect who's stopped building.

• Depth across our stack. You have deep .NET experience including modernizing legacy .NET Framework systems. Angular, Azure, and AWS experience is a plus.

• Systems and integration architecture. You think naturally about how applications and services fit together (integrations, data flow, deployment topology) and how to evolve them safely over time.

• API architecture. You understand how to expose, secure, and version APIs, who's integrated and how, and how to change an API surface without breaking the people who depend on it.

• A security-first instinct. You reason about auth, access, and exposure by default, and treat security as a property of the architecture rather than a later add-on.

• Systems thinking and pragmatism. You fight complexity. You default to boring, well-understood technology and community solutions over bespoke builds, and you can tell the difference between architecture that unblocks teams and architecture that just looks impressive.

• Fluency with AI-assisted development. You're comfortable with agentic coding tools as a primary development mode, and you have views on how to make a codebase and its patterns work well for both engineers and agents.

• Product and Customer Focus. You've worked closely with product managers and tie technical decisions to customer outcomes. You see Product as a partner, not an obstacle.

• Leadership. You've led engineers through feedback and unblocking. This includes setting direction, growing people, and running a healthy team rhythm.