Source Evidence: Lim Tern Poh - LinkedIn public profile
- Source ID:
linkedin_public_profile - Publisher: LinkedIn
- Original URL: https://www.linkedin.com/in/ternpohlim/
- Archive URL: https://web.archive.org/web/*/https://www.linkedin.com/in/ternpohlim/
- Accessed: 2026-09-05
- Content type: first-person professional profile
Supported Claims
- Tern Poh Lim public profile name
- TR 99 AI security
- ASME Digitalization & AI Action Group
- INSEAD Product Game
- NUS VCIC
- 500 Global mentoring
- AI product and ecosystem roles
- Deloitte: enterprise AI deployment and data modernisation across APAC; leadership of a 20-person regional team on an Oracle-to-Google Cloud reporting migration
- Deloitte: support for enterprise Claude rollout and API implementation; design of a Google Cloud operating model; advice on agent product design and harness engineering; leadership of a regional data-governance framework update
- Deloitte: onsite work with client teams to address adoption barriers, support Claude rollout and API integration, and build agentic workflows and AI-enabled products
- Yoozoo: leadership of a cross-functional team of 10 on Slick.AI, with responsibility for the roadmap, user experience, no-code interfaces and go-to-market work
- Arthur D. Little: MBA internship, May–August 2023, supporting Southeast Asian bio- and e-methanol logistics strategy and analysis
- SegmentFault / ONES.com: PKU Guanghua MBA Integrated Practicum Project, March–May 2023, leading a multicultural team on international go-to-market strategy
- NUS Master of Computing: FaceSpeaks, described in the Education media caption as an AWS-based computer-vision project for the Cloud Computing module
- NUS Master of Computing: a multi-agent trading-system architecture, described in the Education media caption as a deployment-module course project
Evidence Summary
The signed-in profile’s Experience section was reviewed on 5 September 2026 at the owner’s request. This note preserves selected professional claims from the owner’s own account, not a full LinkedIn page. The owner subsequently asked to use the additional information on the personal website. Team sizes and project responsibilities are first-person evidence; they are not employer-verified outcomes.
On 20 September 2026, the retained English Experience backup from 19 September was reviewed at the owner’s request to put greater emphasis on forward deployment and agentic AI. It describes onsite work with client teams on Claude adoption, API implementation and agentic workflows, alongside advice on agent product design and harness engineering. This was an offline review of the owner’s account, not new live access or independent verification. The public summary does not imply bootcamp completion or change the formal job title.
The website keeps the established official role names. It omits client names and identifying sector/location combinations, proposal-win claims, revenue or adoption implications, and unsupported production or clinical outcomes. The ONES.com entry is described as an MBA practicum because its description establishes that academic context; the profile’s internship label alone is not used to assert a separate employment appointment. The PKU institutional article also supports the practicum project.
Do not use this source to resolve conflicting AI Singapore titles or dates without checking the corresponding institutional evidence. Do not use private contact details, account analytics, messages or people-search data.
The Education section and its project captions were also reviewed. The website labels the computing work as course projects; the review did not validate their implementation, production use or performance. Do not repeat the FaceSpeaks emotion-recognition or confidence claims, imply investment returns, or describe the earlier multi-agent design as an LLM-agent deployment. New grade or graduation-honour claims were not imported. NUS workshop instruction and moderation are supported separately by nus_mba_ai_business_leaders_workshop.
Use Rule
Use this note as a local claim map. Prefer the original URL first, then the archive URL, then this note if the public page is unavailable.