Why software employees leave and how to understand why
Engineers and product staff leave for many reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 min readRead articleA blockchain development firm builds smart contracts, wallets and platforms for clients, where one coding error can be costly. Here is how to manage engineers, auditors and project staff in a field that moves fast and pays in unusual ways.

Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsA blockchain development company designs and builds decentralised applications, smart contracts, wallets, token systems and private ledgers for client businesses and start-ups. The work is split between engineers who write contract code, front-end and integration developers, security reviewers and project managers who handle clients, often abroad. Mistakes in deployed code are hard to reverse, so review discipline matters more than speed. The people are scarce, highly mobile and often offered work by new projects every month. Some prefer to be paid in tokens, some work from other cities, and some want to be seen publicly for their contributions. All of this makes pay, ownership of code and loyalty harder to settle than in an ordinary software house. See also HR for IT and software.
These are the places the people side of this kind of business tends to give way. The rest of this page works through them.
HR here has to work for each of these groups, not only the office. The set-up below is written with all of them in mind.
GullyHR runs talent acquisition for permanent roles in blockchain development companies. For each role we agree the job description with you, find and screen candidates against it, and support the offer through to joining. Tell us the role and the number of people, and we start there.
We recruit permanent employees. We do not supply contract or temporary staff.
Every business interviews, but few have a written process that works the same way for every role and every interviewer. GullyHR designs yours, from the role brief to the offer, trains your managers to run it, and can run it for you on the roles you hand us.
We agree what the role must deliver, the must-have and nice-to-have skills, and how each will be scored.
Screening call, assessment, interview rounds and decision points, sized to the role and the number of people you hire.
Structured questions for each role family and a rating guide, so two interviewers judge the same answer the same way.
A short briefing for your managers on what to ask, what to avoid and how to give a clear yes or no.
Who approves, how the offer is made, and how candidates are kept informed from first call to joining.
A good contract developer hears from recruiters every week, so a small pay gap or a dull project can end a stay.
Clients push for launch dates, and the second pair of eyes that catches a flaw is the first thing dropped.
Staff ask for part-payment in tokens, the value swings, and no one is sure what was agreed or how it is recorded.
Remote developers are hard to onboard, and ownership of the code they write is often left unclear.
Who holds deployment keys and server access must be settled, and must change cleanly when a person leaves.
Work surges with a market mood and dries up quickly, which strains hiring and makes layoffs a real risk.
Reviewers worry about a missed bug, and without support they burn out or become over-cautious.
Developers get pulled into support, social channels and client calls that were never in their job.
Start with the topics that matter most here: Retention and Attrition Management; Compensation, Payroll and Benefits; Policies, Compliance and Governance. Then work through the rest. Each topic is written for information technology and software, not in general.
Who leaves, when, why — and which of them mattered.
Salary structure, payroll inputs and a month that closes on time.
Policies a manager can apply, and obligations with owners and dates.
How many people, in which roles, by when — and what they will cost.
Structure, reporting lines and who is allowed to decide what.
Requisition to joining, the same way every time.
A first day that is the same for the fifth joiner as the first.
Records, attendance, leave and the day-to-day HR that must simply work.
Goals, reviews and ratings that hold up in a conversation.
Training planned from need rather than from the calendar.
Named backups for the roles that cannot be vacant.
Communication, recognition and the conditions people actually work in.
Two routes — one for complaints, one for conduct — kept separate.
Induction, records, incident reporting and follow-through.
Resignation to relieving letter, in a defined order.
Records that survive people, and approvals that do not queue.
A short monthly pack management actually reads.
An HR function that runs the same way every month.
The pieces a blockchain development companies business puts in place, in an order that makes each easier. Open any card for the detail.
A clear ladder from junior developer to lead auditor, with what each level owns.
A clear ladder from junior developer to lead auditor, with what each level owns. Compensation benchmarking helps place pay against the market for scarce skills.
Employees and contractors sign clear terms on code ownership, client data and keys, kept in order through the HR documentation process.
Employees and contractors sign clear terms on code ownership, client data and keys, kept in order through the HR documentation process. Have a qualified professional review the wording.
If tokens or equity-like rewards are offered, record exactly what, when and how it is valued, and take advice before promising it.
If tokens or equity-like rewards are offered, record exactly what, when and how it is valued, and take advice before promising it.
No contract goes to a client until a named second reviewer signs off, and their time is planned into the project.
No contract goes to a client until a named second reviewer signs off, and their time is planned into the project.
A checklist covering keys, repositories, servers and shared accounts, completed through the exit and offboarding process.
A checklist covering keys, repositories, servers and shared accounts, completed through the exit and offboarding process.
Time to study new tools and audit reports keeps skilled people interested and the firm's work current.
Time to study new tools and audit reports keeps skilled people interested and the firm's work current.
Before changing anything, find out what is true today. These checks take an afternoon and tell you which of the topics above to start with.
Share your requirementsConfirm with a qualified professional. What applies to you depends on your business, your state and your arrangements, and it changes. This page describes practice. It does not state a legal position.
The services below fit this kind of business best. Each starts by recording where you stand, and every later report compares against that. We do not promise outcomes.
A view of what scarce engineers and auditors earn in the market, so offers and raises are made with evidence.
Clean agreements on code ownership, confidentiality and notice, so the firm is not exposed after someone leaves.
A hand-over checklist for keys, repositories and client knowledge when engineers move on.
Planned time and budget for skills in contract languages, tooling and security practice.
Start with a free conversation, or see the paid HR Diagnostic.
Understand the business, its workforce, current processes and HR challenges.
Find the missing, weak, inconsistent or person-dependent processes.
Create the structure, processes, policies, SOPs, dashboards and systems needed.
Help HR and department managers actually adopt the new system.
Digitise repetitive and approval-based workflows where it is worth doing.
Track hiring, attendance, employee cost, performance, training and attrition.
Strengthen the people-management system continuously, not once.
From the GullyHR blog: one on HR in information technology and software, and one on each of the topics this page points to.

Engineers and product staff leave for many reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 min readRead article
What really keeps mobile app and web developers in a small firm: stay conversations, growth paths, fair release rules and a risk sheet an owner can use this month.
6 min readRead article
Simple variable pay structures for product and engineering teams: four options, why individual metrics backfire, a build plan and a one page outline to adapt.
6 min readRead article
How an India head can sort a global parent's HR policies into apply, adapt or replace, write an India addendum with advisers, and keep headquarters on side.
7 min readRead articleMore on the GullyHR blog.
Pay fairly, but also give interesting work, a visible path to lead or auditor, and some say in projects. Ask them regularly what they want. Retention rarely rests on money alone in a scarce field.
Some firms do, but it creates records, valuation and tax questions. Write down the terms clearly and take advice from a qualified professional before offering it, so no one is surprised later.
Be clear on whether they are employees or independent contractors, write the terms down and confirm the legal position with a qualified professional. Agree working hours, access and ownership of code at the start.
The agreement should say so plainly. Most firms assign client work to the firm or the client under written terms. Do not rely on understanding or habit; have the wording checked professionally.
Make sign-off a fixed step before delivery, plan reviewer time in the project plan and let the reviewer say no without blame. Leaders must back them when a date is at risk.
We would ask who holds keys and access, how code ownership is written down and what keeps your scarce engineers. A sensible first project is a role ladder with pay benchmarks and a clean exit checklist. Scope goes into writing before you decide.
All 61 business types in information technology and software · Find another business type
See all HR topics for information technology and software, or another industry.
Tell us what is slowing your team down. We’ll help you find a practical way forward, starting with a conversation.