Full Stack Engineer

About Aetosky Aetosky delivers intelligence products including satellite imagery analysis, RF signal intelligence, and open-source intelligence to government and defence clients across Asia Pacific and the Gulf. About the Role This role builds the product interfaces Aetosky users work in and the service APIs behind them — four product surfaces for four different expert audiences. There are two positions. One of them leans frontend and carries the shared component library until a dedicated frontend engineer joins. Everything runs inside the customer’s own infrastructure, including air-gapped environments. Responsibilities Product Surfaces and APIs • Build product interfaces, and help establish the shared component library they are built on. • Build the service APIs behind those surfaces. • Own usability of complex operational workflows in your surfaces. Reporting and Output • Build reporting and output: evidence packs, incident and case reports, cartographic export, tile and feature delivery, and outbound integration with customer systems. Field Task Management • Build field task management: task assignment, completion, geolocated proof, and offline caching and synchronisation. Quality and Review • Write tests before implementation, and maintain the regression coverage that protects behaviour as surfaces change. • Own the review gate on the services and surfaces you build. Requirements Technical • Solid frontend depth on data-heavy production interfaces — Vue, TypeScript, or equivalent. • Backend depth sufficient to own the services behind the surfaces: async processing, long-running workflows, microservice design, and instrumenting services for observability and distributed tracing. • Real API design experience — Python, Go, Node, or similar. • Test-first practice as a habit rather than a policy complied with: unit, integration, and end-to-end. • Experience with shared design systems — consuming one, and ideally having helped establish one. • Experience building for technical or operational users who are experts in their own field. Engineering Practice • Reviews code they did not write and finds what is wrong with it — correctness and edge cases, not style. • Writes the specification before the implementation and documents the reasoning behind decisions. Preferred • Offline-first or intermittently connected applications. • Map or geospatial interfaces. • Reporting, document generation, or export pipelines. • Having set a frontend standard other engineers built to. … mais