Roles we fill · Technology
Technology
Build it, integrate it, support it, keep it running.
What it covers
Technical roles cover product work, internal tooling, integrations, support and the data work that sits alongside them. They are the roles where a bad hire costs the most, which is why the screening is heaviest here.
What they do
- Build and maintain product features
- Integrate third-party systems and APIs
- Fix bugs and work a maintenance backlog
- QA and release testing
- IT support and internal tooling
- Data analysis, dashboards and reporting
- UX and interface design
- Configure and customise CRM platforms
Titles we hire for
- Software Developer
- Web Developer
- Mobile App Developer
- Data Analyst
- IT Support Specialist
- UX/UI Designer
- CRM Design
- Project Manager
Working remotely
Standard practice, higher screening burden
Software has been distributed for two decades; nothing about the work resists it. What does change remotely is verification — you cannot read the room, so the technical interview and the competency review carry more weight. That is the same screening every candidate goes through, applied to a harder-to-fake skill set.
7–9 hours of overlap with a 9–6 New York day
- Mexico City 8h
- Bogotá 9h
- Lima 9h
- Santiago 8h
- Buenos Aires 7h
- São Paulo 7h
Each bar is that city's own 9am–6pm, placed on New York time. Based on standard UTC offsets; daylight saving shifts some rows by an hour.
Choosing a level
Which level do you actually need?
The same three rates apply across every discipline. What changes is how much judgement the work needs.
- Entry $7–10/hr
Working defined tickets with review. Good where you have someone senior to review their work.
- Mid $11–15/hr
Owning features end to end and making implementation calls independently.
- Expert $16+/hr
Architecture, technical direction, and reviewing everyone else’s work.
Guidance, not a quote — the level is agreed on the call. Full pricing
Before the call
What to have ready.
The search starts on the discovery call. These four answers are what make it a good one.
- 01 Your stack, and which parts they will actually touch
- 02 How repository and production access will be handled
- 03 Who reviews their work — this decides the level you need
- 04 How much of the work is synchronous versus async
Hiring for technology?
Twenty minutes on the role and the level. Candidates to interview inside ten days.