... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
... · Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs · Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns · Experience ...
Ribbon Sbc information
See salary details
$394.23 - $547.20
9% of jobs
$547.20 - $700.17
16% of jobs
$704.67 is the 25th percentile. Wages below this are outliers.
$700.17 - $853.15
18% of jobs
The median wage is $909.50 / hr.
$853.15 - $1K
20% of jobs
$1.1K is the 75th percentile. Wages above this are outliers.
$1K - $1.2K
14% of jobs
$1.2K - $1.3K
9% of jobs
$1.3K - $1.5K
9% of jobs
$1.5K - $1.6K
3% of jobs
$1.6K - $1.8K
1% of jobs
$1.8K - $1.9K
2% of jobs
$1.9K - $2.1K
0% of jobs
$394
$1.1K
$2.1K
How much do ribbon sbc jobs pay per week?
What is a Ribbon SBC?
What are the key skills and qualifications needed to thrive as a Ribbon SBC engineer?
What are some typical challenges faced by professionals working with Ribbon SBC systems, and how can they overcome them?
What is the difference between Ribbon Sbc vs VoIP Engineer?
| Aspect | Ribbon Sbc | VoIP Engineer |
|---|---|---|
| Required Credentials | Networking certifications, SIP, VoIP knowledge | Networking certifications, VoIP, SIP expertise |
| Work Environment | Telecommunications infrastructure, data centers | IT departments, telecom companies |
| Industry Usage | Telecom service providers, enterprise networks | Telecom, IT, VoIP service providers |
Ribbon Sbc specialists focus on deploying and managing Session Border Controllers for secure VoIP traffic, while VoIP Engineers design, implement, and troubleshoot VoIP systems. Both roles require similar certifications and work in telecom environments, but Ribbon Sbc roles are more specialized in network security and session management.
What cities are hiring for Ribbon Sbc jobs?
Cities with the most Ribbon Sbc job openings:
What states have the most Ribbon Sbc jobs?
States with the most job openings for Ribbon Sbc jobs include:
What job categories do people searching Ribbon Sbc jobs look for?
The top searched job categories for Ribbon Sbc jobs are:

Full-time
Posted 10 days ago
Job description
Provides day‑to‑day operational support and deep telecom expertise across SBC‑centric voice environments. Responsible for monitoring, incident triage, SBC troubleshooting, and carrier coordination in support of a hybrid contact center stack (Genesys today, Amazon Connect migration underway). Works from established runbooks, participates in incident bridges, and escalates issues appropriately
Why this role exists
To provide the day‑to‑day operational backbone for a combined telecom security and incident response program - ensuring stable operations across SBC‑centric voice environments while the contact center runs in a hybrid state (Genesys now, Amazon Connect migration underway), with disciplined incident response and change execution.
Key Responsibilities:
· Monitor and triage telecom incidents impacting public‑facing voice platforms, including SBC health and call routing behavior
· Investigate issues using CDRs, SBC logs, SIP traces, and vendor/carrier feedback
· Support STIR/SHAKEN operational behaviors, including signing success/failure, exceptions, unsigned calls, and carrier rejections
· Execute approved operational changes using defined runbooks and change windows (no ad‑hoc architecture changes)
· Coordinate with carriers, vendors, and internal engineering/SRE teams during incidents
· Participate in incident bridges and support escalation workflows
· Maintain runbooks/SOPs and operational documentation/audit artifacts; contribute to post‑incident RCA documentation
Required Qualifications:
· 5–7+ years of VoIP/telecom operations experience in enterprise environments
· Strong experience supporting SBC‑based voice services, including SIP call flows, routing, and log analysis (CDR/SBC/SIP/session logs)
· Experience with incident management processes (ITSM/ticketing, escalations, documentation)
· Working familiarity with contact center call flows and platforms (Genesys and/or Amazon Connect
Preferred Qualifications:
· Experience in BFS or regulated industries with strict change/audit requirements
· Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs
· Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns
· Experience supporting hybrid contact center environments during migrations (on‑prem to cloud)
· Experience acting as a telecom architect or L3 support
· Exposure to enterprise monitoring and observability tools
- Experience working in BFS Sector
About Long Finch Technologies
Sourced by ZipRecruiter
Industry
It services
Company size
51 - 200 Employees
Headquarters location
Edison, NJ, US
Year founded
2010