Each career brief includes a skills grid: evidence to examine, failures to spot and a focused exercise. Use it to discuss a deliverable and identify what to improve; it is not a certification or a hiring score.
UX research examines what people are trying to accomplish and the obstacles they encounter. It turns interviews, observations and task testing into evidence for decisions, with context and limitations. Its work helps decide what to investigate or change before designing a solution.
UI design defines how an interface presents information and makes actions recognisable. It describes components, visual hierarchy and relevant states, including errors and missing content. The handover should let implementation reproduce these rules with real copy and multiple languages.
Web design composes pages around content, visual identity and the visitor’s decisions. It organises reading, evidence and actions into reusable layouts. A composition should remain understandable with longer copy, a missing image or a change in available space.
Product design connects a usage problem with decisions that shape a feature. It compares solutions against needs, implementation constraints and available feedback. The expected result is a reasoned, testable decision, which may also mean simplifying or deferring a feature.
Front-end development turns content and design rules into usable browser behaviour. It connects HTML structure, styles, interactions and received data. Review the work through a complete journey, including keyboard use, late responses and states where results are not yet available.
Back-end development defines server processing, data persistence and access conditions. It turns business rules into operations with explicit inputs, effects and errors. An interface displaying success does not establish that these operations completed.
Full-stack development follows a feature from interface through processing to storage. It aligns contracts between these layers and prepares operation. Working across domains does not remove the need for specialist review, particularly for access, data and critical journeys.
Web integration assembles templates, content and media into usable pages. It checks that structure and components work with real headings, tables and translations. Assess its contribution through the rendered page and its use, beyond resemblance to a mock-up.
Quality assurance turns project expectations into reproducible checks and follows discrepancies through resolution. It specifies context, data and expected outcomes before interpreting a defect. Coverage follows journey risks; a test count alone does not describe it.
Web writing organises information to answer a question and support a decision. It connects facts to sources, chooses explicit headings and links, and clarifies ambiguous claims. The work includes approval and maintenance so the copy remains useful after publication.
SEO examines whether pages can be discovered and answer the searches they target. It connects content, structure, technical access and visibility observations. Recommendations should identify affected pages, expected effects and evidence for tracking changes without promising rankings.
Content management organises who writes, translates, approves, publishes and retires information. It maintains relationships between a source, its versions and pages reusing it. The aim is to make changes traceable and manageable, including when a regular team member is absent.
Data analysis turns a question into defined measures, checks collection and explains results within their scope. It distinguishes observed events from the business action being investigated. A report is useful when units, exclusions and limitations support an explicit decision.
Project management makes scope, dependencies, responsibilities and delivery conditions explicit. It connects team decisions with required contributions and known risks. A schedule should show what enables a stage to start or finish, rather than only listing dates.
The Product Owner clarifies intended value and the ordering of work. In Scrum, this role is accountable for maximising product value and effective Product Backlog management. Decisions stay tied to an explicit goal and available feedback rather than the number of requested features.
The webmaster oversees publishing and day-to-day site operation: content, components, access and incidents within the agreed scope. This role coordinates changes with relevant specialists and checks journeys afterwards. Technical, editorial and hosting responsibilities need owners even when different providers handle them.
Choose an exercise, keep your test data and tell your choices: problem, constraints, results, checks and limits. A transparent presentation allows you to discuss the work without inventing a customer experience.