It can be, if the knowledge concerns the company's own product or processes and is shown to be beyond what the industry generally has. Long tenure and seniority are not the test; the content of the knowledge and its value to the U.S. subsidiary are.
Which document decides it: the knowledge narrative
Hypothetical example: the South Frontenac developer built the module that converts raw rumination-sensor data into health alerts and wrote the integration for two Canadian milking-system brands. That is knowledge of the company's product and its application abroad, which is the core of the definition. Her fluency in the programming language and cloud platform the company uses is not, because a locally hired developer could bring the same.
The petition should therefore describe the alert engine and integration layer in enough detail that an examiner understands why a new hire could not simply be trained in a month, and should link that description to records showing she authored or maintained those components during her Canadian employment. Avoid the two common errors: overstating uniqueness until the claim becomes implausible, and hiding behind confidentiality so that nothing concrete is said. Counsel can help decide how much technical detail to include, but the developer herself must supply the substance.