About FuturByte
A small operation, deliberately. The assessment is the product.
FuturByte places senior software developers with US engineering teams. We are a small operation by design: the assessment is the product, and assessment does not scale the way forwarding CVs does.
The reason this site is built the way it is, with published government wage data on every page and the sources cited, is that the market we work in is full of confident unsourced numbers. We would rather publish figures you can check, including when they are inconvenient for us, than repeat the salary estimates that circulate with no origin.
Where we think hiring locally would serve you better, we say so. That costs us engagements and it is the only way this works as a long relationship rather than a transaction.
What we will not do
- Send you a shortlist with no stated reservations, because that is assembly rather than assessment.
- Quote a salary figure for a specific technology, because no such official figure exists and anyone who quotes one has invented it.
- Recommend a team size larger than your review capacity can absorb, however much budget exists.
- Tell you an engagement is the answer when the problem is architectural or organisational.
- Push a candidate you are unsure about. A developer somebody was talked into hiring rarely works out.
How to use this site
Start from the technology if you know it
Each technology page covers what the technology actually is, the part that separates a senior developer from a mid-level one, seven things worth testing in an interview with what a strong answer and a warning sign sound like, six warning signs in an inherited codebase, what each level can be left to own, how the work is usually scoped, and the published US wage data for the occupation it belongs to. You can use all of that whether or not you ever talk to us.
Start from the market if you know where
Each location page covers the published employment and wage figures across every technical occupation in that metro, how the market has moved across the last three published releases, the employer payroll cost of a local seat using statutory rates, the industries that shape who is available, and where hiring plans in that market tend to go wrong.
Use the occupation, not the technology, to set a band
There is no official wage figure for any framework or language. There is one for the occupation, and every technology page states which occupation it belongs to so the figures can be checked against the right release. A band built from an invented technology-specific number is wrong before the search starts.
Read the location quotient, not just the median
The median tells you what a role costs. The location quotient tells you whether the people exist. A high median in a market with a low quotient means a long search rather than an expensive one, and those are different problems with different answers.
Check the dates
Every figure on this site carries its source and the date it was read. If you are reading this long after that date, the numbers have moved and the relationships between them probably have not.
How we are paid
Commercial terms are agreed in writing before an engagement begins and depend on whether the work is a single placement or ongoing capacity. We do not publish a rate card, because a number without the context of the role and the market is the kind of unsourced figure this site exists to avoid.
Where our data comes from
Every wage and employment figure on this site comes from the US Bureau of Labor Statistics Occupational Employment and Wage Statistics, May 2025, read on 25 September 2026. Release and support information for technologies comes from public release data, read the same day. Employer payroll tax figures come from the Social Security Administration's published contribution and benefit base. Where a figure is an estimate or a judgement rather than a published number, the page says so.
Frequently asked questions
How large is FuturByte?
Small, deliberately. The assessment is what you are paying for and it does not scale the way volume recruitment does. If we grow past the point where we can assess properly, the thing you are buying stops existing.
Where are you based?
We work with US teams and our developers are outside the US, scheduled around a committed overlap with your hours. Where a role genuinely needs presence in a specific city we will tell you rather than pretend otherwise.
Why publish government data rather than your own figures?
Because you can check it. Most salary figures in this market have no source and cannot be verified. Publishing the release, the occupation code and the date we read it means our numbers can be held to a standard rather than taken on trust.
Do you have case studies?
We will talk you through relevant work in a conversation, with the client's permission. We do not publish claims about outcomes we cannot evidence, which is why this site has no statistics about our own performance.
What sectors do you work in?
Mostly product engineering across software, commerce and services. Where a sector carries obligations we do not have experience with, we will say so rather than learn on your project.
How do we start?
Describe the work and your team's current shape. That is enough for a first conversation, and the conversation is free whether or not it leads anywhere.