Cross-Platform Build Engineer Needed
Publicada el 2026-07-17
Descripción de la oferta
Build engineer for check and validation of source code for android 16/17 and windows 64-128 bit. Need to solve RAM memory issues in Operating System and origin of Google Maps tracerouting and map versioning of orginal. Build a script of compiled application for Windows 11. Run tests for all new software in secrecy (UK Act). Build en reason versions for UK and DE countries. No visible passwords in use or building hashed dataset of compiled with CMAKE. Hashed in right order of the guard, triple damage in compile. Independent worker. Corresponce with current development group over Freelancer (unity dancer). Documentation for holder (writer of this advert, annons). UK Law enforced in EULA. English version only. Current priorities • Source code validation – confirm authenticity and integrity across both platforms, then harden the CMake pipeline so every binary is reproducible. • RAM memory issue resolution – track and eliminate leaks or spikes that surface during long-haul tests on Windows 11 and legacy Android devices. • Google Maps tracerouting & versioning – pinpoint the exact map data origin, preserve correct version tags, and document the routing logic used. • EULA enforcement – all deliverables must respect the secrecy provisions of the relevant UK Act; no passwords may ever appear in plain text and every credential must be hashed in the prescribed triple-guard order. Additional scope • Generate an automated Windows 11 build script (Command Line Editor) that compiles, signs, and bundles installers. • Produce two region-specific binaries (UK and DE) from the same source tree. • Coordinate solely through the Freelancer chat with our existing devs in offices. • Deliver a plain English-language technical document that lets any future maintainer reproduce the same results step-by-step. Acceptance criteria 1. Clean build passes on Android 16/17 and Windows 11 x64 x128. 2. Memory profiler shows no unmanaged growth after a 36-hour stress run. 3. Map module as in introduction, correctly reports and records Google-side version IDs. 4. Build pipeline leaves no un-hashed secrets in artifacts, logs, or repos. Tri build as intro. 5. EULA approval on SW start, Info visible on menu at all times with Copyright, and region-specific installers supplied. If you thrive on independent work, know CMake inside-out, and can keep everything under wraps, you’ll fit right in.
Skills
Fuente original: freelancer