Frequently Asked Questions
Plain answers to what engineering leaders ask us before they hire.
General
We place remote developers and dedicated teams with companies that need engineering capacity. We also help teams modernise legacy systems.
Founders building a first release, engineering leaders growing a team and companies that need to update an older platform.
A SyntecHire developer works on one client only and is supported by us. If the fit is wrong, we replace them. A freelancer usually splits time between clients and carries no replacement cover.
Frontend, backend, mobile, cloud, data and AI, CMS and design. The technologies page lists every stack.
Send a request through the contact page. We reply within two working days with questions and a proposed next step.
Pricing And Contracts
Cost depends on seniority, stack and team size. We give you the monthly rate in writing before you commit.
No. Engagements run month to month. The notice period is stated in the contract.
No. If you decide to stop, you give notice and the engagement ends.
No. You interview the developer before any contract.
Yes. Month-to-month terms let you add or reduce developers as the roadmap changes, within the notice period in the contract.
The developer cost estimate tool gives you a starting range. We confirm the actual figure once we understand the role.
Vetting And Quality
Screening covers a profile review, a communication check, code review on real work, a live technical interview and a practical task.
How a developer works: whether they ask questions early, read existing code before changing it and respond well to review.
Yes. You interview every candidate with your own questions and make the final decision.
Tell us. We first try to fix the problem. If that does not work, we replace the developer and hand over the context.
Yes. Code review on every change is one of our working standards, and developers follow your review process.
Yes. We can assess an existing offshore team against the same criteria we use for our own developers and tell you where the gaps are.
Security And IP
You do. All code and intellectual property is assigned to you by contract.
Before any developer gets access to your code.
In your repository. Developers work in your tools, under your access rules.
You grant access and you can remove it. We ask for the least access the task needs.
Yes. Developers follow your policies for devices, credentials and data. Tell us your requirements at the start.
Working Together
You do. The developer joins your team, takes tasks from your backlog and follows your process.
Yours. Developers work in your repository, your tracker and your chat.
No. One developer works on one client.
We agree working hours and an overlap with your team before the engagement starts.
Work is visible in your tools. Commits, pull requests and tickets are where you already look.
Planned leave is agreed with you in advance. Tell us if you need cover and we will discuss the options.
Legacy Modernisation
Any system that is hard to change, hard to hire for or running on technology that is no longer supported.
Rarely. We prefer to replace a system piece by piece, so each step can be tested and reversed.
That is the aim. We plan changes in small steps with a rollback for each one. We will tell you where we see risk before work starts.
With an assessment of the current system. The legacy risk assessment is a quick first step you can take on your own.
That is common. Developers read the code, write down what they find and document as they go.
Did Not Find Your Answer?
Ask us directly. We reply within two working days.