Get in touch
A description of the work is enough. You do not need a finished job specification.
Tell us what the work is and what your team already has. That is enough to start, and you do not need a finished job specification; working out what the role actually is tends to be the most useful part of a first conversation.
What is useful to include
- What the system does and roughly what it runs on.
- What the new person would own, and what is already decided.
- Whether this is new development, maintenance, or a migration, since these attract different people.
- Which hours genuinely need to be covered and why.
- Whether anyone on your side has capacity to review incoming work.
- Your timeline, and what happens if it slips.
What happens next
We reply with questions or with an honest view that we are not the right fit. If it looks like a fit, the next step is a conversation about the work rather than a proposal, because a proposal written before we understand the problem is a document about us rather than about you.
We will also tell you at this stage if we think you should hire locally, if the role reads as two roles, or if the level looks wrong for the work. That conversation is cheapest now.
Frequently asked questions
Do we need a finished job specification?
No, and a confident specification that is wrong is worse than an open one. A description of the system and the problem is enough.
How quickly will you reply?
Within a working day, with questions or with a straight answer that we are not the right fit.
Is the first conversation chargeable?
No. If it turns out there is no engagement here, you have still had a useful conversation about the role and we would rather that than a badly-fitting engagement.
Can you help if we are not sure we need to hire at all?
Yes, and that is a conversation worth having. Delivery problems are frequently review capacity, architecture or prioritisation rather than headcount, and adding developers to those situations makes them worse.
Do you sign non-disclosure agreements?
Yes, routinely, before any detailed discussion of your systems.
What if we are in a different time zone?
Say so and we will work around it. Scheduling across time zones is what we do.