Somewhere around year five, an engineer’s job quietly changes. Less of the day is writing code and more of it is reading other people’s, explaining why the query should not be in the loop, and drawing the same architecture diagram for the third new hire. Nobody renames the job. Nobody adjusts the pay. It just happens.
The unpaid second job
Mentoring is real engineering work. It takes judgment that only comes from having shipped and broken production systems, and it produces something valuable: an engineer who no longer makes that class of mistake. Most companies treat it as a personality trait. “Great with juniors” appears in performance reviews next to “team player”, and is rewarded the same way, which is to say not.
The result is predictable. The seniors who care do the work at 6pm on their own time. The ones who stop caring stop doing it, and the juniors on their team learn from Stack Overflow. Neither outcome is good for anyone.
What changes when it is paid
- It gets scoped. A paid review has a turnaround and a rationale. A favour has neither.
- It gets recorded. Reviews counted, hours logged, a public profile that says what you do. Not a line in a review cycle nobody reads.
- It gets chosen. You pick the services, the stack and the hours, instead of absorbing whatever lands on your team.
- It gets respected. The junior on the other end is paying attention, because a real client is paying attention to them.
What we pay, exactly
Blacksmith.Works pays senior engineers per service, not per month. €25 per code review: a junior’s pull request against a real codebase, reviewed with a written rationale, returned within 48 hours, on your own schedule. €50 per mentoring hour: 1:1 calls, code walkthroughs, unblocking conversations, scheduled on your calendar. Solution architecture is scoped and quoted per project, done up front before the first pull request opens, with no on-call afterwards. Leading a complex build or executing one end-to-end as a Mentor Build is scoped at kickoff and pays more, because it is more.
One honest detail for readers outside North Macedonia: you are contracted through Deel and cover your own €50 a month contractor seat. One mentoring session covers it. We would rather say that here than have you find it on a form.
What we ask in return
Junior developers and paying clients depend on the mentors, so the bar is real. Five or more years of production work, with multiple deployments behind you and at least one stack you are known for. Mentor-grade communication: review that explains why a change matters and does not humiliate anyone, and the ability to say “I do not know, let me check”. A reliable cadence: reviews back within 48 hours, sessions kept or rescheduled in advance, honesty about your bandwidth.
Vetting is a short call where you walk us through a real architecture decision you made. If it is a fit, you are reviewing pull requests on your first project the week after.
The quiet benefit
You will be reviewing the engineers companies are about to hire. That is a first look at the ones you would want on your own team, long before a recruiter sees them. Several of the best hiring decisions in this industry were made by someone who had already read the candidate’s pull requests.
If you already mentor informally and wish it paid, apply as a mentor. Send a CV, a GitHub or a LinkedIn, whichever best represents the work you have shipped.