When you join Cubic, you become part of a company that creates and delivers technology solutions in transportation to make people’s lives easier by simplifying their daily journeys, and defense capabilities to help promote mission success and safety for those who serve their nation. Led by our talented teams around the world, Cubic is committed to solving global issues through innovation and service to our customers and partners.
We have a top-tier portfolio of businesses, including Cubic Transportation Systems (CTS) and Cubic Defense (CD). Explore more on Cubic.com.
Service Operations · Product & Platform Engineering for NOC and SOC
Reports to: NOC Senior Manager
Dotted line to: SOC Manager
Work pattern: Shifts, with an on-call during weekends as technical expert for P1/P2 incidents
Experience: 8+ years in IT infrastructure, application support or operations; internal candidates with hands-on Cubic product experience preferred
Role Purpose
The Principal Operations Engineer is the product and platform expert who links how Cubic's products are built with how they are run. Involved from design and development through implementation and maintenance, you stay current on our products and bring that knowledge to the NOC and SOC to keep services available, performing well and secure, and to stop problems from coming back.
Your technical skills are broad across Windows, Linux, Azure, networking, Java applications and Microsoft SQL. Your depth is in Cubic's own products, applications and OT/IoT devices. You will serve the NOC and SOC equally, working alongside the teams that run day-to-day operations rather than duplicating them.
This role makes other teams more effective on Cubic products. It does not duplicate their work.
Team
They own
This role's contribution
Product, development & delivery
Building and releasing products
Design input; supportability, monitoring, security and access requirements; readiness sign-off
Change management
Change process and approvals
Technical review of changes affecting portfolio products and the Azure/Wintel estate
Patch pod
Patching
Guidance on taking vulnerability fixes into production: impact, testing, rollback, readiness
Automation pod
Building automation
Identifies and specifies automation for products; validates results
Observability team
Monitoring tools and dashboards
Defines what healthy looks like for each product
Access management pod
Provisioning and access reviews
Defines the least-privilege access model for each product
Monitoring, triage, restoring service
Top escalation for product, Java and SQL issues; runbooks and known errors
Detection, investigation, forensics
Product and infrastructure context; impact of containment options
Running incidents and war rooms
Technical expert for portfolio products
Problem management
Problem process and governance
Technical root-cause analysis and fix delivery for portfolio products
Service desk
User contact
Product knowledge articles
Out of scope: alert triage, incident command, patch deployment, building automation, administering monitoring tools, and provisioning access.
Success Measures
Targets are baselined during the first 60–90 days. Individual measures cover work this role controls; shared measures cover outcomes this role influences alongside other teams. Suggested weighting: individual 60%, shared 40%.
Area
KPI
Target
Type
Product lifecycle
Portfolio releases and major changes with design and readiness review
100%
Individual
P1/P2 incidents within 30 days of go-live caused by readiness gaps
0
Individual
Product knowledge articles updated after a release
Within 10 business days
Individual
Availability & performance
Portfolio services meeting availability and performance targets
Meets contract/service target monthly
Shared
Time to engage on P1/P2 when called
P1 ≤ 15 min · P2 ≤ 30 min
Individual
Time to restore on P1/P2 incidents engaged on
20% better than baseline within 2 quarters
Shared
Problem resolution contribution
Technical root-cause input for P1/P2 problems on portfolio products
Within 5 business days of assignment
Individual
Assigned problem fix actions delivered on time
≥ 90%
Individual
Known-error entry drafted once root cause is found
100%, within 5 business days
Individual
Problem lessons added to design review and readiness checklists
Checklists updated quarterly
Individual
Vulnerability fix transition
Guidance provided after a patch pod request
≤ 5 business days
Individual
Fixes on portfolio products done without causing an incident
≥ 95%
Shared
Fix items waiting on ops engineering input
≤ 5%
Individual
Secure operations
Portfolio meeting Azure/Wintel hardening baselines
Employee
We are committed to creating an inclusive workplace and welcome applications from people of all backgrounds. We do not discriminate based on any protected characteristic under applicable law.
Pay not posted
Posted Jul 27, 2026
Pay not posted
Posted Jun 15, 2026
Woven by ToyotaPalo Alto, CA +1
$189K–$311K / yr
Posted 19 days ago
Pay not posted
Posted Dec 10, 2024
Source: the Cubic Workday careers site. We last checked this job 1 h ago. We first saw it 1 h ago. A job on a job board does not always mean that the team interviews people now. We found this job board in a public list. We did not yet compare it with the careers page of the company.
≥ 95%
Shared
Java / SQL support
Escalations resolved without developer or vendor involvement
≥ 70%
Individual
Compliance
Audit evidence provided on time
100%
Individual
Major audit findings on portfolio products
0
Shared
Planning
End-of-life components with a replacement plan
100%, ≥ 12 months before end of support
Individual
Knowledge
Portfolio architecture and product documents reviewed in last 6 months
≥ 90%
Individual
Stakeholders
NOC and SOC satisfaction (quarterly survey)
≥ 4 / 5 from each
Individual
NOC/SOC time split within agreed range
Within ±10%
Individual
Pay not posted
Posted Oct 9, 2026
Pay not posted
Posted Oct 6, 2026
No one has reported an interview at Cubic yet. Did you interview there? Add the questions.