Boxxdocks: Strengthening the Next Generation Tracking Platform
How a B2B supply chain platform hired a React Native Consultant, a React Native Engineer and a Data Migration Consultant.
Challenge
BoxxDocks tracks physical assets for businesses in logistics, manufacturing, retail, the public sector and defence - where things are, who holds them, and what has been done to them. The platform has two halves. Orbit is the web product where managers see dashboards and pull reports. The mobile app is where the data actually enters the system, used by people in warehouses, on sites and in vehicles, often on rugged handheld devices with built-in scanners rather than on phones. That division sets the engineering priorities. The app has to work on whatever hardware a worker has, often without a reliable connection, and anything it captures incorrectly propagates straight into the reporting built on top of it. The reporting, in turn, is only as good as the data model beneath it. Both halves needed specialist attention, at different points, and neither need justified a permanent hire.
Three requests went in across twenty months, each for a different specialism. The first was a React Native engineer for the mobile application: eight years of JavaScript with the most recent two in TypeScript, React Native and React with Redux and React Query, REST and GraphQL interfaces, and established testing and CI practice. Part of that work was integrating the app with hardware scanning devices, which is the point at which React Native stops being a cross-platform convenience and starts requiring native work against a manufacturer’s SDK. The second was a data migration consultant: six years of production ETL and warehousing across Azure, AWS and GCP, including migrating legacy cube systems to Azure Synapse, working in Python, Spark, Airflow, SQL and Power BI. The third came later - a React Native consultant to audit the mobile application, with seven years of cross-platform development and team leadership behind them, TypeScript, Expo, Firebase and native module work in Swift and Kotlin, brought in to assess rather than to build.
BoxxDocks has a CEO, a CTO and its own engineering team, so as a part of screening everyone put forward was assessed by people who could judge them properly. The engineering request needed native integration against device SDKs rather than screen work alone, since an app that talks to scanning hardware is a different proposition from one that does not. The migration request needed someone who had moved production data without interrupting the reporting that depends on it. The audit request, in its turn, needed someone senior enough to review a mature application and report on it constructively, which is as much a matter of manner as of skill. The first engagement was confirmed 30 hours after the first request opened.
Outcome
BoxxDocks has always opened a request when a particular skill was needed, used it for as long as needed - three times, across three disciplines. The value is in the account staying open rather than in anyone staying engaged.
- Three requests, each for a different specialism, with the first matched in 30 hours.
- Mobile engineering including hardware scanner integration, a data migration behind the reporting layer, and later an independent audit of the application.
- Specialist capacity alongside an existing CEO, CTO and engineering team.
- Twenty months of an open account, drawn on when a particular skill was required.
A Strategic, Multi-Phase Hiring Approach
Phase: Request
Three requests opened months apart, each for a different discipline: a React Native engineer for the mobile application, a data migration consultant for the reporting layer, and later a React Native consultant to audit the application.
Phase: Matching
The engineering shortlist of 3 was screened against production work in the same stack and towards native integration against device hardware rather than screens alone, the migration shortlist of 3 towards production data moved without interrupting the analytics built on it, and the audit shortlist of 3 towards engineers senior enough to review a mature application and say something useful about it.
Phase: Interviews
The CEO, the CTO and members of the existing engineering team all took part, with the first engagement confirmed 30 hours after the first request opened.
Phase: Engagement
Each engagement opened with part-time monthly workload and hour caps set, daily hour tracker, and monthly reports with detailed breakdown of hours committed.
Phase: Support
The account stayed open across twenty months and was used when a specialism was needed, with all changes to workload, hour caps, or extra hours, confirmed from the account.
