Full stack developer

What happens for a full stack developer?

• The brief for a full stack developer is one person, not a roster.
• You write that brief before anyone is approached.
• Three finalists are introduced for a full stack developer.
• You interview them and you choose.
• You pay the person you select directly.
• There is no monthly markup on the wage.
• If a full stack developer leaves within six months, we search again.
• That second search is not a refund.
• Shared hours for a full stack 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 full stack 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 full stack developer.
• Wages for a full stack developer are agreed by you.
• We do not employ a full stack developer for you.
• You keep the relationship after you select.
• The shortlist for a full stack developer is three people.
• Each finalist for a full stack developer is interviewed first.
• You can reject the shortlist and talk again.
• The brief for a full stack developer names the output.
• Hours you share with a full stack developer are written down.
• Tools for a full stack developer are listed before day one.
• Month one is for learning the queue.
• Day 60 is when a full stack 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 full stack developer can take on this: Build the screen and the API change in the one ticket.
• a full stack developer can take on this: Cover the empty, error and saved states.
• a full stack developer can take on this: Add a test on the risky side of the change.
• a full stack developer can take on this: Demo it on staging before it is called done.
• A useful skill here: Both interface and server code.
• A useful skill here: A staging environment.
• A useful skill here: Tests where the risk is.
• A useful skill here: A demo, not only a pull request.

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