We do not outsource trust.
We do not train people to read scripts.
We do not lower the bar to scale.
This page defines the standard required to represent Open Source Security.
Most people are not a fit. That is intentional.
An OSS Engineer is a senior, customer-facing security professional responsible for deploying, explaining, and supporting real-world network security for non-technical users.
This role sits at the intersection of deep technical mastery, clear human communication, and personal accountability.
OSS Engineers are not tier-1 support. They are not call-center technicians. They are not learning on the job. They are trusted to represent OSS directly to customers.
OSS Engineers are expected to arrive with deep, practical experience in all of the following areas. This is not a training role.
OSS touches nearly every security subsystem OPNsense provides. Engineers must understand how these systems interact, not just how to navigate the GUI.
Concrete example: You should be able to troubleshoot a WireGuard handshake failure without searching for the answer. You should understand why "Disable Routes" must be checked in OPNsense WireGuard peer configuration. If these references mean nothing to you, this role is not a fit.
Technical knowledge alone is not sufficient. OSS Engineers must be able to:
| ✓ | Explain complex security concepts to non-technical users |
| ✓ | Communicate calmly and clearly under pressure |
| ✓ | Guide customers through decisions without overselling |
| ✓ | Set and enforce boundaries when necessary |
| ✓ | Earn trust quickly and maintain it over time |
You are often the most technically capable person a customer has ever spoken to. You are also responsible for making them feel confident, not overwhelmed.
| Aspect | Structure |
|---|---|
| Location | Fully remote |
| Interaction | Customer-facing video consultations |
| Compensation | Paid per engagement |
| Hours | No minimum, no maximum |
| Schedule | Self-managed availability |
Consultations are typically 25-30 minutes and focus on configuration, validation, and education. This role is designed for experienced professionals who value autonomy and responsibility over hierarchy.
OSS Engineers are compensated per consultation. This is a 1099 contractor role.
| What Exists | What Does Not Exist |
|---|---|
| Per-consultation payment | Guaranteed hours |
| Regional leadership opportunities | Required schedules |
| Higher compensation for team oversight | Quotas or sales commissions |
At launch, OSS operates exclusively within the United States.
OSS is intentionally expanding region by region. Engineers who establish strong local presence may be offered responsibility for defined geographic regions.
Regional ownership: An engineer in Texas owns Texas. Customers in that region route to you. You build the relationship. You maintain the standard.
To be explicit, this role is not:
| X | Entry-level |
| X | A helpdesk position |
| X | A sales job |
| X | A full-time employment requirement |
| X | A path for learning networking fundamentals |
If you are still asking what a VLAN is, this role is not for you.
Home networks are now critical infrastructure.
OSS exists because this gap has become untenable. The mission is to make enterprise-grade network security accessible to people who will never become network engineers.
If you read this page and thought:
"Yes. This is already how I work."
Then you may be a fit for OSS.
This page exists permanently because OSS is always looking for the right people. There is no rush, and there is no pressure.
The bar is the bar.
If you believe you meet the standard described on this page, introduce yourself.
[email protected]No formal application. No HR portal. Just a direct conversation.