Lead Data Engineer (019-878)
Company: Hunt St
Location: Location not specified (Remote)
Type: Full-time
Remote: Yes
Posted: 2026-05-15
About this role
Looking for Philippines-based candidates
Job Role:
Lead Data Engineer
Compensation range:
$4,000-5,000 AUD / Monthly (depending on experience and client discretion)
Engagement type:
Independent Contractor Agreement
Work Schedule:
This role is expected to align with the AU business hours (approx. 9 AM - 5 PM, Monday to Friday) for collaboration, but as a contractor, you'll have flexibility in how you manage your time.
Who We Are:
At Hunt St, we help Australian companies hire top remote talent in the Philippines. For this role, you will be engaged directly by the client as an independent contractor. We are not an outsourcing agency. All of our roles are 100% remote so you'll be able to work from home.
Who The Client Is:
Our client is an independent technology consulting firm with over 15 years of experience helping organizations improve their systems, data, and workflows across industries such as manufacturing, healthcare, research, and laboratory environments. Rather than selling software, they provide unbiased consulting focused on system implementations, data migration, workflow optimization, and regulatory compliance. Their collaborative approach helps businesses modernize legacy systems, improve operational efficiency, and maximize the value of their existing technology so they can scale with confidence.
Role Overview:
This role is central to the successful design, build, and ongoing governance of a DataHub. The Lead Data Engineer acts as the primary interface between offshore and onshore teams, setting architectural direction and engineering standards while ensuring consistent code quality and adherence to agreed design principles. During the build phase, the role oversees architecture decisions, coordinates with IT teams on core data layer delivery, and approves work prior to UAT release.
As delivery transitions from build to run, the role shifts into operational ownership—managing DataHu...