Mô tả công việc

Các trách nhiệm chính 1
Translate Business Strategy into Solutions Architecture

- Understands business drivers and business capabilities (future and current state) and determines corresponding enterprise system designs and change requirements to drive the organization's targeted business outcomes.

- Understands emerging technology trends and disruptions and the practical application of existing, new, and emerging technologies to enable new and evolving business and operating models.

- Translates business and technical requirements into an architectural blueprint to achieve business objectives and documents all solution architecture design and analysis work.

- Analyzes the technology industry, competitors and market trends, and determines their potential impact on the enterprise.

- Provides deliverables like standard definitions, reference models and architecture designs to help the architecture review board (ARB) assess the impact of new and ongoing technology investment on the business and IT estate.

- Acts as a consultant on a broad range of technologies, platforms and vendor offerings to drive targeted business outcomes.

Các trách nhiệm chính 2
Lead Solutions Design and Analysis

- Leads evaluation, design and analysis for the implementation of a solutions architecture across a group of specific business applications or technologies based on enterprise business strategy, business capabilities, value-streams, business requirements and enterprise standards.

- Creates architectural designs to guide and contextualize solution development across products, services, projects and systems (including applications, technologies, processes and information).

- Creates reference architectures focused on detailed design principles, decision points, detailed APIs, major systems and dependencies between business and IT.

- Manages and develops the architecture for a broader scope of projects or products, working closely with application architects that manage and design architecture for a single project or product or initiative.

- Analyzes the business-IT environment (run, grow and transform the business) to detect critical deficiencies, legacy and technical debt, and recommends solutions for improvement (systems of record, differentiation and innovation).

Các trách nhiệm chính 3
Orchestrate Solutions Delivery

- Designs and directs the governance activities associated with ensuring solutions architecture assurance and compliance.

- Defines the principles, guidelines, standards and solution patterns to ensure solution decisions are aligned with the enterprise's future-state architecture vision.

- Facilitates the evaluation and selection of software product standards and services, as well as the design of standard and custom software configurations.

- Supports product managers in EOL (end of life) product decisions to maintain, refresh or retire products, services or systems (including applications, technologies, processes and information).

- Develops a roadmap for the evolution of the enterprise application portfolio from future to current state (as defined by the solutions architecture).

- Monitors the current-state solution portfolio to identify deficiencies through aging of the technologies used by the application, or misalignment with business requirements.

- Identifies the organizational impact (for example, on skills, processes, structures or culture) and financial impact of the solutions architecture.

Các trách nhiệm chính 4
Facilitate and Collaborate to Deliver Business Outcomes

- Works closely with the program management office (PMO) or project management office to ensure the execution of plans corresponds with what is being promised throughout the project or product lifecycle.

- Works closely with the product owners and product managers to ensure a robust architectural runway that can support future business requirements throughout the product lifecycle.

- Provides consulting support to application architects within agile teams to ensure the project or product is aligned with the overall enterprise architecture.

- Consults with application and infrastructure development projects and products to fit systems or infrastructure to architecture and identify when it is necessary to modify projects to accommodate the solutions architecture.

- Supports a community of practice (CoP), guiding and helping agile teams, product owners, and application architects to align with the overall enterprise architecture governance and assurance.

Yêu cầu ứng viên

Trình độ đào tạo
Đại học in Công nghệ thông tin

Các năng lực khác

- Knowledge of various backend development languages like Java, Go and Python

- Knowledge of various database technologies like MySQL, MongoDB and Oracle

- Knowledge of various frontend web development languages like JavaScript, HTML and CSS.

- Hands-on experience with at least one of following domains: cloud native application development, DevOps practices, highly available and critical system development

- Knowledge of various aspects of an enterprise technology architecture like business, information, data, network and security

- Exposure to multiple, diverse technologies, platforms and processing environments

- Solid understanding of product management, agile principles and development methodologies and capability of supporting agile teams by providing advice and guidance on opportunities, impact and risks, taking account of technical and architectural debt

- Knowledge of information principles and processes

- Knowledge of financial models and budgeting

- Understanding and knowledge of system development life cycle methodologies (such as waterfall, spiral, agile software development, rapid prototyping, incremental, synchronize and stabilize, and DevOps)

- Understanding and knowledge of IT service management (ITSM) and Information Technology Infrastructure Library (ITIL)

- Knowledge and understanding of different modeling languages (such as UML and ArchiMate)

- Understanding and knowledge of IT standards and controls

- Excellent understanding of application development methodologies and infrastructure and network architecture

Các yêu cầu khác

- Excellent interpersonal skills in areas such as teamwork, facilitation and negotiation

- Strong leadership skills

- Excellent analytical and technical skills

- Excellent written and verbal communication skills

- Excellent planning and organizational skills

- Minimum of five years of experience in at least two IT solution development disciplines, including technical or infrastructure architecture, network management, application development, middleware, database management or cloud development

Phân tích kỹ năng cần có

## Phân tích Kỹ năng yêu cầu

### 🔧 Hard Skills (Kỹ năng kỹ thuật)

| Nhóm kỹ năng | Yêu cầu cụ thể | Mức độ quan trọng |
|---------------|----------------|-------------------|
| Backend Development | Java, Go, Python | ⭐⭐⭐⭐⭐ |
| Database | MySQL, MongoDB, Oracle | ⭐⭐⭐⭐⭐ |
| Frontend | JavaScript, HTML, CSS | ⭐⭐⭐ |
| Cloud & DevOps | Cloud native, DevOps practices, highly available systems | ⭐⭐⭐⭐⭐ |
| Enterprise Architecture | Business, information, data, network, security architecture | ⭐⭐⭐⭐⭐ |
| Modeling | UML, ArchiMate | ⭐⭐⭐⭐ |
| Methodology | Agile, Waterfall, Spiral, DevOps, ITIL/ITSM | ⭐⭐⭐⭐ |
| System Design | Microservices, API design, distributed systems | ⭐⭐⭐⭐⭐ |

### 🧠 Soft Skills (Kỹ năng mềm)

- Giao tiếp xuất sắc (written & verbal) - cần trình bày kiến trúc cho cả kỹ thuật và business
- Leadership - dẫn dắt team, định hướng architecture
- Analytical skills - phân tích hệ thống phức tạp, đánh giá rủi ro
- Planning & Organization - quản lý portfolio, roadmap
- Interpersonal - teamwork, facilitation, negotiation

### 📜 Chứng chỉ gợi ý

| Chứng chỉ | Mô tả | Ưu tiên |
|-----------|-------|--------|
| TOGAF 9 | Enterprise Architecture framework phổ biến nhất | ⭐⭐⭐⭐⭐ |
| AWS/Azure/GCP Solutions Architect | Cloud architecture certification | ⭐⭐⭐⭐⭐ |
| CISM | Certified Information Security Manager | ⭐⭐⭐⭐ |
| ITIL Foundation | IT Service Management | ⭐⭐⭐⭐ |
| Kubernetes/CKA | Container orchestration | ⭐⭐⭐⭐ |
| PMP/ACP | Project/Agile certifications | ⭐⭐⭐⭐ |

### 📊 Bảng so sánh: Solution Architect vs Enterprise Architect

| Khía cạnh | Solution Architect | Enterprise Architect |
|-----------|-------------------|---------------------|
| Phạm vi | Tập trung vào giải pháp cụ thể cho 1-2 dự án/sản phẩm | Toàn bộ tổ chức, tầm nhìn dài hạn |
| Chi tiết kỹ thuật | Rất chi tiết, hands-on | Trừu tượng hơn, governance-level |
| Tương tác | Dev team, PM, Product Owner | C-level, Board, Business units |
| Đầu ra chính | Technical specs, API design, reference architecture | Enterprise roadmap, standards, principles |

> Note: JD này leans về phía Solution Architect có tầm ảnh hưởng rộng, nhưng cần cả hai góc nhìn.

### ⚠️ Điểm cần lưu ý

- 5+ năm kinh nghiệm ở ít nhất 2 domain trong: infrastructure, network, app development, middleware, DB, cloud
- Cần hiểu financial models & budgeting - vì ngân hàng
- Hands-on experience với highly available & critical systems - yêu cầu quan trọng cho fintech/banking

Chuẩn bị phỏng vấn

## Hướng dẫn Phỏng vấn VPBank - Senior IT Architect (JG 10)

### 📋 Quy trình phỏng vấn dự kiến

```
Vòng 1: HR Screening (30-45 phút)
↓
Vòng 2: Technical Interview - Architecture Team (60-90 phút)
↓
Vòng 3: Panel Interview - IT Director + Business Stakeholders (60 phút)
↓
Vòng 4: Final Interview - C-level/CHỦ TỊCH/HĐQT (30-45 phút)
```

### 🎯 Câu hỏi theo từng vòng

#### Vòng 1: HR Screening
1. Giới thiệu bản thân và quỹ đạo nghề nghiệp
2. Tại sao bạn quan tâm đến vị trí Solution Architect tại VPBank?
3. Mức lương mong muốn và kỳ vọng khác?
4. Bạn có đang có offer nào khác không?
5. Kinh nghiệm quản lý team hoặc stakeholder management

#### Vòng 2: Technical Deep-dive
1. "Describe your most complex architecture decision you've made. What was the problem, options considered, and outcome?"
2. "How would you design a highly available system for banking transactions? Walk me through your approach."
3. "Explain the difference between microservices and monolithic architecture. When would you recommend each for a bank?"
4. "How do you balance technical debt vs. new feature development?"
5. "Describe your experience with cloud migration. What challenges did you face?"
6. "How do you communicate technical concepts to non-technical stakeholders? Give an example."
7. Design question: "Design an architecture for a real-time payment system processing 10,000 TPS."
8. Trade-off question: "If you had to choose between consistency and availability in a banking system, what would you choose and why?" (there's no "both" answer here - CAP theorem)

#### Vòng 3: Panel - Business & Leadership
1. "How do you align technology strategy with business objectives? Give examples."
2. "Describe a time when you had to convince leadership to adopt a new technology. What was your approach?"
3. "How do you handle conflicts between development teams on architectural decisions?"
4. "What is your approach to building architectural runway for future business requirements?"
5. "How would you handle a situation where a product manager wants to ship a feature that conflicts with enterprise architecture standards?"
6. Case study: "VPBank is planning to launch a new digital banking product in 6 months. How would you contribute to the architecture strategy?"

#### Vòng 4: Final - Executive
1. Your vision for enterprise architecture at VPBank
2. How do you see the role of AI/ML evolving in banking architecture?
3. What would be your first 90 days in this role?
4. Questions for the leadership about strategic direction

### 💡 Tips chuẩn bị

Technical Preparation:
- Ôn lại TOGAF framework - VPBank enterprise architecture practice
- Nắm chắc CAP theorem, microservices patterns (Saga, CQRS, Event Sourcing)
- Hiểu sâu về cloud architecture (AWS/Azure), Kubernetes
- Đọc về VPBank's tech stack và digital transformation strategy

Behavioral Preparation:
- Chuẩn bị STAR stories cho: leadership, conflict resolution, stakeholder management
- Nghiên cứu VPBank's recent tech announcements, partnerships

VPBank-specific Research:
- VPBank's digital banking initiatives
- Recent technology partnerships/investments
- VPBank's cloud adoption journey
- Any public case studies about their architecture

### 👔 Dress Code

- Vòng 1-2: Business casual (áo sơ mi, quần tây)
- Vòng 3-4: Business formal (completes the professional look)
- Quan trọng: thể hiện sự chuyên nghiệp và hiểu biết ngành tài chính

Lộ trình ôn thi

## Lộ trình Ôn tập & Chuẩn bị (2 tuần)

### 📚 Kiến thức Nền tảng cần ôn

#### Week 1: Enterprise Architecture & Solution Design

Day 1-2: TOGAF Fundamentals
- TOGAF 9 Foundation concepts
- Architecture Development Method (ADM)
- Enterprise Continuum
- Reference: [TOGAF 9 Handbook](https://www.opengroup.org/togaf)

Day 3-4: Solution Architecture Patterns
- Microservices architecture patterns
- Event-driven architecture
- API gateway patterns
- Saga pattern cho distributed transactions
- Circuit breaker, retry patterns

Day 5-6: Cloud Architecture
- Cloud-native design principles
- 12-factor app methodology
- Well-Architected Framework (AWS/GCP/Azure)
- Containers & Kubernetes fundamentals

Day 7: Review & Hands-on
- Vẽ reference architecture diagrams
- Practice explaining architectures

#### Week 2: Banking Domain & Leadership

Day 8-9: Banking IT Systems
- Core banking systems architecture
- Payment systems (NAPAS, SWIFT)
- Regulatory compliance (PCI-DSS, cybersecurity laws)
- Digital banking architecture patterns

Day 10-11: DevOps & Platform Engineering
- CI/CD pipelines
- Infrastructure as Code (Terraform, Ansible)
- Observability (monitoring, logging, tracing)
- SRE principles

Day 12-13: Soft Skills & Communication
- Architecture Decision Records (ADRs)
- Presenting to executives
- Stakeholder management frameworks
- Technical writing best practices

Day 14: Mock Interview & Final Review

### 📖 Tài liệu Tham khảo

| Loại | Tài liệu | Link |
|------|----------|------|
| Book | "Fundamentals of Software Architecture" - Mark Richards | Amazon |
| Book | "Building Microservices" - Sam Newman | Amazon |
| Book | "Enterprise Integration Patterns" - Hohpe & Woolf | Amazon |
| Book | "Accelerate" - Nicole Forsgren | Amazon |
| Online | AWS Well-Architected Framework | aws.amazon.com/architecture |
| Online | Microsoft Azure Architecture Center | docs.microsoft.com/azure/architecture |
| Online | ThoughtWorks Technology Radar | thoughtworks.com/radar |
| Course | TOGAF 9 Certification Training | OpenGroup partner |
| Course | AWS Solutions Architect Professional | AWS Training |

### 🎯 Checklist trước ngày phỏng vấn

- [ ] Research VPBank's recent tech news, partnerships
- [ ] Prepare 5-7 STAR stories về architectural decisions
- [ ] Review your portfolio of past architecture work
- [ ] Practice drawing architecture diagrams on whiteboard
- [ ] Prepare thoughtful questions cho interviewer
- [ ] Confirm interview format (online/in-person), timing
- [ ] Prepare laptop/portfolio nếu cần demo
- [ ] Điều chỉnh CV để highlight architecture achievements

Tư vấn nghề nghiệp

## Lời khuyên Sự nghiệp cho Senior Solution Architect

### 🚀 Lộ trình Thăng tiến

```
Senior Solution Architect (JG 10)
↓ (3-5 năm)
Lead Architect / Principal Architect
↓ (3-5 năm)
Chief Architect / VP of Architecture
↓
CTO / Enterprise Architecture Director
```

### 📈 Mức Lương Kỳ vọng (VPBank - JN 2024)

| Cấp bậc | Mức lương (VND/tháng) | Notes |
|---------|----------------------|-------|
| Senior Solution Architect (JG 10) | 60-100 triệu | Thỏa thuận cao, có thể đến 120M+ |
| Lead Architect | 100-150 triệu | Bonus 2-4 tháng |
| Principal Architect | 150-200 triệu | C-level compensation |
| Chief Architect | 200-300+ triệu | + ESOP possible |

> Note: Lương ngành banking thường cao hơn fintech 20-30%, đặc biệt ở các ngân hàng lớn như VPBank. "Thỏa thuận" trong JD có nghĩa budget không giới hạn nếu ứng viên đủ năng lực.

### 🎯 Kỹ năng Cần Phát triển thêm

Ngắn hạn (6-12 tháng):
1. TOGAF Certification - Chuẩn ngành, validate kiến thức
2. Cloud Architecture cert (AWS SAP hoặc Azure Architect Expert)
3. Hands-on với một cloud provider cụ thể - VPBank đang dùng gì?
4. Domain knowledge: Banking/Financial Services - regulatory, compliance

Trung hạn (1-2 năm):
1. Leadership & Executive presence - trình bày với C-level
2. Strategy & Business Acumen - hiểu business outcomes
3. Mentoring & Team building - dẫn dắt junior architects
4. Architecture governance - định nghĩa standards cho tổ chức

Dài hạn (3-5 năm):
1. Enterprise Architecture thinking - tầm nhìn toàn công ty
2. Innovation leadership - AI/ML, blockchain applications
3. Board-level communication - đọc báo cáo tài chính, OKRs
4. Industry thought leadership - conference talks, publications

### 💼 Tại sao nên chọn VPBank?

Pros:
- Một trong những ngân hàng TMCP lớn nhất VN
- Đang đẩy mạnh digital transformation
- Budget công nghệ lớn, tech stack hiện đại
- Cơ hội làm việc với hệ thống mission-critical
- JG 10 là cấp cao, có ảnh hưởng lớn

Cons/Challenges:
- Ngân hàng = nhiều compliance, regulation
- Legacy systems vẫn còn, không phải greenfield
- Legacy constraints với công nghệ mới
- Quy trình approval phức tạp hơn startup

### ⚡ So sánh: VPBank vs Fintech vs BigTech

| Tiêu chí | VPBank | Fintech | BigTech (FANG) |
|----------|--------|---------|----------------|
| Lương | 8-9/10 | 7/10 | 10+/10 (USD) |
| Tech stack | Modern, legacy hybrid | Modern, greenfield | Cutting-edge |
| Impact scale | National | Regional | Global |
| Work-life balance | 7/10 | 6/10 | 5/10 |
| Learning opportunity | 8/10 | 9/10 | 10/10 |
| Job security | 9/10 | 7/10 | 8/10 |

Câu hỏi thường gặp

Mình có 6 năm kinh nghiệm làm backend developer (Java), chưa có kinh nghiệm architecture. Có nên apply vị trí này không?

Có thể apply, nhưng cần bổ sung thêm kiến thức architecture. Nên:
1. Học TOGAF cơ bản (foundation level)
2. Đọc sách 'Fundamentals of Software Architecture' của Mark Richards
3. Thực hành thiết kế hệ thống, vẽ architecture diagrams
4. Tập trung vào strength của bạn: deep Java knowledge + backend experience là nền tảng tốt
5. Trong CV và phỏng vấn, highlight các quyết định thiết kế bạn đã đưa ra dù ở vai trò senior developer

Vị trí yêu cầu 5+ năm kinh nghiệm, bạn đáp ứng được. Quan trọng là thể hiện được tư duy architecture và communication skills.

Vị trí này yêu cầu 'Thỏa thuận', mình nên hỏi mức lương như thế nào cho phù hợp?

Với JG 10 và yêu cầu cao như vậy, đây là cách approach:

1. Research market rate: Senior Solution Architect tại VPBank/major banks: 60-100 triệu VND/tháng
2. Đừng đưa số đầu tiên: Khi HR hỏi, nói 'Tôi muốn hiểu thêm về scope và đãi ngộ của VPBank trước'
3. Base + bonus structure: Hỏi rõ về base salary, performance bonus, 13th month, insurance
4. Total compensation: Yêu cầu package bao gồm cả benefits: insurance, healthcare, parking, phone allowance
5. Flexibility: Nếu thích VPBank, bạn có thể trade off: lương thấp hơn market nhưng yêu cầu remote days hoặc training budget

Lưu ý: 'Thỏa thuận' cho thấy họ sẵn sàng trả cao cho đúng người - đừng undervalue bản thân.

Mình đang làm ở công ty outsource, muốn chuyển sang ngân hàng. Cần chuẩn bị gì về mặt kiến thức ngành banking?

Đây là những knowledge areas cần nắm khi chuyển từ outsource sang banking:

Bắt buộc:
1. Regulatory landscape: Basel III/IV, Circular 41 (TTTM), cybersecurity regulations của NHNN
2. Payment systems: NAPAS 247, SWIFT, real-time payment
3. Security standards: PCI-DSS, ISO 27001, multi-factor authentication
4. Core banking: Hiểu cách CBS (Core Banking System) hoạt động

Nên biết:
5. Banking products: deposits, loans, cards, internet banking
6. Risk management framework trong ngân hàng
7. Audit & compliance requirements

Resources:
- NHNN website: đọc các circular/regulation mới
- VPBank IR: annual report, investor presentations
- VPBank news: digital banking initiatives

Mấu chốt: Thể hiện bạn hiểu banking = regulated industry, không phải tech startup.

Technical interview vòng 2 sẽ hỏi gì? Mình cần ôn những patterns nào?

Vòng technical cho Solution Architect sẽ tập trung vào 3 areas chính:

1. System Design (60% câu hỏi)
- Design a payment gateway
- Design a highly available banking system
- Design API layer cho microservices
- Scale a system từ 100 → 100,000 users

2. Architecture Patterns (25% câu hỏi)
- Microservices decomposition strategies
- Event-driven architecture
- CQRS, Event Sourcing
- Saga pattern cho distributed transactions
- API Gateway vs Backend-for-Frontend

3. Decision Making (15% câu hỏi)
- Monolith vs Microservices trade-offs
- Cloud vs On-prem decisions
- Build vs Buy cho components
- Tech stack selection rationale

Tip: Sử dụng framework STAR khi trả lời: Situation → Task → Action → Result. Đặc biệt nhấn mạnh Trade-offs và compromises bạn đã make.

Làm Solution Architect ở ngân hàng khác gì so với startup?

Khác biệt chính theo trải nghiệm của mình:

1. Compliance & Regulation
- Banking: Phải tuân thủ NHNN, PCI-DSS, SOX... nhiều constraint
- Startup: Freedom hơn, nhưng có thể có security audits từ enterprise clients

2. Legacy Systems
- Banking: Mainframe, COBOL, Oracle Forms vẫn chạy production. Nhiều integration work
- Startup: Greenfield, modern stack

3. Decision Velocity
- Banking: Change advisory board, multiple sign-offs, slower
- Startup: Ship fast, iterate

4. Scale & Reliability
- Banking: 99.99% uptime là standard, not negotiable
- Startup: 99% có thể chấp nhận được

5. Career Growth
- Banking: Ổn định, benefits tốt, brand value
- Startup: Stock options, faster growth, higher risk

Reality check: Nếu bạn thích 'clean architecture', banking có thể frustrate. Nhưng nếu muốn work on systems affecting millions of customers daily, banking là choice tốt.

Mình nên hỏi gì khi được hỏi 'Bạn có câu hỏi gì cho chúng tôi?' ở cuối phỏng vấn?

Đây là questions hiệu quả cho senior architect interview:

Strategic questions (cho panel/business):
- What are the top 3 architectural challenges VPBank is facing in the next 2 years?
- How does the architecture team interact with product and business teams?
- What is VPBank's cloud strategy and current state?
- How do you measure success for this role?

Team & Culture (cho HR/Team):
- What does a typical day/week look like for a Solution Architect here?
- How is the architecture community structured? Is there a CoP?
- What are the biggest gaps you're looking to fill?
- What training/development opportunities are available?

Process & Tools (cho technical):
- What is the current tech stack and modernization roadmap?
- How do you handle architecture reviews and governance?
- What tools does the team use for documentation and modeling?

Avoid: Questions về salary/leave/parking ở vòng technical. Save cho HR.

First 90 days trong vai trò này nên làm gì?

Đây là framework cho first 90 days hiệu quả:

Days 1-30: Listen & Learn
- 1:1 với tất cả stakeholders (IT leads, Product, Security, Operations)
- Understand current architecture landscape
- Review existing architecture documentation
- Shadow sprint ceremonies, architecture review boards
- Identify quick wins nhưng KHÔNG announce changes

Days 31-60: Analyze & Prioritize
- Map current systems, integrations, dependencies
- Identify critical pain points (technical debt, integration issues)
- Align with business strategy - what are the 2024-2025 priorities?
- Start building relationships với development teams
- Propose initial high-level roadmap

Days 61-90: Execute & Communicate
- Present architecture vision to leadership
- Define principles và standards (lightweight, not bureaucratic)
- Pick 1-2 initiatives để influence
- Start architecture community of practice
- Deliver first tangible outcome

Key success metric: Maintain trust của developers, credibility với leadership.

Chia sẻ từ cộng đồng

Ẩ

Ẩn danh 2024-11-15

Vừa phỏng vấn vòng cuối tuần rồi, HR nói JF 10 này trực tiếp báo cáo lên CIO. Mức lương thực tế deal được khoảng 85-90M, bonus 2 tháng. Tech stack của VPBank đang dùng Java Spring Boot, Kubernetes, AWS. Nếu bạn nào có GCP/Azure cert cũng được welcome lắm.

A

Architect_T*** 2024-10-28

Working at VPBank as Solution Architect đã 2 năm. Điểm tốt: được access vào hệ thống core banking thực sự, impact lớn, team tech strong. Điểm chưa tốt: legacy code vẫn nhiều, change process chậm. Nhưng overall recommend cho ai muốn build career trong banking tech.

Ẩ

Ẩn danh 2024-11-20

Cảnh báo: JD viết bằng tiếng Anh, nhưng công việc thực tế phải làm việc với nhiều stakeholder không nói tiếng Anh lắm. Nếu bạn giỏi tiếng Anh nhưng yếu soft skills tiếng Việt thì hơi khó. Còn ngược lại thì OK.

N

Newbie_bank 2024-09-15

Mình apply vào vị trí này nhưng trượt ở vòng technical. Họ hỏi rất sâu về distributed systems: consistency, availability trade-offs, và yêu cầu vẽ architecture diagram trên whiteboard. Gợi ý: ôn thật kỹ CAP theorem và design patterns.

Ẩ

Ẩn danh 2024-11-05

Có ai biết JG 10 này thuộc grade nào trong hệ thống VPBank không? Mình nghe nói còn có JG 11, 12 nữa. Muốn so sánh với các ngân hàng khác xem JD này tương đương cấp nào.

B

Banker_HCM 2024-10-10

Tech lead tại VPBank đây. Đã review resumes cho position này. Điều tụi mình search: (1) Có production experience với highly available systems không? (2) Đã từng make architectural decisions nào có business impact? (3) Leadership experience? Nhiều CV giỏi tech nhưng thiếu business acumen.

Ẩ

Ẩn danh 2024-11-18

Cảnh báo nhẹ: interview process kéo dài. Mình mất 2 tháng từ apply đến offer. Có 4 vòng như mô tả. HR responsive nhưng phải schedule chờ bên nào rảnh trước. Cái này thì tùy may rủi.

IT-165_Kiến trúc sư cao cấp_JG 10