Skip to main content
GullySystem

How a Staffing Engagement Starts, Is Trialled and Ends

An engagement starts with an interview. You meet the named engineers, a trial that either side can stop follows, and it ends with notice, written handover and removal of access.

How the first stretch is set up

Meeting the people

You interview before you sign. Anyone you do not want is replaced before a contract exists, which is far easier than asking for a change once work has started.

Access and accounts

Accounts open in your name. Repositories, cloud consoles and trackers are set up under your company, and each engineer holds an individual login that you can revoke at once without disturbing anyone else.

The trial

A trial comes first. An early stretch, agreed in writing, lets either side stop on short notice if the fit is wrong, and it tests working habits and communication as much as skill.

Notice

Longer notice follows the trial. Its length is set in the contract, and it should be long enough for you to find a replacement or for the departing engineer to write handover notes.

What you hold the whole time

Everything important sits with you early. Source code lives in your repository, cloud, domain and third-party accounts are registered to your company, and secrets are kept in a vault that you control from day one. Documents are written as work goes. Nothing waits for a rushed final week.

Where endings go wrong

Knowledge in one head is fragile. A rule written down during the final week is usually thin, so ask for exit sessions and for a recorded walk through of the release steps. Also check that no shared password stayed in use, because removing a person achieves nothing while the password lives on, so rotate keys on the last day.

FAQ

Frequently asked questions

Is there a trial period?

Yes, and it is written down. Either side can end the engagement on short notice during the trial if the work or the working relationship is not right, and you pay for time worked.

What access do the engineers get on the first day?

Only what the first tickets need. Accounts are issued in each engineer’s own name, more rights are added when a task requires them, and production access comes last, often not at all.

How much notice is needed to end an engagement?

The contract sets it. Notice applies after the trial, giving you time to find a replacement and giving the engineer time to write handover notes, so that neither side is surprised.

What do we keep when the engagement ends?

You keep all of it. The code, the accounts, the documentation and the recorded walk-throughs were yours from the start, individual logins are removed, and the engineers retain no copy of your code.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

What happens after you share your requirements

  1. A senior engineer reads your answers. Nobody phones first.
  2. Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
  3. If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
  4. No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.

Share your requirements