💬 I'm a Senior Full-Stack Developer, so working with a UX mentor on my CV wasn't an obvious choice — but the context made sense. Igor and I had briefly crossed paths at a work event, where I mentioned I was job hunting but felt my resume wasn't landing. He offered to take a look, and I trusted the offer. It turned out to be one of the more useful professional conversations I've had. We worked mostly async, which kept things efficient. Igor went deep on how I was presenting my experience — not the technical side, but how it reads, what it signals, and whether my strongest points were actually visible. We then had a call to walk through the reasoning: why certain changes mattered, what recruiters and hiring managers actually look for today, and how to position my strengths rather than just list them. Igor's read on the current market was sharper than I expected — he's reviewed enough hiring pipelines and candidate materials to know what actually moves the needle. What I didn't expect was the LinkedIn and GitHub angle — Igor pointed out that my profile and activity were part of the picture, not just the document itself. After the final async review, I updated everything accordingly. Within a week, I got a cold outreach on LinkedIn — someone came to me. That was the signal I needed.

💬 I'm a Senior Product Designer with 10 years of experience, and I've grown my entire career at one company — a well-known outsourcing firm. It's been a solid path, going from early-career to senior there, but it meant my frame of reference for how to present my experience outside that context was narrower than I realized. When I started job hunting, I knew my resume wasn't doing me justice, but I couldn't pinpoint why.
We had one live session that covered both the resume and the portfolio. The resume needed a full rebuild — what I had wasn't working. The portfolio was trickier: most of my strongest work was under NDA, and I genuinely didn't know how to represent it without breaking confidentiality. Igor worked through that constraint with me — what could be shown, how to frame the rest, and how to expand the portfolio so it actually reflected ten years of experience instead of looking thin.
After the session, we did a couple of async rounds reviewing the updated versions. Igor was working from what I had going in and what I produced after — he couldn't verify the NDA-protected work directly, but the recommendations on structure and framing were spot on regardless.
We did this in October 2025. I started getting actual responses to applications instead of silence — and by February, I had accepted an offer. I won't credit one resume rebuild for the whole outcome, but the shift from no replies to real conversations happened right after we made these changes.

💬 Igor and I have known each other for years — he's actually family, not just a professional contact. When I got laid off at the end of 2025, I had a notice period of a few months to find something before it ended, so the pressure was real. I reached out mostly because I knew he'd worked at GlobalLogic, where the standards for what a resume and a candidate profile should look like are genuinely high — plus, he regularly works alongside developers and has experience managing small teams that included developers, so I knew he'd understand my background well enough to give relevant advice.
He didn't hesitate — offered to take a look right away, no back-and-forth. We went through my resume structure in detail: what a recruiter actually scans for first, then what a technical reviewer needs to see, and in what order. We also covered the visual side — layout, hierarchy, how it should look, not just read. It was clear this wasn't his first time doing this; the recommendations came fast and were specific, not generic.
What I didн't expect was the cover letter. I hadn't even considered writing one, honestly — Igor brought it up and helped me put one together, which ended up being something I used going forward.