Staff Technical Lead - Billing Revenue Management

TELUS•Edmonton, AB

15h

About The Position

Join our team and what we'll accomplish together Billing is one of the most consequential touchpoints a customer has with TELUS — and one of the least loved. Our ambition is to change that: to reimagine billing as something customers actually trust, where their bill is clear, accurate, and never a source of frustration or doubt. That means more than modernizing the technology. It means rethinking the systems, processes, and engineering practices that sit behind every invoice, every account interaction, and every payment — calculating charges, generating bills, managing accounts, and reconciling revenue across millions of customers. The estate is complex, largely 20+ years old, and under active transformation. As an L5, you are the senior engineering presence across the billing domain — hands-on technically, and accountable for elevating the engineers around you. You report directly to the Director in the Billing Revenue Management domain, operate across multiple teams without direct reports, and influence through credibility and craft.

Requirements

7+ years hands-on engineering with production ownership of complex, high-volume systems
Demonstrated comfort working in environments; you reduce ambiguity rather than avoid it
Strong foundation in distributed systems: eventual consistency, event-driven architecture, high-availability design
Experience with billing, financial, or revenue systems is a strong asset
Cloud-native fluency on GCP (Kubernetes, Pub/Sub, Dataflow, BigQuery, Cloud SQL) and IaC/DevOps practices
You genuinely enjoy helping other engineers grow — through code reviews, pairing, design discussions, or documentation
Ability to explain complex concepts clearly and help engineers develop both technical depth and ownership mindset
Experience mentoring junior or mid-level engineers (doesn't need to be formal; could be peer mentoring, tech lead experience, or guild leadership)
Hands-on engineer who stays close to the code and the systems you own — not delegating away the interesting problems
Operates with ownership and transparency — surfaces problems early, shares context freely, builds trust through consistent delivery
Comfortable learning new domains quickly; billing may be new to you, but you pick up complex systems rapidly
Open to experimenting with AI development tools; comfortable integrating them into your workflow without needing to be an expert first

Nice To Haves

Direct experience with various vendor billing platforms
Background in telecom, utilities, or regulated billing environments
Experience mentoring engineers at a company or within a technical guild/community
GCP Professional certifications (Cloud Architect, Data Engineer)

Responsibilities

Design, build, and operate systems across the billing lifecycle: charge calculation, invoice generation, account management, network mediation, usage charging, and payment processing
Decompose legacy components into maintainable, internally-owned services — reducing technical debt and improving system reliability
Ensure accuracy, auditability, and reconciliation across billing workflows; own the quality bar for your subsystems
Debug and resolve complex cross-system issues in production; lead root cause analysis and implement durable fixes
Operate with ownership: stay close to the code, monitor system health, and respond to production issues
Prototype new ideas and solutions, review and improve design and code across the teams
Use AI development tools daily as part of your coding workflow — code generation, test coverage, legacy code comprehension, documentation
Experiment with AI-assisted approaches to billing problems (e.g., using LLMs to understand legacy code, accelerating test writing)
Share learnings with your team about what works and what doesn't; help teammates adopt tools that genuinely improve their delivery
Mentor junior or mid-level engineers on the team; grow their billing domain expertise and engineering judgment
Run code reviews as learning opportunities — provide constructive feedback, explain the "why" behind standards, and help engineers understand trade-offs
Pair program on complex problems; transfer knowledge directly through hands-on work
Lead occasional design discussions or post-incident reviews where the team learns together
Build internal documentation (wikis, playbooks, runbooks) to reduce reliance on vendor expertise and make billing knowledge accessible to the team
Own integration quality between upstream charging and mediation systems that feed the billing pipeline
Debug cross-system issues; ensure data flows accurately from charging through to billing
Provide input on system design decisions that affect downstream billing workflows