Engineer
Posted 25 Sep 2026
Advertised as “Principal Engineer ”
BranchFactor Summary
The original posting with the fluff stripped out
- Expected experience
- 12+ yrs
- Management level
- Individual contributor
No salary listed for this role.
Field of studyComputer Science, Engineering (or related)
Study levelBachelor's
About us
Appnovation is the AI Product Company. Headquartered in Vancouver, Canada, with teams around the world, Appnovation builds AI products, delivers enterprise AI and digital solutions, and co-invests with clients to bring new AI products to market.
Open source has been the foundation of Appnovation's work since 2007, and it remains the foundation underneath every AI product the company builds today. Appnovation teams work with organizations in highly regulated industries, including global leaders such as Pfizer, Google and AstraZeneca, to help them adopt AI they can govern and own.
ABOUT THE ROLE
We are seeking a Principal Engineer to own the end-to-end technical coherence of an enterprise marketing technology ecosystem for our life sciences clients. In most large organizations, content is created and approved in one system, delivered as an experience in another, and measured in a third, each run by a different team and vendor. When the seams between them are well designed, a business result can be traced back to the asset and workflow that drove it. When they are not, creators can't see how their work performs, publishers can't prove impact, and analysts spend more time reconciling data than finding insight.
This is a senior technical leadership role with no direct reports. You will set a single, clear technical direction across multiple platform teams, making sure their architectures, data contracts and roadmaps fit together as one system. You will lead through clarity and credibility rather than reporting lines, and you will help shape new AI-enabled patient and healthcare professional (HCP) experiences that can be built safely, approved and proven in production, not just shown in a prototype.
ROLE RESPONSIBILITIES
- Technical Direction: Define and own one clear technical approach across content creation, governance and approval; publishing, experience delivery and design systems; and measurement, tagging and reporting, with special focus on the content-to-experience and experience-to-insight handoffs.
- Cross-Team Standards: Set shared standards for API contracts, metadata and taxonomy, data governance and security, so a decision made by one team doesn't create rework or data gaps for another.
- Architecture Reviews and Decisions: Lead architecture reviews and RFCs across platform teams, act as the escalation point for the hardest cross-team problems (migrations, vendor consolidation, build vs. buy), and keep a written record of what was decided and why.
- End-to-End Data Traceability: Own the technical strategy for tracing content, experience and performance data from asset, through publication, to the results it produced.