Key Accountabilities (1)
Why This Role: The bank faces rapid technology change (AI/ML maturity, GenAI explosion, cloud-native adoption, API-first architecture). Current EA function has no dedicated capacity to scout, evaluate, and guide emerging technology adoption. Without this role, the bank falls into reactive mode — chasing technologies after competitors do, or avoiding them due to not sure how to govern. This role is proactive: scout → evaluate → publish guidance → measure adoption.
Responsibilities:Quarterly Technology Radar:
- Publish ring placement (Adopt/Trial/Assess/Hold) for 30–40 technologies relevant to the bank's domains. Radar serves as the authoritative source for technology decisions — no new technology can be introduced to ARB without Radar guidance.
- PoC Evaluation & Gatekeeping: When Domain EAs or SAs want to run a PoC, Emerging Tech Lead scopes it, defines success metrics, runs evaluation, measures results, and presents findings to ARB. Ensures PoCs are structured, not random experiments.
- Trend Analysis: Monitor trends in AI/ML, GenAI (LLMs, RAG, fine-tuning), cloud-native (Kubernetes, serverless), API architecture, data architecture (lakehouse vs. warehouse), and low-code/no-code platforms. Present quarterly trend analysis to ARB and Director.
- Adoption Tracking: Track which technologies the bank has adopted, in which domains, and measure adoption velocity. Feed this back to CIO as strategic input on technology leadership.
- ARB Participation: Attend every ARB meeting to present Technology Radar updates, discuss PoC evaluations, and provide emerging tech perspective on high-complexity designs.
- Collaboration with Domain EAs: Work with Domain EAs to apply emerging technology guidance to domain roadmaps. For example, if Lakehouse architecture emerges as best practice for data platforms, help Domain 5 Lead integrate lakehouse strategy into the 3-year roadmap.
Success Metrics (6-month review):Technology Radar published on schedule (quarterly), 30+ technologies coveredPoC conversion rate (PoCs evaluated → adopted by 12-month): 70%+Emerging tech adoption velocity (time from Adopt ring to first production usage): <6 months for high-impact technologiesARB and CIO perceive role as strategic input (qualitative feedback)
Success Profile - Qualification and Experiences
Qualifications
- Graduated in Information Technology or Banking
Work Experience
- Understand the bank's IT development strategy and roadmap in the next 5 years
- Able to propose solution architecture for some main business areas of the bank such as Payment, BPM, DW, Risks, Lending...
- Ability to coordinate with other units to carry out the work from ideation, to design and operation.
- Having expertise, deep understanding of analysis, design, selection of technical solutions
- At least 8 years of experience in practical implementation of many key solutions in end-to-end banking from business to application and deployment layer such as card, core, internet banking, data warehouse...
- Strong verbal and written communication, collaboration, and leadership skills with Technical teams and Business teams
- Experience guiding/teaching others in architecture principles, such as roadmaps, technical standards, non-functional requirements, and solution diagramming/documentation
- Demonstrated success working with standard software development lifecycle models, deliverables/artifacts and tools, SOA concepts and design patterns
- Experience designing scalable/reliable/flexible/secure solutions across heterogeneous hardware platforms , operating systems, middlewares, and infrastructure technologies
- Technical experience with architecture, technology stacks, or overall architectural governance
- Experience with cloud computing and/or other virtualization technologies
- Experience establishing and documenting standards, guidelines, and best practices
Language level
English, according to TCB's regulations in each period
