Appearance
🏆 Tiêu chuẩn — Professional DA Standards
Các tiêu chuẩn giúp bạn trình bày bản thân chuyên nghiệp, nhất quán, và đáng tin cậy — từ CV, LinkedIn, portfolio đến phỏng vấn. Professional standards = signal cho recruiter rằng bạn serious.
Tổng quan tiêu chuẩn buổi 20
Buổi 20 — buổi cuối — chuyển từ "học DA" sang "trở thành DA". Kỹ năng technical đã có từ 19 buổi trước. Giờ cần professional standards để package skills đó thành hồ sơ compelling:
- Resume Standards — Chuẩn CV cho DA position: format, content, action verbs, quantified impact
- Interview Standards — Chuẩn phỏng vấn DA: technical, behavioral, case study, presentation
- Portfolio Standards — Chuẩn portfolio: GitHub, README, notebook quality, dashboard, documentation
📋 Danh sách tiêu chuẩn liên quan
| # | Tiêu chuẩn | Tổ chức / Nguồn | Áp dụng cho Buổi 20 |
|---|---|---|---|
| 1 | Resume Best Practices | Harvard Business Review, Indeed Career Guide | Chuẩn content, format, ATS-friendly |
| 2 | STAR Interview Framework | Development Dimensions International (DDI) | Chuẩn trả lời behavioral interview |
| 3 | GitHub Portfolio Standards | GitHub Documentation, Open Source Guide | Chuẩn repo structure, README, documentation |
1️⃣ Resume Standards — Chuẩn CV cho Data Analyst
Giới thiệu
Resume Standards cho DA position khác với CV truyền thống. Recruiter mất trung bình 6-7.4 giây đọc CV (Ladders Eye-Tracking Study, 2018). CV của bạn cần pass 2 layers: ATS (Applicant Tracking System) — phần mềm lọc CV tự động, và Human reviewer — recruiter/hiring manager.
Nguyên tắc cốt lõi
| Nguyên tắc | Mô tả | Ví dụ |
|---|---|---|
| One Page | DA entry/mid-level: tối đa 1 trang | Cắt experience không relevant |
| Quantified Impact | Mỗi bullet point có con số | "Reduced churn 15%" NOT "Helped reduce churn" |
| ATS-Friendly | Dùng standard headings, no tables/columns phức tạp | "Experience", "Education", "Skills" — NOT creative headers |
| Relevant First | Projects & Skills trước Experience (nếu career changer) | Project section ngay sau Summary |
| Action Verbs | Bắt đầu mỗi bullet bằng strong verb | Analyzed, Built, Designed, Reduced, Improved |
Checklist chi tiết
RESUME QUALITY CHECKLIST:
───────────────────────────────────
FORMAT:
✅ 1 trang (letter hoặc A4)
✅ Font: professional (Calibri, Arial, Garamond, 10-12pt)
✅ Margins: 0.5-1 inch
✅ Consistent spacing between sections
✅ PDF format (không gửi .docx — formatting bể)
✅ File name: "TenBan_DataAnalyst_Resume.pdf"
HEADER:
✅ Full name (bold, larger font)
✅ Email (professional: firstname.lastname@gmail.com)
✅ Phone number
✅ LinkedIn URL (customized: linkedin.com/in/firstname-lastname)
✅ GitHub URL
✅ Location (City — không cần full address)
✅ Portfolio link (nếu có website)
SUMMARY (2-3 câu):
✅ Current identity: "Data Analyst with..."
✅ Key skills/tools mentioned
✅ Industry interest or specialization
✅ What you're seeking
❌ KHÔNG: "Hard-working, passionate, team player" (generic)
❌ KHÔNG: "Looking for opportunities" (weak)
SKILLS:
✅ Organized by category: Analysis / Visualization / Database / Tools
✅ Chỉ list skills bạn THỰC SỰ dùng được
✅ Match keywords từ job description
✅ Include: Python, SQL, Excel, Tableau/Power BI, Git
❌ KHÔNG: list 30 skills — max 12-15 relevant
PROJECTS (cho career changers — ĐẶT TRƯỚC Experience):
✅ Project name + tools used
✅ 2-3 bullet points: Action → Result (with numbers)
✅ Link: GitHub repo + dashboard (nếu có)
✅ Most relevant project first
EXPERIENCE:
✅ Reverse chronological
✅ Company name, title, dates
✅ 2-4 bullet points per role
✅ Every bullet: [Action verb] + [What] + [Impact with number]
❌ KHÔNG: "Responsible for..." / "Duties included..."
EDUCATION:
✅ Degree, university, year
✅ Relevant coursework (optional)
✅ GPA only if > 3.5/4.0
CERTIFICATIONS:
✅ Google Data Analytics, IBM Data Analyst, etc.
✅ Include date completed
✅ Only relevant certificationsAction Verbs cho DA Resume
| Mục đích | Verbs mạnh | Verbs yếu (tránh) |
|---|---|---|
| Phân tích | Analyzed, Investigated, Evaluated, Assessed, Diagnosed | Looked at, Checked |
| Xây dựng | Built, Developed, Created, Designed, Engineered | Made, Did |
| Cải thiện | Improved, Optimized, Enhanced, Streamlined, Accelerated | Helped, Assisted |
| Giảm thiểu | Reduced, Decreased, Minimized, Eliminated, Cut | Tried to reduce |
| Communicate | Presented, Recommended, Reported, Briefed, Communicated | Talked about, Showed |
| Data | Cleaned, Transformed, Integrated, Validated, Automated | Worked with data |
Ví dụ Good vs Bad Bullet Points
| ❌ Bad | ✅ Good |
|---|---|
| "Responsible for data analysis" | "Analyzed 50K customer transactions to identify 3 high-churn segments, reducing churn by 12%" |
| "Created dashboards" | "Built Tableau dashboard tracking 15 KPIs, adopted by 4 departments, replacing 20-page monthly report" |
| "Used Python for work" | "Automated weekly reporting pipeline using Python + Pandas, saving 8 hours/week" |
| "Helped with SQL queries" | "Optimized 12 SQL queries reducing average runtime from 45min to 3min" |
| "Good at Excel" | "Developed Excel financial model with 20+ formulas tracking $2M marketing budget across 6 channels" |
2️⃣ Interview Standards — Chuẩn phỏng vấn DA
Giới thiệu
STAR Framework (Situation, Task, Action, Result) — phát triển bởi Development Dimensions International (DDI) — là chuẩn trả lời behavioral interview được sử dụng rộng rãi nhất. Theo LinkedIn (2024), 92% employers sử dụng behavioral questions. STAR giúp structure câu trả lời: cụ thể, logic, và có impact.
STAR Framework chi tiết
┌─────────────────────────────────────────────────────────┐
│ S — SITUATION: Bối cảnh gì? │
│ "Tại [company], team đang gặp vấn đề [problem]..." │
├─────────────────────────────────────────────────────────┤
│ T — TASK: Nhiệm vụ của bạn là gì? │
│ "Em được giao [responsibility/goal]..." │
├─────────────────────────────────────────────────────────┤
│ A — ACTION: Bạn làm gì cụ thể? │
│ "Em đã: 1) [step 1], 2) [step 2], 3) [step 3]..." │
├─────────────────────────────────────────────────────────┤
│ R — RESULT: Kết quả ra sao? (PHẢI có số!) │
│ "Kết quả: [metric] cải thiện [X%], tiết kiệm [Y]" │
└─────────────────────────────────────────────────────────┘Interview Standards cho 3 loại câu hỏi
Technical Interview
| Tiêu chuẩn | Mô tả | Cách đạt |
|---|---|---|
| SQL proficiency | Viết query đúng + tối ưu | Practice: StrataScratch, LeetCode, HackerRank (3 bài/ngày × 2 tuần) |
| Python basics | Pandas operations, basic analysis | Review project notebooks, practice trên Kaggle |
| Statistics knowledge | p-value, confidence interval, A/B testing | Read: StatQuest (YouTube), ôn lại Buổi 15-16 |
| Business sense | Translate technical → business impact | Practice: "So what?" cho mỗi finding |
Behavioral Interview
| Tiêu chuẩn | Mô tả | Ví dụ câu trả lời STAR |
|---|---|---|
| Prepared stories | Chuẩn bị 5-7 stories cover các themes | Failure, Teamwork, Initiative, Conflict, Learning |
| Specific details | Có data points, timeline, names | "Tháng 3, team 4 người, dataset 50K rows" |
| Honest about weaknesses | Acknowledge + show improvement | "Em chưa giỏi presentation → tham gia Toastmasters → improve" |
| Growth mindset | Show learning attitude | "Sai → fix → learned → next time better" |
Case Study Presentation
| Tiêu chuẩn | Mô tả | Tip |
|---|---|---|
| Structured approach | Framework: Problem → Hypothesis → Analysis → Findings → Recommendations | Dùng slide template Buổi 20 |
| Time management | Finish within allocated time | Practice with timer. 15 min presentation = rehearse ≥ 5 lần |
| Q&A handling | Answer directly, acknowledge unknowns | "Good question. Based on the data, [answer]. However, I'd need [X] to confirm." |
| Visual clarity | Charts readable, key takeaways highlighted | 1 chart per slide, annotate key points |
Interview Do's and Don'ts
INTERVIEW STANDARDS:
───────────────────
DO's:
✅ Research company trước: product, users, recent news
✅ Prepare 3 questions to ask interviewer
✅ Bring laptop with portfolio ready (nếu onsite)
✅ Practice SQL on paper/whiteboard (không IDE)
✅ Use STAR for every behavioral answer
✅ Quantify EVERYTHING: "X% improvement", "Y hours saved"
✅ Ask for clarification if question unclear
DON'Ts:
❌ Nói xấu công ty cũ
❌ Trả lời "Em không biết" mà không follow up
→ Thay bằng: "Em chưa gặp case này, nhưng em sẽ approach bằng..."
❌ Oversell: nói biết tool mà chưa dùng production
❌ Ramble: answer > 2 min cho câu hỏi behavioral
❌ Skip "so what?": nêu finding mà không nêu impact
❌ Forget to ask questions at the end3️⃣ Portfolio Standards — Chuẩn GitHub & Documentation
Giới thiệu
Portfolio Standards — tổng hợp từ GitHub Documentation, Open Source Guide, và best practices từ hiring managers tại Google, Meta, Shopee. Portfolio là evidence cho skills bạn claim trên CV. 73% hiring managers (Stack Overflow Survey 2024) đánh giá ứng viên qua portfolio/GitHub trước khi interview.
Repository Standards
| Tiêu chí | Standard | Ví dụ |
|---|---|---|
| Repo name | Lowercase, hyphens, descriptive | marketing-roi-analysis NOT Project1 |
| README | Complete: problem, method, findings, how-to-run | Template từ Phần 2 index.md |
| Structure | Organized folders: data/, notebooks/, src/ | Tree diagram trong README |
| Notebook quality | Clean, documented, Restart→Run All passes | No debug cells, no errors |
| Dependencies | requirements.txt hoặc environment.yml | Pin versions: pandas==2.1.0 |
| Data handling | No raw data > 100MB in repo. Use .gitignore | Link to data source trong README |
| Version control | Meaningful commit messages | "Add EDA notebook" NOT "update" |
| License | MIT or Apache 2.0 for portfolio projects | LICENSE file in root |
README Standards
README QUALITY STANDARDS:
───────────────────────────
MUST HAVE:
✅ Project title + one-line description
✅ Problem statement (business context)
✅ Data description (source, size, features)
✅ Methodology (approach, tools, steps)
✅ Key findings (3-5, with visuals/screenshots)
✅ Recommendations (actionable, with expected impact)
✅ Tools & technologies used
✅ How to run/reproduce
✅ Author info + contact
NICE TO HAVE:
⭐ Table of contents (cho README dài)
⭐ Badges: Python version, license, status
⭐ Screenshots of dashboard/key visualizations
⭐ Video demo or recording link
⭐ Future improvements section
⭐ Acknowledgments
AVOID:
❌ README chỉ có 2 dòng: "My project. Run main.py"
❌ No context about WHY this project matters
❌ Broken image links
❌ Outdated instructions that don't workNotebook Documentation Standards
| Section | Standard | Ví dụ |
|---|---|---|
| Title cell | H1 with project name + description | # Marketing ROI Analysis |
| Import cell | All imports at top, grouped logically | Standard lib → Third party → Local |
| Data loading | Clear source, shape, preview | print(f"Dataset: {df.shape}") |
| Section headers | H2 for major sections, H3 for sub-sections | ## 1. Data Cleaning, ### 1.1 Missing Values |
| Markdown context | Before each analysis section: WHY → WHAT → SO WHAT | "We check for outliers because..." |
| Code comments | Complex logic explained inline | # Remove outliers beyond 3 std deviations |
| Visualization | Title, axis labels, legend, annotation | plt.title("Churn Rate by Segment") |
| Summary cell | Final cell: key takeaways, next steps | Bullet list of 3-5 findings |
GitHub Profile Standards
GITHUB PROFILE QUALITY:
───────────────────────
PROFILE:
✅ Professional photo (headshot)
✅ Bio: "[Role] | [Key Skills] | [Interest]"
✅ Location set
✅ LinkedIn link in bio
✅ Profile README with featured projects
ACTIVITY:
✅ Contribution graph: ideally some green (shows activity)
✅ Pinned repositories: top 4-6 projects
✅ At least 3 public repos with complete READMEs
✅ Recent activity (within last 3 months)
COMMIT STANDARDS:
✅ Meaningful messages: "Add customer segmentation analysis"
✅ Regular commits (not 1 giant commit with everything)
✅ Branch naming: feature/add-eda, fix/missing-values
❌ AVOID: "update", "fix", "asdf", "test123"📋 Tổng hợp — Professional DA Standards Matrix
| Category | Standard | Priority | Check |
|---|---|---|---|
| Resume | 1 page, quantified impact, ATS-friendly | 🔴 Critical | ☐ |
| Resume | Action verbs + numbers in every bullet | 🔴 Critical | ☐ |
| Resume | Projects section with GitHub/dashboard links | 🔴 Critical | ☐ |
| Professional headline with tools + niche | 🟡 Important | ☐ | |
| Featured section: portfolio, posts | 🟡 Important | ☐ | |
| 2-3 recommendations from peers/mentors | 🟢 Nice-to-have | ☐ | |
| Interview | STAR framework cho behavioral answers | 🔴 Critical | ☐ |
| Interview | SQL practice: 50+ problems solved | 🔴 Critical | ☐ |
| Interview | 5-7 prepared stories covering key themes | 🟡 Important | ☐ |
| Portfolio | 3+ public projects with complete READMEs | 🔴 Critical | ☐ |
| Portfolio | Clean notebooks: Restart → Run All | 🔴 Critical | ☐ |
| Portfolio | Live dashboard link | 🟡 Important | ☐ |
| Portfolio | GitHub profile README | 🟡 Important | ☐ |
| Portfolio | Meaningful commit messages | 🟢 Nice-to-have | ☐ |
Remember: Standards = minimum bar. Exceed them = stand out. Mỗi tiêu chuẩn ở trên là "table stakes" — đủ để không bị loại. Để được chọn, bạn cần projects tốt + communication skills + domain knowledge. Standards giúp bạn không mất điểm vì lỗi cơ bản.