{"id":2473,"date":"2026-05-14T10:28:23","date_gmt":"2026-05-14T10:28:23","guid":{"rendered":"https:\/\/theemcnews.co.uk\/?post_type=job_listing&p=2473"},"modified":"2026-05-14T10:28:24","modified_gmt":"2026-05-14T10:28:24","slug":"principal-rf-engineer-12","status":"publish","type":"job_listing","link":"https:\/\/theemcnews.co.uk\/index.php\/job\/principal-rf-engineer-12\/","title":{"rendered":"Principal RF Engineer"},"content":{"rendered":"
\n

About the job<\/h2>\n<\/div>\n

Principal RF Engineer<\/strong><\/p>\n

You will own the mathematical and physical foundations of one of the few operational commercial space-based RF geolocation systems in active customer use today. The core problem: estimating the position of RF emitters using time difference of arrival (TDOA), frequency difference of arrival (FDOA), and angle of arrival (AoA) measurements collected by a constellation of low Earth orbit (LEO) satellites. You will formulate estimation problems, develop and validate algorithms, characterize error sources, and drive performance improvements across all three measurement domains.<\/p>\n

You will inherit a working production geolocation system. This is not a greenfield research project. The algorithms exist, they run, and they produce results for real customers. Your job is to understand the existing system deeply, identify where performance is limited, and systematically improve it. Over time you will also extend the system with new measurement types and capabilities as mission requirements evolve.<\/p>\n

This is a hands-on, iterative role operating on real-world data with all its imperfections. Calibration is incomplete. Truth data is sparse. Operational constraints require pragmatic engineering tradeoffs. You will spend significant time examining real geolocation outputs, diagnosing performance issues, refining algorithms based on what the data shows, and shipping incremental improvements. The work cycle is not “design an algorithm and hand it off.” It is: analyze outputs, identify the limiting error source, develop or refine an algorithmic solution, validate it against data, and repeat. You will work alongside software engineers who handle production implementation and infrastructure; your role is to ensure the algorithms are correct, well-understood, and continuously improving.<\/p>\n

You will write code daily. Python is the primary tool for prototyping, simulation, data analysis, and algorithm validation. This is not a pure research position; the expectation is that you are building, testing, and iterating on working code, not producing papers.<\/p>\n

Key Responsibilities<\/strong><\/p>\n