Skip to content
StatusGet emergency help

A senior engineer on your team for three months or longer

Steady senior capacity on a B2B contract: a product to finish, a system to modernize, or a gap to cover until you hire. It often starts after an incident, when I already know the system.

Discuss a contractSee the work
Your week with a contract
Your days, on your team’s hoursEmergencies and On CallWake Simon, 00:00–06:00

Full time, about 22 days a month

The terms, on one page

Engineering contract

evolved s. r. o.
Valaská Belá 482, 972 28 Valaská Belá

Parties
Your company and evolved s. r. o., IČO 56 841 540, VAT ID SK2122462947
Engineer
Šimon Šoka, managing director. No subcontractors, no handover to someone junior.
Length
Three months minimum, then month to month with one month’s notice
Time
2 to 5 fixed days a week, up to full time. Hours follow your team, in any time zone
Rate
Day rate quoted after a 30-minute scoping call
Invoicing
Monthly in euros, for the days worked
Location
Remote from Slovakia. On site for kickoff if it helps
Reporting
Written update every Friday, handoff note in the last week
Availability
Reachable every day, around the clock. Other clients’ incidents never take your contract hours
Your companySignature, name, date
Šimon Šoka
Šimon ŠokaFor evolved s. r. o.

A summary of the usual terms. The contract itself is written for each engagement.

Where a contract fits

After a launch

The release is out and the list of fixes, performance work and missing pieces is longer than the team.

v1.0 shipped · backlog growing

Legacy .NET that has to move

Framework to modern .NET, a monolith that needs seams, a database nobody wants to touch.

net48 → net9

A gap until you hire

A senior engineer leaves, or the hire is months away, and the roadmap cannot wait.

seat open · 3 mo

AI-native delivery

Claude Code, MCP and automated review loops in the team’s workflow, with tests and review kept.

claude code · mcp · review

From first call to first commit in about two weeks

  1. 30-minute call

    The system, the goal, what done looks like.

  2. Written scope

    Days per week, length and day rate on one page.

  3. Contract and access

    Signed with evolved s. r. o., least-privilege access set up.

  4. First commit

    A small, real change through your normal review.

  5. Written update

    Done, blocked, next. Short enough to read on a phone.

  6. Handoff note

    What changed, where it lives, what to watch.

Tell me about the team and the system

Five lines are enough for a first reply. I reply to contract enquiries the same day.

Discuss a contractsimon@bettercallsimon.eu

What to send

Company and team size:
What the system does, stack:
What you need done in 3 to 6 months:
Days per week you have in mind:
Earliest start date: