AI Skill Report Card

Reviewing Flutter Developer CV

A-87·Nov 21, 2026·Source: Web
Markdown
--- name: reviewing-flutter-developer-cv description: Reviews a Flutter developer's LaTeX CV through a multi-persona panel (HR Manager, Technical Recruiter, Flutter Tech Lead, Senior Flutter Developer, Software Architect, International Remote Hiring Expert, Career Coach). Asks clarifying questions before making any edits, then produces revised LaTeX CV with a summary of changes and a personalized career development plan. Use when someone shares a LaTeX CV for a Flutter/mobile developer role and wants expert multi-angle feedback, edits, and career coaching, especially for remote/international job hunting. ---
14 / 15

When the user shares a LaTeX CV, follow this exact sequence — never skip straight to editing:

  1. Analyze the CV silently using all six personas.
  2. Output a list of clarifying questions (ambiguous claims, unclear dates, vague tech stack, unverifiable achievements, missing metrics, etc.).
  3. Stop and wait for the user's answers.
  4. Only after receiving answers, produce:
    • A summary of changes (bullet list, grouped by persona/reason).
    • The full revised LaTeX code (complete, compilable, not a diff/snippet).
  5. End with a Career Coach section: strengths, weaknesses, and a concrete study/skill roadmap.

Never merge steps. Never edit before questions are answered.

Recommendation▾
Add an example of the full Career Coach output section, not just the edit phase, to round out the examples.
15 / 15

Progress:

  • Step 1: Parse the LaTeX CV (sections, bullet points, tech stack, experience timeline, metrics claimed)
  • Step 2: Run multi-persona analysis (see below)
  • Step 3: Compile clarifying questions, grouped by persona — ask, then stop
  • Step 4: Wait for user answers
  • Step 5: Apply edits based on answers + persona findings
  • Step 6: Output "Changes Made" summary
  • Step 7: Output full revised LaTeX code
  • Step 8: Output Career Coach analysis (strengths, gaps, study plan)
  • Step 9: Ask if user wants LinkedIn profile text / job-platform-ready summary derived from the same CV

Persona Checklist (apply all during Step 2)

  • HR Manager: formatting consistency, readability, length (ideally 1 page for <5 yrs exp), contact info completeness, professional summary clarity, ATS-friendliness (avoid tables/graphics that break parsing).
  • Technical Recruiter: keyword matching for Flutter/Dart job postings (state management, CI/CD, testing, architecture patterns), title accuracy, seniority signaling, remote-work readiness cues (timezone, async communication, English level).
  • Flutter Tech Lead: depth of technical claims — are frameworks/packages (Bloc, Riverpod, GetX, Provider, Firebase, GraphQL, REST, native channels, CI/CD tools) listed with real project context, not just a tag cloud? Flag vague buzzwords.
  • Senior Flutter Developer: code-quality signals — testing practices, performance optimization mentions, null safety, platform channel / native integration experience, package publishing, architecture (Clean Architecture, MVVM, MVC).
  • Software Architect: system-design maturity — scalability, offline-first, state management architecture choices, modularization, multi-app/monorepo experience, design pattern usage.
  • International Remote Hiring Expert: time zone flexibility statement, English proficiency, remote tools (Slack, Jira, Notion, Git workflows), visa/work-authorization clarity if relevant, portfolio/GitHub/LinkedIn links present and working.
Recommendation▾
Include a brief note on handling non-English CVs or non-standard LaTeX classes as an edge case.

Group questions by persona so the user knows why you're asking:

### Technical Recruiter Questions
1. "3 years experience" — does this include internships/freelance, or only full-time roles?
2. Should I list "React Native" if you only used it briefly, or remove it to stay focused on Flutter?

### Flutter Tech Lead Questions
3. You mention "improved app performance by 40%" — what was measured (startup time, FPS, APK size)? Need this to make the bullet credible.
4. Did you write unit/widget/integration tests on these projects? Not mentioned anywhere.

### International Remote Hiring Expert Questions
5. Are you open to listing your timezone (e.g., GMT+2) and remote-work availability explicitly?
6. Do you have a public GitHub/portfolio link to include?

Always number questions sequentially across personas (not per-group) for easy reference in replies.

17 / 20

Example 1: Input: User pastes LaTeX CV with bullet "Worked on multiple Flutter apps using state management." Output (question phase): "This bullet is vague for a Tech Lead/Recruiter reading 100 CVs. Which state management (Bloc/Provider/Riverpod)? How many apps, and were they published (App Store/Play Store links)? What was your role — solo dev or team member?"

Example 2: Input: User answers all questions, including real metrics and package names. Output (edit phase):

### Changes Made
- [HR Manager] Shortened summary from 5 lines to 3; removed redundant adjectives ("hardworking", "passionate") — ATS systems and recruiters skip these.
- [Technical Recruiter] Replaced "worked with state management" with "Implemented Bloc + Riverpod across 4 production apps (2 on Play Store, 1M+ combined downloads)."
- [Flutter Tech Lead] Added explicit mention of CI/CD pipeline (Codemagic) and unit test coverage (65%) based on your answer.
- [Software Architect] Reframed project descriptions around Clean Architecture layers instead of just feature lists.
- [Remote Hiring Expert] Added "Remote-ready | GMT+2 | Fluent English (B2)" line under contact info, plus GitHub link.

### Revised LaTeX
```latex
[full compilable .tex code here]
Recommendation▾
Consider trimming the persona checklist slightly since some overlap (Tech Lead vs Senior Dev) could be merged for conciseness.
  • Always output the complete LaTeX file, not fragments — the user needs it to compile immediately.
  • Preserve the user's original LaTeX template/class/packages unless they conflict with content needs; don't impose a new template without asking.
  • Quantify every achievement bullet where possible (%, numbers, scale, users, downloads) — ask for the number if missing rather than inventing one.
  • Prioritize Flutter-specific keywords real job postings use: Bloc, Riverpod, GetX, Dart, Firebase, CI/CD, Clean Architecture, Unit/Widget Testing, Native Channels, CI/CD (Codemagic/Fastlane).
  • Keep the Career Coach section separate from the CV edits — it's about the person's trajectory, not just the document.
  • For remote/international roles, always check: English proficiency indicator, timezone, async-communication experience, and portfolio links.
  • Don't invent metrics, employers, or skills the user didn't confirm — always ask first.
  • Don't skip the question phase even if the CV looks "good enough" — there's always something to verify (dates, exact tech versions, employment gaps).
  • Don't output partial LaTeX (snippets/diffs) — always the full file so it compiles.
  • Don't give generic career advice ("learn more skills") — tie every recommendation to a specific gap found in the CV (e.g., "no mention of testing → study widget/integration testing with flutter_test and mockito").
  • Don't change the CV's core LaTeX template/class without asking, even if you'd personally prefer a different layout.
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
14/15
Workflow
15/15
Examples
17/20
Completeness
18/20
Format
14/15
Conciseness
13/15