Backend developer

What happens for a backend developer?

• The brief for a backend developer is one person, not a roster.
• You write that brief before anyone is approached.
• Three finalists are introduced for a backend developer.
• You interview them and you choose.
• You pay the person you select directly.
• There is no monthly markup on the wage.
• If a backend developer leaves within six months, we search again.
• That second search is not a refund.
• Shared hours for a backend developer go in the brief.
• Name the software required on day one.
• Onboarding covers the first 30, 60 and 90 days.
• Time tracking can be set up after the start.
• A call line with SMS can be part of setup.
• Messaging tools are recommended for the team.
• You arrange payment for a backend developer yourself.
• Contract guidance stays general and simple.
• It is not a substitute for your own adviser.
• Discovery starts with the bottleneck in the business.
• The role is written before sourcing begins.
• Applicants are screened before you meet anyone.
• References are checked on the shortlist.
• About 21 days is the target to three finalists.
• That timing is a target, not a promise.
• The deposit opens the search.
• The balance is due when you select someone.
• Remote staffing is another name for this hire.
• A dedicated offshore hire is the offer.
• Outsourcing the queue still leaves you as the manager.
• The person joins your team, not a shared floor.
• Clients also compare a one-time fee with a monthly markup.
• The published fee covers the search for a backend developer.
• Wages for a backend developer are agreed by you.
• We do not employ a backend developer for you.
• You keep the relationship after you select.
• The shortlist for a backend developer is three people.
• Each finalist for a backend developer is interviewed first.
• You can reject the shortlist and talk again.
• The brief for a backend developer names the output.
• Hours you share with a backend developer are written down.
• Tools for a backend developer are listed before day one.
• Month one is for learning the queue.
• Day 60 is when a backend developer runs the queue.
• Day 90 is a simple review of results.
• A replacement search is the guarantee.
• Read the guarantee terms before you rely on it.
• a backend developer can take on this: Implement the endpoint or the job in the ticket.
• a backend developer can take on this: Add a test for the failure case, not only the success.
• a backend developer can take on this: Check logs when a request fails.
• a backend developer can take on this: Note the migration or the config the release needs.
• A useful skill here: Server-side code your team uses.
• A useful skill here: SQL or the data store you use.
• A useful skill here: Logs and a staging environment.
• A useful skill here: Review before release.

How a search works

Process

1. 01

   Agree the brief

   Agree the tasks, tools and hours

2. 02

   Search

   We search and assess candidates

3. 03

   Shortlist

   About 21 days to three finalists is a target

4. 04

   You choose

   You interview them and you choose