Fiktives Beispiel · Alex Morgan ist keine reale Person. Dieser Bericht zeigt Format und Tiefe einer vollständigen Analyse; er ist keine echte Bewertung.

DIE ANALYSE VON DER QUELLE BIS ZUM VORSCHLAG

Ein PDF, eine Stelle. Jede Feststellung verweist zurück auf die Seite.

Alex ist Informatikabsolvent und bewirbt sich bei Meridian. Der Lebenslauf ist ein echtes einseitiges PDF und wird wie ein Upload behandelt: Text und Seitenvorschau stammen aus der Datei selbst. Lesen Sie die vorrangigen Korrekturen, öffnen Sie die zitierten Passagen, vergleichen Sie drei Formulierungsvorschläge mit dem Original und sehen Sie, wie ein in privaten Notizen festgehaltenes Messergebnis anders behandelt wird als die Angaben im Lebenslauf.

Fiktiven Lebenslauf, Stellenanzeige und ergänzende Angaben lesen

Eingereichter Lebenslauf

Das geprüfte PDF öffnen

ALEX MORGAN 
Software Engineer 
alex.morgan@example.com
07700 900123 · Bristol, UK
github.com/alexmorgan-dev 
PROFILE 
Passionate and detail-oriented Computer Science graduate with a strong interest in building reliable
software. A quick learner and team player who is comfortable working across the stack and keen to
develop further in a fast-paced environment. 
EXPERIENCE 
Northstar Labs, Bristol — Software Engineering Intern Jun 2024 – Sep 2024 
Was responsible for building a Python validation service which was used to check around 120,000
records every day against a set of 12 business rules defined by the product team.
Worked on improving the performance of internal tools.
Collaborated with the engineering team on new features for the customer dashboard.
Took part in code reviews and daily stand-ups. 
Waterside Café, Bristol — Team Member (part-time) Oct 2022 – May 2024 
Served customers and handled cash and card payments during busy weekend shifts.
Trained three new starters on the till system. 
PROJECTS 
Transit Monitor — TypeScript, React, Node.js, PostgreSQL 2024 
Built a dashboard that tracks service disruptions across 6 Bristol bus routes, with a PostgreSQL data
pipeline that ingests open data every 5 minutes.
Responsible for the React frontend and the Node backend, and also wrote automated integration tests
for the API. 
Recipe Share — Python, Flask, SQLite 2023 
A small web app for saving and sharing recipes, with user accounts and search. Various features. 
EDUCATION 
University of Bristol — BSc Computer Science, Upper Second Class (2:1) Sep 2021 – Jun 2024 
Final-year project: anomaly detection in public transport arrival data (Python, scikit-learn), graded 72%.
Relevant modules: Software Engineering, Databases, Distributed Systems, Machine Learning. 
Redland Sixth Form College — A levels: Mathematics (A), Computer Science (A), Physics (B) 2019 – 2021 
SKILLS 
Languages: Python, TypeScript, JavaScript, SQL 
Frameworks and tools: React, Node.js, Flask, PostgreSQL, Docker, Kubernetes, AWS, Git, GitHub
Actions 
Spoken languages: English (native), Spanish (conversational)

Stellenanzeige

Graduate Software Engineer
Meridian · Bristol (hybrid) · Permanent · Start September 2026

About the role
You will join a product engineering team that builds the scheduling and reporting tools our operations customers rely on. Graduates work in a small squad with a mentor, ship to production within their first month and rotate across the stack during the two-year programme.

What we are looking for
Required: a degree in Computer Science or a related field.
Required: practical experience with TypeScript or Python, from work, study or personal projects.
Required: experience writing automated tests.
Preferred: PostgreSQL and deployment experience.
Preferred: experience working in an agile team.
Applicants must have permission to work in the UK.

How to apply
Submit a CV of no more than two pages.
Include a cover letter with your application explaining why you want to work at Meridian.

Ergänzende Angaben

Northstar Labs: the internal tool was the nightly customer report generator. I rewrote the slowest SQL queries and added caching for repeated lookups. The run time went from about 40 minutes to under 10; my team lead measured it over two weeks. The customer dashboard work was two features, an export button and a date filter, both paired with a senior engineer.
Transit Monitor: I implemented the API and the React frontend and deployed the app with Docker Compose on a university VM. No Kubernetes was involved. Kubernetes and AWS come from a two-day online course, not project work.
Right to work: British citizen.
Analyse abgeschlossen
Beispielanalyse. Fiktiver Lebenslauf und beispielhafte Bewertungen. Es wurde kein Modell aufgerufen.
ANALYSEERGEBNISSE

Alex Morgan.

Graduate Software Engineer · Meridian

1 PDF-SeiteBewertungssicherheit: high
Zugangsvoraussetzungen klären
Gesamtbewertung
73/100
Belegte Passung + Lebenslaufqualität
73/ 100
Lebenslaufqualität
68/100
Wie klar der Lebenslauf Belege darstellt
Belegabdeckung
71%
Anforderungen mit zitierter Lebenslaufpassage
Passung zur Rolle
75/100
Belege für die Anforderungen dieser Rolle
alex-morgan-cv.pdf
Lebenslauf, Seite 1
DIE BEWERTUNG

Ihr Lebenslauf, bewertet.

Alex has the evidence a graduate hiring manager wants: a degree, a Python service with real volume, and a tested full-stack project. The CV undersells it. The strongest internship bullet opens with fourteen words of filler, the internal-tools bullet gives the reader nothing to ask about, and the profile could belong to anyone. Four of seven requirements are demonstrated; deployment and agile practice are close, and work permission is not stated anywhere on the page.

Zugangsvoraussetzungen Nicht bestätigtRegeln zur Lebenslaufeinreichung Belegt

Worauf Sie sich konzentrieren sollten

Kritisch

Make the internal-tools bullet concrete

This is the bullet an interviewer will ask about first, and it gives them nothing: no tool, no change, no result. Next to the validation service it reads like padding.

Verbessern

Say what you built on Transit Monitor

“Responsible for” describes a remit, not work. The strongest part of the sentence, the integration tests, arrives last as an afterthought.

Was funktioniert

A number a hiring manager can picture

120,000 records a day against 12 business rules tells the reader the scale of the internship work without any adjectives.

Testing inside a real project

Integration tests for a working API with a live data pipeline is exactly the evidence the testing requirement asks for.

Relevant, graded final-year work

Anomaly detection on transport data with a stated grade is specific and close to Meridian’s domain.

Aufschlüsselung der Bewertung

Belege & Konkretheit6/10

Two bullets carry numbers a reader can picture. Three describe activity with no tool, change or result.

Relevanz & Priorisierung6.5/10

The most relevant work is on the page but not in front: the tested project sits below a café job, and the profile spends its space on adjectives.

Klarheit & Struktur7.5/10

Sections are in a sensible order with consistent entry headings. Ownership is stated as a remit rather than as work done.

Darstellung & Lesbarkeit8/10

One clean page, right-aligned dates and clear headings. The bottom third is empty while two bullets wrap for a single word.

Konsistenz & Glaubwürdigkeit7/10

Nothing on the page contradicts itself. Four tools are listed with no supporting work, which invites interview questions the CV cannot answer.

Sprache & Feinschliff7/10

Readable and error-free. Passive constructions and generic adjectives slow the opening.

Die Bewertungen beurteilen den Lebenslauf, nicht Ihre Einstellungschancen.

Klärenswert

  1. 01What did you change in the internal tools, and how was the result measured?
  2. 02Which dashboard features did you build, and what part was yours?
  3. 03Is UK work permission already held?

One A4 page with clear section headings and right-aligned dates, so the timeline scans quickly. The bottom third of the page is empty while the tools line and one project bullet each wrap for a single word; a slightly wider text column would fix both. The A-level entry runs into its date. The profile paragraph is the densest block on the page and the least specific.

RASTER 1.0.0 · Hand-authored fictional exampleFIKTIVES BEISPIEL · 20.9.2026
IHRE NÄCHSTE FASSUNG

Formulierungsvorschläge

3 Vorschläge

Prüfen Sie jede Änderung an Ihrer Erfahrung, bevor Sie sie in Ihr eigenes Dokument übernehmen.

ÄNDERUNG 01LEBENSLAUF · SEITE 1
ORIGINAL

Was responsible for building a Python validation service which was used to check around 120,000 records every day against a set of 12 business rules defined by the product team.

VORSCHLAG
Built a Python validation service that checked around 120,000 records every day against 12 business rules defined by the product team.

Puts the verb first and removes “was responsible for … which was used to”. Keeps Python, 120,000 records a day, 12 rules and the product team’s ownership of the rules; adds no result.

ÄNDERUNG 02LEBENSLAUF · SEITE 1
ORIGINAL

Responsible for the React frontend and the Node backend, and also wrote automated integration tests for the API.

VORSCHLAG
Built the React frontend and the Node backend, and wrote automated integration tests for the API.

Replaces a remit (“responsible for”) with the work, and drops “also”. Keeps both tiers and the tests exactly as stated; does not claim sole ownership or design decisions.

ÄNDERUNG 03LEBENSLAUF · SEITE 1
ORIGINAL

A small web app for saving and sharing recipes, with user accounts and search. Various features.

VORSCHLAG
A small web app for saving and sharing recipes, with user accounts and search.

Removes “Various features”, which adds nothing the reader can check. Everything that remains is already in the original.