Technical Leader – Platform Architecture

1. POSITION OVERVIEW

The Technical Leader – Platform Architecture is responsible for defining, designing, and governing the overall technical architecture of the GASCO Platform. This platform is a multi-sided, large-scale system that enables GASCO to operate its internal devices fleet, integrate external partners, and provide a controlled marketplace for third-party devices and pilot participation.

The position plays a critical role in ensuring that the platform is scalable, secure, compliant, and sustainable for long-term business growth.

2. CORE TECHNICAL COMPETENCIES

2.1 Platform Architecture

• Design and governance of:
  • Multi-tenant architecture
  • Multi-role access models (Platform Owner, Partner, Public User)
• Definition and enforcement of:
  • Modular or microservices-based architectures
  • Domain boundaries and ownership
  • API contracts and integration standards

2.2 Core Platform Systems

Demonstrated experience with most of the following systems is required:

• Booking, mission management, or scheduling engines
• Workflow and approval management systems
• Pricing, billing, and revenue-sharing mechanisms
• Identity and Access Management (RBAC, ABAC)
• Audit logging and system traceability

2.3 Data, Scalability, and Reliability

• Design and operation of systems supporting:
  • High concurrency
  • Large-scale data processing
• Strong knowledge of:
  • Relational and non-relational databases
  • Event-driven architecture
• Practical experience addressing:
  • Performance optimization
  • Data consistency challenges
  • Fault tolerance and system resilience

2.4 Cloud and DevOps

• Experience deploying and operating platforms on:
  • AWS, Azure, or Google Cloud Platform
• Proficiency in:
  • CI/CD pipelines
  • Containerization and orchestration
• Understanding of:
  • Cost management
  • Observability and monitoring
  • Incident response and system reliability

3. LEADERSHIP RESPONSIBILITIES

3.1 Technical Governance

• Define and maintain architectural principles, standards, and best practices.
• Review and approve critical technical and architectural decisions.
• Ensure consistency and quality across all platform components.

3.2 Cross-functional Collaboration

• Act as the primary technical counterpart to:
  • Business leadership
  • Operations teams
  • Product management
• Translate business and operational requirements into sound technical solutions.
• Provide technical guidance to prevent misalignment between business objectives and platform architecture.

3.3 Accountability

• Assume end-to-end responsibility for:
  • Platform architectural integrity
  • Long-term scalability and maintainability
  • Technical risks impacting platform operations

4. PREFERRED QUALIFICATIONS

• Experience in one or more of the following domains:
  • Aviation, Devices, or aerospace systems
  • IoT or real-time data processing platforms
  • GIS or location-based systems
• Prior collaboration with executive leadership on:
  • Technology strategy
  • Platform roadmap planning
• Experience in designing systems subject to:
  • Regulatory compliance
  • Safety and governance requirements

 REQUIRED EXPERIENCE AND QUALIFICATIONS

1. Professional Experience

• Minimum 15 years of experience in software system development.
• At least 7 years in senior technical leadership roles, such as:
  • Technical Leader
  • Chief / Principal Architect
  • Engineering Manager with primary technical accountability
• Proven hands-on involvement in building large-scale systems, not limited to operational maintenance or support.

2. Experience with Comparable Platforms (Mandatory)

Candidates must demonstrate direct experience in designing or building platform-based systems with characteristics comparable to the GASCO Platform, including but not limited to:

• Marketplace Platforms
  • Ride-hailing, accommodation-sharing, or B2B/B2C marketplaces
• Asset or Resource Sharing Platforms
  • Fleet management systems
  • Equipment or resource scheduling platforms
• Logistics or Transportation Platforms
  • Dispatching and scheduling systems
  • Resource allocation and optimization platforms
• Ecosystem-driven Platforms
  • Partner onboarding and management
  • Revenue-sharing models
  • SLA, KPI, and governance frameworks

Preference will be given to candidates who have:

• Participated in platform development from initial design through MVP and scaling phases
• Held responsibility for architectural decision-making rather than execution alone