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 proptech startup builds software and services for buying, renting, managing or building property, and often runs a field team alongside its engineers. HR must bind two very different groups, and keep up with fast hiring and changing priorities.

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 proptech startup builds a platform or tools for real estate: listings, rentals, property management, brokerage, site monitoring or home services. Engineers, designers and product managers build the app, while sales, listing verification, site visit and customer care teams run the operation on the ground. Property deals are slow and local, so a startup often mixes a modern software culture with a field business that depends on brokers, owners and site visitors. Funding rounds change plans, targets shift, hiring comes in waves and both teams have different pay logic and working hours. Founders often hold HR themselves, and spreadsheets stand in for records. The wider HR for IT and software companies page covers what technology businesses share.
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 PropTech startups. 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.
Engineers and field staff have different hours, pay and status, and friction shows up as mutual blame when a listing is wrong.
People take on whatever is needed, so titles, reporting lines and pay drift apart and promotion rows follow.
A round triggers a hiring rush with thin induction, then a freeze, which leaves new joiners and managers unsure.
Verification staff who rush or are rewarded for volume produce wrong listings, which users notice at once.
Field staff deal with owners and tenants in person, and a rude visit or a leaked contact becomes a complaint.
Offers mention ownership casually without clear terms, and people later disagree about what was promised.
Pivots reset goals, and teams measured on old numbers feel cheated when the plan moves.
A few engineers hold the systems and the knowledge, and a resignation threatens a release.
Start with the topics that matter most here: Organisation Design; Recruitment and Talent Acquisition; Compensation, Payroll and Benefits. Then work through the rest. Each topic is written for information technology and software, not in general.
Structure, reporting lines and who is allowed to decide what.
Requisition to joining, the same way every time.
Salary structure, payroll inputs and a month that closes on time.
How many people, in which roles, by when — and what they will cost.
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.
Policies a manager can apply, and obligations with owners and dates.
Induction, records, incident reporting and follow-through.
Who leaves, when, why — and which of them mattered.
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 PropTech startups business puts in place, in an order that makes each easier. Open any card for the detail.
A one-page chart of roles, levels and reporting lines for product, tech, sales and field, with matching pay bands from compensation benchmarking.
A one-page chart of roles, levels and reporting lines for product, tech, sales and field, with matching pay bands from compensation benchmarking.
Link hiring to the funding plan, so each wave has a start date, an induction and a named manager.
Link hiring to the funding plan, so each wave has a start date, an induction and a named manager. The recruitment process helps stage it.
Verification and listing teams are measured on quality checks as well as counts, using the performance management process.
Verification and listing teams are measured on quality checks as well as counts, using the performance management process.
What field staff may share, how to treat owners and tenants and how to report a complaint.
What field staff may share, how to treat owners and tenants and how to report a complaint.
If options or shares are offered, the terms are stated once in plain words and confirmed with a qualified professional.
If options or shares are offered, the terms are stated once in plain words and confirmed with a qualified professional.
A short design note per core service and a second engineer on each, recorded in the HR documentation process.
A short design note per core service and a second engineer on each, recorded in the HR documentation process.
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.
Pay bands that fit both engineers and field staff without causing envy.
Staged hiring plans linked to funding, with clear roles and interview scorecards.
Goals for quality and speed that survive a change of plan.
Ways to bind field and product teams so they share the same story.
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
A founder's guide to building job grades, titles and billing levels for a growing IT services firm, with a step-by-step method and a grade description outline.
6 min readRead article
How a D2C founder can test a performance marketing hire on real work, ignore weak signals such as dashboard screenshots, and run a fair process.
7 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 articleMore on the GullyHR blog.
Share core policies on conduct and leave, and adapt hours, travel and targets to each group. Keep one set of principles.
Put the role map in writing, review it each quarter and update it before a funding-driven hiring wave.
Put terms in one clear document and avoid casual offers in chats. Confirm structure with a qualified professional.
Use quality checks on listings and visits alongside counts, and sample for errors every week.
Fix targets for a quarter, communicate pivots early and say what happens to incentives when the plan moves.
We would ask how roles and pay are set across tech and field, how hiring waves are planned and how listing errors are traced. A good opening project is a role map plus a staged hiring plan. Scope is written for you to accept or change.
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.