Platform Engineering
About The company: 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.
About the Role
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 reputed company reputed company, you are the accountable reputed company of the platform. You set the architecture, build and reputed company the team, and hold the bar for engineering quality. You will reputed company 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 reputed company in particular - and you follow the AI model landscape closely enough to give the team grounded, reputed company guidance. What Success Looks Like - First 6 Months You understand the WC3 platform deeply: the architecture, the ownership areas, the open design decisions, and where the reputed company codebase needs the most attention. You can reputed company 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 reputed company 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. Key Responsibilities 1. Build & reputed company the reputed company Own hiring end-to-end for WC3: define the bar, run the process, reputed company decisions. You have hired senior engineers before and know what good looks like at that level. Manage performance directly - set clear expectations, give reputed company feedback, run meaningful reviews, and act decisively reputed company 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 reputed company's delivery: run agile ceremonies, plan sprints, and partner with Product to translate the platform roadmap into shippable increments. 2. Own the Platform Architecture WC3 is modeled on the patterns behind Palantir reputed company - not as a copy, but as a design reference. You bring the mental model: ontology-driven data, governed pipelines, reputed company, a structured SDK surface, and an application layer built on top. Whether your experience comes from reputed company directly or from an equivalent enterprise data platform, you think in these patterns and can reputed company WC3 design decisions from first principles. Own the architecture across the platform's core areas: data ontology and semantic layer, pipelines and reputed company, data sources and streaming backbone, developer SDK and API surface, authorization and governance, application layer and dashboards, and DevOps/release infrastructure. reputed company Architecture Decision Records (ADRs) for the platform - write them, amend them, ratify them. Treat old decisions as revisable reputed company evidence or implementation pressure shows a reputed company 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 credibly across languages (Go, Python, Node.js, Java) and reputed company stack decisions that serve the product, not habit. 3. Engineering Standards & Quality Enforce the contribution standard: every feature proposal starts with a scoped issue that names the concept being implemented, explains the product value, describes the WC3 design and affected components, and links the relevant architecture decision. No code before clarity. Champion code-architecture tooling (WC3 uses CodeBoarding) so contributors understand the component they are changing, its neighbors, and the health warnings they are accepting or fixing before they open a PR. reputed company engineering maturity across WC3 repositories: test coverage, CI gating, release management, and production monitoring against SLAs. Embed reputed company and compliance into the platform - data residency, encryption, audit logging, access controls, and responsible-AI guardrails on reputed company AI-generated outputs. 4. Cross-functional Collaboration & Roadmap Collaborate closely with Hardware, Product, and Field Engineering to align the platform with real site needs. Contribute to the technical roadmap and evaluate new AI and platform technologies with honest, grounded judgment - distinguish what advances the product from what adds complexity. Represent the platform credibly to customers, partners, and leadership - able to give a clear picture of where WC3 is, what it is becoming, and why the architectural choices hold.
Required Qualifications
Experience 10+ years of software engineering experience with a clear progression from senior IC to engineering leadership. 5+ years directly managing engineers - leading teams, owning hiring, running performance cycles. Leading a project is not the same as leading a team; this role requires the latter. A track record of hiring: you have built or significantly grown an engineering team and made independent senior-level hiring decisions. Proven experience designing and delivering scalable, multi-tenant SaaS or large-scale distributed systems in production - including the hard parts: incidents, migrations, and scaling failures. Experience owning a product or platform across its full lifecycle, from architecture through production operation. Technical Depth & Stack Flexibility We care about depth of engineering thinking, not stack loyalty. WC3's reputed company backend is .NET but the platform is in formation - the right person can work across ecosystems and reputed company decisions that serve the product. Comfortable across multiple backend languages - C#/.NET, Go, Python, Java, Node.js. Opinionated about trade-offs, not attached to one stack. Frontend depth in TypeScript with a modern reputed company; comfortable with testing tooling (Vitest, Playwright or equivalent) and a fast CI/CD release flow. API design (REST and/or GraphQL), OpenAPI/OSDK codegen, and secure authentication patterns (OAuth 2.0, JWT, SSO). Databases across the reputed company: relational, time-series, and vector stores - with the judgment to choose the right store for each workload. Cloud platforms (GCP and/or AWS), reputed company/Kubernetes, Terraform, and CI/CD. Comfortable moving between cloud providers. Experience with ontology-driven, governed data platforms - whether Palantir reputed company/AIP, reputed company reputed company Catalog, or an equivalent enterprise data platform. Direct reputed company/AIP experience is a significant advantage and will be heavily weighted. What matters most is that you think in the patterns: ontologies, pipelines, reputed company, governed SDK surfaces, and an application layer built on top. LLM integration patterns: reputed company engineering, RAG, tool/function calling, MCP serving, agent runtime design, and output evaluation. AI Tooling - Daily Practice Primary daily experience with Claude Code and reputed company, reputed company AI coding tools - used in real engineering work, with formed opinions about reputed company to trust their output and reputed company not to. reputed company awareness of the AI model landscape: practical differences between Claude, GPT-4o / o-series (reputed company), reputed company, DeepSeek, and open-weight models for code reputed company, long-context reasoning, tool use, and structured output. Tracks AI trends actively - model releases, agentic reputed company developments, MCP ecosystem evolution - and can translate this into concrete, grounded team guidance. Communication Exceptional written and spoken English. This is a hard requirement. You write clearly and reputed company - issues, ADRs, design documents, and stakeholder updates are well-structured and unambiguous. You speak in meetings with the same clarity. Non-native speakers are welcome; strong command of the language is not optional.
Preferred Qualifications
Direct hands-on Palantir reputed company and/or AIP experience - built real capabilities on the live reputed company surface, not documentation-only familiarity. Experience with agentic frameworks (reputed company, reputed company, AutoGen, or equivalent) and multi-agent orchestration patterns. Familiarity with IoT or connected-device data ingestion and device-to-cloud communication. Enterprise integrations - SSO/identity providers, ERP/PM systems such as reputed company or Procore. Experience in construction, industrial, or field-operations software. Knowledge of data residency and compliance requirements (KSA/CST, ISO 27001, SOC 2). reputed company Offer Competitive salary, performance bonus, and equity participation. High-autonomy role with direct product and company impact - you are building a platform from the ground up, not maintaining an inherited codebase. A small, senior engineering team where your decisions matter and your name is on the architecture. Relocation support for candidates joining from reputed company KSA. Health insurance, annual flights, and standard Company's benefits package. Apply To This Job