Measurable impact on performance and the productSee strengths
SAMPLE REPORTSynthetic data · fictional candidate
Julia Zawadzka, the companies and every business outcome are fictional. This sample demonstrates the format and level of detail of a CV Unfold report.
Back to homepageSample CV report
Julia Zawadzka · Senior Frontend Engineer
79/100
OVERALL CV COMMUNICATION QUALITY
The CV credibly communicates Senior Frontend level, mainly through strong performance, architecture and quality evidence from the earlier role, but the most recent experience is described more generically and shows result and individual-ownership boundaries less clearly.
PERCEIVED LEVELSenior Frontend Engineer
Applying for levelSenior
FIRST 20 SECONDSINTERVIEW
3 findingsFindings and recommendations4 strong signalsWhat works in your favour3 prioritiesYour revision priorities
DOCUMENT PERCEPTION
Based on the CV's content and structure. This is not an assessment of the person.
The score describes CV quality against the application target.
01
How the document frames your profile
PERCEIVED LEVEL
The document shows an experienced frontend profile with around eight years in React and TypeScript. The strongest evidence concerns performance, modular architecture, end-to-end testing and accessibility. The most recent role suggests a broader scope of responsibility, but its description is less concrete than the Railbird Mobility role.
What supports this impression
Credible architectural thinkingSee strengths
A practical approach to quality and accessibilitySee strengths
Breadth of frontend collaboration and impactSee strengths
What creates doubt
The most recent role shows results less clearly
VertexPay contains important initiatives, but the bullets on Core Web Vitals, the migration and the component library state no observable result or improvement mechanism.
Individual ownership boundaries need clarification
The phrases “Helped build”, “Coordinated” and “took part in discussions” show involvement in important initiatives, but do not clearly separate personal decisions from the team's work.
The strongest evidence of seniority sits in the earlier role
The most convincing numbers and architectural decisions are described at Railbird Mobility, while the most recent role occupies the more prominent position but has more generic bullets.
What they may ask
Which technical decisions during the migration from Redux to hooks and React Query belonged directly to you, and which were agreed as a team?
Why this question?
The CV describes planning and delivering the migration, but does not show its scope, constraints or specific trade-offs.
What concrete result did the 28-component library deliver, and what was the scope of your personal contribution to building it?
Why this question?
The document states the component count and adoption, but does not describe the effect on consistency, delivery speed, quality or ownership of standards.
How was the Core Web Vitals and performance improvement at VertexPay measured, and which technical work had the biggest effect?
Why this question?
The most recent role states a performance improvement but gives no before/after values or improvement mechanism.
What were the constraints and criteria for the staged rollout of the onboarding modernisation?
Why this question?
The CV points to pre-release checks and a rollout that did not disrupt onboarding, but does not explain the decisions, risks or coordination involved.
02
FIRST 20 SECONDS
After 5 seconds
A Senior Frontend Engineer with around eight years of experience, focused on React, TypeScript, performance, accessibility and UI architecture.
After 10 seconds
A concrete performance result stands out — p75 LCP down from 4.4s to 2.5s — along with experience authoring an RFC and splitting a large application into domain modules.
After 20 seconds
The profile gives good reason for a Senior Frontend conversation, but raises the question of whether the most recent role had comparable impact and ownership scope, since its results are described less concretely.
SIMULATED OUTCOMEINTERVIEW
This is a simulation of the first impression created by the document, not a real hiring decision or a prediction for a specific application.
03
Seniority signals by category
Impact and outcomes
The category has very strong evidence at Railbird Mobility: concrete LCP and abandonment results. At VertexPay, impact is stated but without a before/after comparison or an observable consequence, so the repeatability of evidence in the most recent role is limited.
74/100Ownership and responsibility
The CV shows planning a migration, authoring an RFC and leading it to agreement. In the most recent role, though, some bullets use the verbs “Coordinated” and “Helped”, which makes the boundaries of personal responsibility less clear.
76/100Frontend credibility
The document contains concrete frontend mechanisms and results: route-level code splitting, image optimisation, performance budgets, Playwright, an accessibility improvement and an architecture migration. This is evidence of practice, not just a technology list.
86/100Frontend architecture and systems thinking
The RFC on domain modules, the migration to a more modular structure and the shared component library show systems thinking. VertexPay, however, lacks detail on component boundaries, the library's API or the reasoning behind key trade-offs.
82/100Collaboration
The CV shows collaboration with product, design, backend, QA and platform teams, plus work on a solution used by three product teams. Some bullets, however, do not specify what impact the applicant had on agreements and decisions.
82/100Clarity and signal hierarchy
The CV has clear sections, chronology and distinct specialisations, but the best evidence — concrete performance results and the RFC — sits with the earlier role. The most recent role and its initiatives are more generic, so the signal hierarchy does not maximise how seniority is read.
72/100ATS / technical document hygiene
Whether the file parses correctly. This is not an assessment of content or seniority.
100/100
- Real text layer detectedText can be extracted from the file, so ATS systems can read it.
- Text extracts in a natural orderExtraction order matches the document's visual layout.
- Standard sections are recognizableExperience, skills and education have recognizable headings.
04
What weakens the document — evidence before opinion
The most recent role states an improvement but not its consequence
TO IMPROVE
VertexPay bullets mention improving Core Web Vitals, the component library and the migration, but show no before/after values, regression reduction, faster delivery or other observable outcome. The earlier role contains a markedly stronger impact signal.
WHY IT MATTERS
For a Senior target, the reader needs to see that impact and results are current, not only tied to earlier experience.
WHAT TO DO
For each key VertexPay initiative, establish a concrete observable consequence, then add it to the relevant bullet only when it follows from actual data or a confirmable effect.
EVIDENCE FROM THE CV
Helped build a shared component library with 28 components, now used across several parts of the product.
Planned and delivered the migration of onboarding screens from legacy Redux patterns to hooks, React Query and a more modular frontend structure.
Improved Core Web Vitals and load performance across the onboarding and account-management flows.
Reduced p75 LCP on the mobile booking flow from 4.4s to 2.5s and cut mobile booking abandonment by 10% through route-level code splitting, image optimisation and performance budgets in CI.
Individual ownership boundaries are unclear in the most important initiatives
TO IMPROVE
VertexPay uses the phrases “Coordinated”, “Helped build” and “took part in architecture discussions”. These show involvement in important work, but do not explain which decisions, implementation elements and agreements belonged directly to the applicant.
WHY IT MATTERS
An unclear split of responsibility can weaken the Senior-level reading, even when the initiative itself has the right scope.
WHAT TO DO
Clarify the personal decisions, implementation scope and responsibility for agreements in the onboarding redesign and the component library before strengthening the verbs describing your contribution.
EVIDENCE FROM THE CV
Coordinated the frontend delivery of the customer onboarding redesign used by three product teams, working with product, design and backend.
Helped build a shared component library with 28 components, now used across several parts of the product.
Coordinated frontend implementation across several onboarding workstreams and took part in architecture discussions with backend engineers.
Established reusable patterns for forms, navigation, validation and feedback states, working with designers and engineers from other teams as adoption grew.
The strongest evidence is less exposed than the most recent role
TO IMPROVE
The most concrete achievements — the LCP result, the effect on booking abandonment and the architectural RFC — sit with Railbird Mobility. VertexPay, the first and most prominent role, is dominated by descriptions of coordination, feature-building and support.
WHY IT MATTERS
A first read of the CV may suggest less current impact than the document as a whole actually shows.
WHAT TO DO
Move the LCP result and the RFC closer to the summary, keeping their attribution to the Senior Frontend Engineer role at Railbird Mobility.
EVIDENCE FROM THE CV
Coordinated the frontend delivery of the customer onboarding redesign used by three product teams, working with product, design and backend.
Helped build a shared component library with 28 components, now used across several parts of the product.
Planned and delivered the migration of onboarding screens from legacy Redux patterns to hooks, React Query and a more modular frontend structure.
Built customer-facing features, conducted code review and supported less experienced frontend developers with day-to-day technical questions.
Reduced p75 LCP on the mobile booking flow from 4.4s to 2.5s and cut mobile booking abandonment by 10% through route-level code splitting, image optimisation and performance budgets in CI.
Authored an RFC for splitting the large frontend application into domain modules and led alignment with the backend and platform teams before rollout.
Strong signals
A performance result tied to its mechanism
The document does not stop at a performance-improvement claim: it states the p75 LCP change, the effect on booking abandonment, and the technical work behind it.
Evidence of an architectural decision
Authoring the RFC on domain modules and leading it to agreement with other teams show work on the structure of a larger frontend application.
Frontend quality spanning testing and accessibility
Introducing Playwright into the release process, plus concrete keyboard-navigation and form-error-handling improvements, strengthen the profile's credibility.
Experience with shared solutions
The 28-component library and the reusable patterns for forms, navigation, validation and feedback states show impact broader than a single feature.
Action plan
Clarify the impact of the most recent role
Establish and add to the VertexPay bullets verifiable results for the performance improvement, the migration and the component library, without inventing new or unconfirmed metrics.
Clarify your personal scope of responsibility
In the VertexPay descriptions, separate your own decisions and actions from the team's work, particularly for onboarding, the component library and the migration rollout.
Strengthen the hierarchy of existing evidence
Move or highlight the LCP result and the RFC in the achievements summary, while keeping their attribution to Railbird Mobility unambiguous.
FROM REPORT TO REVISION
How to revise your CV
The report identifies what to clarify and improve. You choose the wording and are responsible for its accuracy.
- Establish the facts
Review the cited CV passages and specific advice. Identify your own work, the support you received and what you can confirm. Check anything you cannot remember.
- Revise in your own words
Clarify the description yourself using the recommendations. Include only true information. If the advice concerns something you have not done, do it before adding it to your CV.
- Recheck the new version
Read the whole CV, save the revised PDF or DOCX and upload it for another analysis. Compare findings and evidence as well as the score.
A clearer description does not guarantee a higher score. The score depends on the information shown in the new document.
What does your CV communicate?
See your free result and most important evidence.