The fastest way to get value from an initial conversation is to describe the workflow, technical bottleneck, data problem, or software architecture issue you want to improve. If the work involves test setups or measurement systems, include that too.
For projects that need a senior technical partner, including software development, automation, data pipeline work, software architecture consulting, RF test automation, or broader technical support:
Include a short description of the problem, your timeline, the kind of systems, tools, equipment, or data involved, and whether you need planning, implementation, or both.
Usually reply within a few days.
You’ll work directly with Jon Robbins, principal of Squalor LLC. Background in RF and test automation, measurement data systems, and technical software leadership for engineering teams—about 26 years of programming and contracting, with RF work since 2006. Based in North Carolina; remote and project-based engagements welcome.
A short note is enough if any of these sound familiar.
Engineers are spending too much time collecting data, moving files around, driving equipment by hand, or maintaining brittle internal processes.
You have a real technical need, but the internal tooling path is fragmented, backlogged, or nonexistent.
You want someone who can assess architecture, build useful systems, and help the team operate more cleanly.
