Engineering Manager - Data Platform

The company is a construction-tech company headquartered in AL Khobar,KSA, building the connected-worker platform for large-scale construction and industrial sites. Our hardware - smart helmets, anchors, and gateways - feeds a real-time SaaS platform that gives site teams worker location, safety compliance, automated mustering, and productivity analytics. We operate across major projects in the GCC and are growing fast. We are building for the long term.

The company is a construction-tech company headquartered in AL Khobar,KSA, building the connected-worker platform for large-scale construction and industrial sites. Our hardware - smart helmets, anchors, and gateways - feeds a real-time SaaS platform that gives site teams worker location, safety compliance, automated mustering, and productivity analytics. We operate across major projects in the GCC and are growing fast. We are building for the long term.

WC3 is our 3.0 platform - the SaaS core that connects IoT hardware to customer workflows. It is pre-launch, in active formation, and deliberately modeled on the architectural patterns behind ontology-driven, pipeline-first, and built to serve AI agents as first-class consumers alongside human users.

As WC3 Squad Lead, you are the accountable owner of the platform. You set the architecture, build and lead the team, and hold the bar for engineering quality. You will lead a team of Senior engineers - you will be joining a small, senior group with high autonomy and direct product impact.

This is a senior engineering leadership role. You have led teams before: hired engineers, managed performance, built culture, and earned trust at both the technical and organizational level. You think in systems and org design, not just code. You are also a serious, daily user of AI coding tools
- Claude Code and Codex in particular - and you follow the AI model landscape closely enough to give the team grounded, current guidance.

• You understand the WC3 platform deeply: the architecture, the ownership areas, the open design decisions, and where the current codebase needs the most attention. You can lead an architecture walkthrough for any platform area.
• You have run at least one meaningful hiring process, made a hiring decision, and the team is measurably stronger than when you joined.
• The contribution standard is operational: engineers open structured issues, scope their changes to the right components, and submit PRs that are small enough to review and explicit enough to teach the platform.
• The AIP layer - the agent runtime, MCP surface, and AI-powered product features - has a clear technical direction with an accepted architecture decision behind it.
• Stakeholders trust you as the person who owns the platform - not just its code, but its direction.

• Own hiring end-to-end for WC3: define the bar, run the process, make decisions. You have hired senior engineers before and know what good looks like at that level.
• Manage performance directly - set clear expectations, give continuous feedback, run meaningful reviews, and act decisively when someone is not meeting the bar.
• Build a high-ownership, contribution-first engineering culture. WC3 uses an earned ownership model: authority over platform areas accrues through demonstrated contribution, not seniority or title. You run this model and ratify ownership promotions.
• Mentor engineers at every level - from onboarding new contributors to developing senior engineers toward platform ownership. Your track record includes engineers who grew significantly under your leadership.
• Own the squad's delivery: run agile ceremonies, plan sprints, and partner with Product to translate the platform roadmap into shippable increments.

WC3 is modeled on the patterns behind Palantir Foundry - not as a copy, but as a design reference. You bring the mental model: ontology-driven data, governed pipelines, lineage, a structured SDK surface, and an application layer built on top. Whether your experience comes from Foundry directly or from an equivalent enterprise data platform, you think in these patterns and can make WC3 design decisions from first principles.

• Own the architecture across the platform's core areas: data ontology and semantic layer, pipelines and lineage, data sources and streaming backbone, developer SDK and API surface, authorization and governance, application layer and dashboards, and Dev Ops/release infrastructure.
• Lead Architecture Decision Records (ADRs) for the platform - write them, amend them, ratify them. Treat old decisions as revisable when evidence or implementation pressure shows a better path.
• Design for high availability, low latency, and horizontal scalability. Own data modeling across relational, time-series, and vector stores.
• Drive the C#/.NET backend while remaining genuinely flexible about the stack. WC3 is pre-launch - you can reason…