CTO & Technical Co-Founder

TRALKAN is a Swiss company building SENTINEL Command, a command and coordination platform for autonomous aerial emergency response. We work with the organisations that respond when something is on fire, someone is missing, or infrastructure fails.

You'd be joining as the first technical hire and co-founder, working alongside a founding team that is already contributing part-time toward the same funding milestone — this isn't a leap of faith into an empty room.

Sentinel Command exists today as a working software platform, validated through progressively integrated operational use cases. You'd own the technical architecture required to take it from its current state toward coordinating real drones and ground robots in the field — leading the transition from software prototype toward increasingly integrated operational validation.

• Assess the current platform and define the technical path toward operational validation
• Develop core workflows for operational requests, approvals, asset coordination and traceability
• Design modular interfaces for drones, robots, sensors and external systems
• Ensure reliable telemetry, video and operational state management under poor connectivity
• Establish standards for security, access control, testing, deployment and observability
• Assess and integrate AI assistance with clear human oversight
• Engage prospective users to validate assumptions and translate operational needs
• Recruit and mentor the initial engineering team as we scale post-funding

• Demonstrated track record shipping software used by real customers or operational teams
• Strong backend and systems engineering: APIs, event-driven workflows, databases, real-time data
• Experience integrating software with devices, robotics or industrial systems
• Full-stack capability with direct involvement in implementation and debugging
• Sound judgment on reliability, security and failure handling
• Product mindset: scope reduction, assumption testing, clear technical trade-off communication
• Ability to share ownership and navigate uncertainty with founding teams
• Professional English proficiency

• Python, TypeScript, React or Next.js experience
• Familiarity with autonomous-systems middleware, flight-control integration or manufacturer SDKs
• Geospatial applications, video streaming, edge computing or disconnected operations
• AI model evaluation and workflow integration experience
• Emergency response, critical infrastructure, robotics or defence sector exposure
• Regulatory or certification experience relevant to drone operations (EASA, BVLOS, U-space)
• Field trials or early customer deployment experience
• German language proficiency — genuinely useful given the operational stakeholders (fire services, civil protection, municipalities) we work with in Switzerland

We're upfront that this is a two-phase arrangement, and we'd rather you know that going in than discover a mismatch later.

Phase 1 — pre-financing (current stage): part-time or parallel commitment, structured around your availability — the same arrangement the rest of the founding team operates under today. No salary during this phase, but equity vesting begins on your start date, not on funding close.

Phase 2 — post-financing: transition to full-time at the compensation listed below, with continued vesting under the same schedule agreed in Phase 1 — no re-negotiation required to convert.

Co-founder equity in the 12–18% range, vesting over 4 years with a 1-year cliff. Where you land in that range depends on timing of commitment, scope of ownership, and risk assumed pre-funding — we'll walk through the specific reasoning with you directly. Standard double-trigger acceleration applies on acquisition or founder departure (negotiable). Founder equity is subject to the same vesting logic — this is built with symmetric skin in the game, not just yours.

1. Application review — We read every application. You hear back either way, within 5 working days.
2. First conversation — 45 minutes with the founder. What you have built, what you want to build.
3. Technical conversation or case — Real work, scoped to a couple of hours. Never unpaid production work.
4. Final conversation — Scope, expectations, compensation, and your questions.
5. Offer — Written, with the numbers spelled out.