Small teams. High leverage. Frontier work.
Rangle is engineers, designers, and product leaders rebuilding what software consulting looks like in the agentic era. We ship work traditional consultancies can't keep up with and enterprise teams can't pull off alone. If you're looking for somewhere to practice on the frontier, not just keep up with it, keep reading.
Open roles
Pick a role on the left to see the detail and apply. We read every application that comes in.
- Location
- Remote (Greater Toronto Area, Canada)
- Timezone(s)
- ET
Agentic Product Leads own product strategy and delivery on our cross-cutting client engagements. The work is technically cross-cutting and politically real on the client side, though the shape of the problem is usually further along than the principal-tier 0-to-1 work owned by our Principal Product Leads.
This is not a delivery PM role. Backlog management, ceremony facilitation, and status reporting are the floor, not the bar. We are hiring for judgment, taste, and conviction: the ability to identify the part of an enterprise problem that is actually hard, and drive the team toward a defensible answer. The Agentic Product Lead is expected to raise the technical and strategic ceiling of the working team, including conversations with our Solution Architects and the client's product and engineering leadership.
You report to the VP of Agentic Product & Platform Strategy, sit in the Platform Delivery Studio, and run at a 90% billable target.
Why Rangle
Rangle is making a deliberate bet: 12 years of lean, agile, and CX practice applied to agentic systems, and a wager that agentic is a platform engineering problem, not a project engineering problem. We're building sovereign, antifragile infrastructure that clients can actually own (Paddington.io), so they aren't permanently dependent on someone else's agent platform.
Successful agentic systems are as much about culture, experience, and trust as they are about expertise and capability, and we want product leaders who find that exciting and want to help us deliver on it in real client work. The product leaders we want are people who'll learn alongside the team, add to the lessons we've earned so far, and help us turn the next round of hard-won experience into something the next engagement gets to start from.
What We're Looking For
- Problem-shaped thinking. You describe past work by the hard parts (the schema conflict, the regulatory constraint that broke the obvious design, the integration that looked simple and wasn't), not by phases and deliverables
- Specificity and ownership. You can name the trade-offs you made and why. You hold a view on technical choices adjacent to your work, even when provisional, and you stay close to decisions that shape your roadmap
- Empirical definitions of success. You can answer "how did you know it was working" with something concrete: a leading indicator, a falsifiable hypothesis, a behaviour that shifted, an outcome metric tied to a real decision
- Insight pulled across context. If you've worked across industries, you can name the thread that generalised and what didn't. The synthesis is the credential
- An internal engine. Curiosity that goes past the work surface. You read, build, and form genuine opinions about tools and methods
- Systems-level thinking. You guide a high-performing system rather than letting it collapse to your bandwidth and control
- Ceiling-raising. When you join a working team, the technical and strategic ceiling of the conversation goes up. You ask the question that reframes the problem or take a position the room hadn't considered
Major Responsibilities
- Discovery. Run continuous discovery: story mapping, stakeholder interviews, assumption testing. Surface the hard problems early, while there is still room to shape the response
- Delivery clarity. Own flow metrics, RAID, and clear reporting to client product and engineering leadership. Communicate progress and risk plainly, including when the news is hard
- Stakeholder partnership. Primary product voice to client product owners, engineering leads, and senior stakeholders. Build the kind of trust that lets you tell partners what they need to hear, and have it land
- Team coordination. Partner with Solution Architects on sequencing and trade-offs. Represent the product lane at the same table as design and engineering, not downstream of it
- Agentic Product Engineering. Hands-on in the prototype and feature layers. Everyone develops here, but our agentic harness engineers and agentic systems engineers (experts in system architecture, operations, and quality engineering) handle the deeper technical considerations
- Agentic and platform strategy. Drive client alignment on agentic tooling permissions, evaluation regimes, and human-in-the-loop levels. Bring a clear, defensible point of view
Skills and Experience
- 5+ years in product, with at least 2 years in platform, infrastructure, or genuine 0-to-1 work where the shape of the product was still being figured out
- Direct experience with enterprise clients in regulated or organisationally complex environments. You can describe a specific moment where a constraint forced a non-obvious product call
- Strong working knowledge of front-end architecture, API orchestration, data integration patterns, and cloud-native concepts. You don't write code, but you can engage substantively with architects and offer a real point of view when you disagree
- Continuous discovery practiced in parallel with delivery. The portfolio evidence we want includes a hypothesis you killed, not just features you shipped
- Familiarity with agentic AI tooling, LLM-assisted development workflows, and AI governance considerations. This is a working knowledge requirement, grounded in hands-on use rather than personal-task curiosity
- Consulting or significant client-facing delivery experience. Builds trust quickly with senior client stakeholders while holding your own line
- Clear written and verbal communication. You write in your own voice rather than reaching for stock product-management phrasing, and you describe work in terms specific enough that a reader can tell which engagement you mean
How We Hire
- A technical depth probe on a past engagement. You pick the engagement; we pick the layer to dig into
- A live exercise structuring an ambiguous brief. We are evaluating decomposition, what you ask first, and what you defer
- A conversation about a tool or method you've changed your mind about, and why
- References focused on whether you raised the ceiling of the rooms you were in
Working Relationships
Internal: VP of Agentic Product & Platform Strategy, Principal Product Lead, Managing Director, Solution Architects, Developers, Product Designers, Director of AI Strategy
External: Client product owners, engineering leads, design leads, and senior stakeholders
Don't see the right role? We're always interested in strong candidates; pick the closest match and tell us about yourself in the cover letter.
What we're building
We run agentic development as a first-class practice. Not "we use AI tools." Not "we're experimenting with Cursor." We've reshaped how teams compose, how delivery works, and how software gets shipped around the reality that AI has changed the math.
Concretely, that looks like:
- Small integrated teams, not staffing pools. A typical engagement is 3–5 people owning an outcome end-to-end, not a line of developers handed tickets.
- AI-native from the first line of code. Claude Code, MCP servers, spec-driven development, agent orchestration. We use the tools our clients are trying to figure out.
- Real platforms, not just apps. Postgres with RLS, Kubernetes via Kilter, event-sourcing where it fits, design systems that outlive the engagement. Clients own what we build for them.
- Sovereignty as substrate. More of our clients need to own their software, their data, their models, their tooling. We help them do it.
We're pragmatic about stacks: the right tool for the context. We care about stack fluency, not stack loyalty.
Platform & Infrastructure
Container orchestration, declarative control planes, GitOps-driven delivery, long-running workflow orchestration, event streaming, identity, and observability. A solid relational database underneath. Specific tools rotate by engagement; the architecture principles don't.
Application Layer
A modern TypeScript and React foundation, paired with whichever libraries and frameworks fit the project. We favor type safety, strict tooling, and patterns that travel across engagements.
Agentic Layer
We're implementation-agnostic at the agentic layer. Claude Code is our daily driver today; the tools shift as the frontier does. What travels across projects is the durable team judgment we encode as skills, rules, subagents, and reusable patterns.
Deployment Targets
Client-owned infrastructure when that serves the client (including Canadian data residency), hyperscalers when context demands it. Our default is stacks clients can own, operate, and evolve.
How we work
We organize every engagement around a consistent core team: three roles working together end-to-end, not seniority bands.
Agentic Managing Director (AMD)
Client-facing, owns the engagement and the outcome. Builds trust, navigates ambiguity, drives value creation.
Agentic Systems Engineer (ASE)
The architecture layer. Front-end, data, infrastructure, design systems. Builds the meta-systems that let the rest of the team move fast.
Agentic Product Engineer (APE)
Ships inside the scaffolding ASEs build. Moves fast, grows toward ASE or AMD over time.
Alongside the triad, Design, Product, and Delivery sit as supporting roles: specialist expertise that joins the core team where the engagement needs it.
Design
Taste, pattern, aesthetic direction. Shapes how the team's work looks, feels, and holds together across a single engagement and across the design systems we leave clients with.
Product
Client problem depth, business value sense, trade-off judgment. Partners with the AMD to shape what gets built and why it matters, not a translation layer between business and engineering.
Delivery
Execution discipline, risk navigation, launch readiness. On our largest engagements, partners with the AMD to make sure complex, multi-stakeholder programs actually ship on time and on scope.
Moving between roles takes reps. Our internal model is 400 hours of flight time (roughly four months of real engagement work) to move from a classical developer to a fluent agentic one. We coach you through it, but you fly the hours.
Beyond flight time, we run katas: protected weekly time for deliberate practice against a diagnosed gap, with a coach who has watched your work and can name what to push on. AI compressed the incidental learning that used to come from typing code and reading senior PR feedback. Katas are the deliberate replacement, not a supplement — reading, reps, and feedback against a real surface.
We're small enough that the people you meet on day one are the people making the decisions. Culture here is a village, not a train station: trust, safety, accountability, doors left unlocked. We know each other. You'll be known.
What we look for
We look at every candidate across three dimensions, in this order.
Character first. We care most about people who own outcomes rather than diagnose problems from the sidelines, who hold themselves to a high internal bar without waiting for external pressure, and who make the teams around them better. Character is the hardest thing to develop after hire, so it's the first thing we screen for.
Context second. In the agentic era, AI compresses raw technical work. The gap between a good and great hire shows up in judgment: do they understand what should be built, not just what was asked for? Can they read a room? Can they hold their ground with a stakeholder when the pressure is on?
Craft third. Table stakes, but shape-shifting. We care less about accumulated expertise in any one stack than about how fast you build mental models in unfamiliar territory. Our people rotate across clients and industries. Deep domain knowledge can become a trap; investigation instinct matters more.
Across all three we run four cross-cutting lenses.
Taste
Good vs great.
Talent
Raw ceiling.
Tempo
Pace.
Tenacity
Push through.
If you already work in an agentic style (systematic, spec-first, can articulate why a workflow works and not just which tools you use), you'll be at home here.
What we're not
We're not a body shop. We don't sell seats, hours, or bodies-to-tickets. If you want a large team, a well-defined scope, and someone to hand you work each sprint, we're not the shop.
We're not Accenture-with-AI. We're not adding a Claude license to the same old delivery model. We've rebuilt the model.
We're not a soft landing. The bar is high. Character first, but craft is real, and the work is real. If you're looking for an easy ride, this isn't it.
If those three descriptions are what pushed you out of your last job, keep reading.
The basics
We cover what you'd expect: health and dental from day one, flexible hours, remote work, RRSP matching, a wellness budget, a professional growth budget, and accessibility support throughout the recruitment process.
What we don't do is make the basics the story. They're table stakes. The story is the work and the people.
Interview FAQs
Accessibility statement
Rangle is committed to meeting the accessibility needs of those with disabilities throughout our recruitment process. We believe in dignity, independence, integration, and equal opportunity for candidates of all abilities who want to be a part of our team of Ranglers.