Integrations engineer
A system is only useful when what it does lands in the software the business already uses. You build those connections and make them safe to rerun: the record that is created, the booking that is made, the invoice that is drafted.
The work
- Build and maintain connections to CRM, scheduling, messaging and accounting software through their APIs and webhooks.
- Map a client’s fields and rules, and write them down so the mapping can be checked.
- Handle the failures: retries, duplicates, expired access, a service that is down.
- Set everything up in the client’s own accounts, with the least access that works.
What you bring
- Experience with REST APIs, webhooks and OAuth in production.
- Hands-on time inside at least one CRM or accounting system.
- A habit of logging what happened, so a miss can be traced.
How the contract works
- A written scope
- Every project starts from a written scope: what is to be delivered and by when.
- Your rate, by the hour
- You are paid by the hour at a rate agreed before you start, and you invoice for the hours worked.
- Your own business
- You are an independent contractor. You use your own tools, decide how the work gets done, and look after your own taxes.
- Project by project
- A contract covers one project. It is not a promise of further work, and you are free to work for others.
- Client data stays put
- Work happens in the client’s own accounts, with the least access the task needs, under a confidentiality agreement.