Mateusz Nowak · Rzeszów / remote · CET open to remote opportunities

Give me the messy,
high-context problem.
I’ll make it usable.

AI model training contractor, psychology student, C2-certified English communicator and systems-minded writer. I’m strongest where instructions are dense, edge cases matter, and the work needs both judgment and structure.

Cambridge C2 · Grade AAI model training · remoteResearch · writing · QAPolish native · English C2
AI evaluationresearch synthesiscontent QAwriting & editinginformation architecturecreative systemsAI evaluationresearch synthesiscontent QAwriting & editing
221/230Cambridge C2 overall score
Grade ACambridge C2 Proficiency
RemoteIndependent contractor workflow
EN / PLProfessional communication
01 / why me

Useful on day one.

I’m early-career, not pretending otherwise. The advantage is that I already work like somebody who expects the brief to be complicated: I read closely, learn fast, document what matters, and don’t need to be handheld through every unfamiliar tool.

01

Dense instructions don’t scare me.

Current AI model-training work requires adapting to task-specific rules, quality requirements and changing evaluation criteria while working independently.

02

I can actually write.

Cambridge C2 Proficiency at Grade A, long-form fiction, editing and research synthesis mean I can handle nuance, tone and precision instead of just producing grammatically acceptable text.

03

I think in systems.

From canon databases to product concepts and game rules, I naturally turn messy information into structures people can navigate, maintain and use.

04

I care about the edge cases.

I like QA-style work because the interesting part is usually where the obvious rule stops being obvious. That makes me useful in evaluation, review and consistency-heavy workflows.

03 / selected evidence

Different projects.
Same brain.

The portfolio is intentionally broad. The common thread is making complicated things coherent — whether the thing is an AI rubric, a fictional universe, a product concept or a research question.

04 / working style

Low ego.
High standards.

I don’t need the task to match a job title I’ve already had. Give me the goal, constraints and examples; I’ll learn the system, ask useful questions when needed, and make the output cleaner than I found it.

01

Understand before producing

Map the actual problem, assumptions and constraints before rushing into output.

02

Document the invisible logic

Make decisions and rules explicit enough that someone else can follow them later.

03

Check the weird cases

Consistency breaks at the edges. I actively look for those breaks.

04

Make the final thing easy

Complexity can stay backstage. The user or reader should get clarity.

If the job involves language, judgment, research, systems or quality, there’s a good chance I can become useful very quickly.