The work

You will be handed RF and electromagnetic engineering problems and asked to do two things well: produce a rigorous solution yourself, and judge whether someone else's solution is actually correct. Tasks range across link budgets and propagation modeling, antenna and array design, impedance matching and microwave circuit analysis, EMC/EMI mitigation, radar and sensing system trade-offs, and interpretation of simulation output from HFSS, CST, COMSOL, ADS or MATLAB. Expect to write out derivations, state your assumptions explicitly, flag where a stated specification is internally inconsistent, and explain why a plausible-sounding answer fails a sanity check on units, physics, or realizable hardware.

Much of this is evaluation work: reviewing a proposed technical approach, identifying the specific step where reasoning breaks, and articulating the correction at a level another RF engineer would accept. The client's interest is in expert judgment that survives scrutiny, so partially-right answers with hidden assumptions are worse than useless. Written clarity matters as much as being right — a correct number with no traceable reasoning cannot be used.

What the screen looks for

  • Hands-on industry or lab experience applying RF/EM principles to real systems, not just coursework familiarity.
  • Degree in electrical/electronics engineering, RF, electromagnetics or a closely related field; advanced degrees are preferred but not required.
  • Depth in at least one named area — arrays and beamforming, mmWave, channel modeling, EMC, RF measurement — that holds up under follow-up questioning.
  • Willingness to say "the specification is underdetermined" rather than inventing a number.

Logistics

Fully remote and asynchronous. Short-term engagement, typically part-time hours arranged around your own schedule; throughput expectations are set per project batch rather than by fixed shifts. Pay of $80–95/hr reflects rates observed on this listing and can vary by task type, assessed depth, and project stage — treat it as observed, not guaranteed. Expect a technical screen with domain questions before any task access.