feat: motivation letters per work experience

[FindMalek]

Context

Original ask: write a letter of motivation for each of Malek's work experiences (Digital Army through DeepMetis, per the original phrasing — meaning across the current roster of companies, not literally just those two).

Design/format reference given: https://x.com/arthur_designss/status/2090453771516359164

⚠️ Reference not yet reviewed. The browser tool used to view this link failed to respond during this session (tried twice, did not retry further per this repo's own troubleshooting guidance of not looping on failing tool calls). The link is included here so it's not lost, but nobody has actually seen what it shows yet — could be a resume design, a letter format, a portfolio layout, or something else entirely. Do not start implementation from this issue until someone has actually opened the link and described/confirmed what it's referencing.

Relationship to testimonials (important distinction, don't conflate)

Per earlier discussion (2026-08-20): motivation letters and testimonials are explicitly different things:

• Testimonials (tracked in feat: build recommendations and testimonials system #65/feat: build recommendations and testimonials system #73): what other people said about working with Malek — avatar, quote, their name, their position, their company.
• Motivation letters (this issue): written by Malek, about each experience — presumably explaining why he took the role, what he was hoping to get out of it, or a reflective narrative. The exact content/purpose of a "motivation letter" per past experience still isn't fully specified — was one company-side artifact (used when applying?) or written after the fact for the portfolio?

The original ask also said motivation-letter pages should cross-link testimonials: show what people said about Malek's work at that specific company on the motivation-letter page for that company, with their avatar and position. This means the motivation-letter page's data model depends on the testimonials data model (#65/#73) — build/finalize that first, or at least keep the two schemas compatible.

Scope questions to resolve before implementation

• What does "motivation letter" actually mean here — a formal cover-letter-style artifact per company, or a more casual reflective write-up? The reference link should clarify this once reviewed.
• Per-company, one page each (matching the "one issue per item" convention already applied to work case studies) — confirm this applies here too once scope is clear.
• Which companies get one: the full current roster (Jobflow, Hortensia, Function03, Promolab/Endless Byte pending restructure, Digital Army, QTech, DeepMetis, 8Returns, Undrstnd Labs), or a specific subset?

Acceptance criteria

• Reference link reviewed and described in a follow-up comment on this issue before implementation starts.
• Data model / page structure decided, including how testimonial cross-linking works (avatar + position + quote pulled from the same source as feat: build recommendations and testimonials system #65/feat: build recommendations and testimonials system #73's testimonial data).
• Content written per company (real, in Malek's voice — not generic/templated filler).

Out of scope

• Testimonial collection itself — tracked in feat: build recommendations and testimonials system #65/feat: build recommendations and testimonials system #73, this issue only consumes that data once it exists.