Staff Software Engineer, Notifications

About Command|Link

Command|Link is a global SaaS Platform providing network, voice services, and IT security solutions, helping corporations consolidate their core infrastructure into a single vendor and layering on a proprietary single pane of glass platform. Command|Link has revolutionized the IT industry by tackling the problems our competitors create. In recognition for our unprecedented innovation and dedication, Command|Link was recognized as the SD-WAN Product of the Year, ITSM Visionary Spotlight, UCaaS Product of the Year, NaaS Product of the Year, Supplier of the Year, and the AT&T Strategic Growth Partner. Command|Link has built the only IT platform for scale that solves ISP vendor sprawl and IT headaches. We make it easy for our customers to get more done, maximize uptime and improve the bottom line.

Learn more about us here!

This is a 100% remote position

About your new role:

Command|Alert is the service that decides when, where, and how every alert gets delivered, and getting that right is one of the clearest ways CommandLink wins against competitors on alert fatigue. All alerts trigger all the time; this service's job is to turn that firehose into the right message, to the right person, through the right channel, with guaranteed delivery and without flooding anyone. As a Staff Engineer on this service, you own not just the implementation but the delivery architecture: the routing logic, escalation model, workflow orchestration strategy, and the per-tenant configuration model that makes it all composable. You'll define how the service evolves as channel complexity grows, set the technical patterns other engineers build against, and ensure Command|Alert remains a platform capability rather than a collection of point integrations.

Key Responsibilities:

- Own the architecture and long-term direction of Command|Alert, including delivery guarantees, routing logic, enrichment pipelines, escalation policies, and per-tenant configuration.

- Define the integration model for outbound channels: PagerDuty, Slack, email, SMS, SOAR platforms, Jira, ServiceNow, CommandLink ITSM, AI triage, and webhooks.

- Design and evolve the Temporal workflow layer that underpins complex delivery logic: grouping, silencing, custom scheduling, business-hours windows, and guaranteed delivery under failure.

- Own long-running channel state: tracking alert volume, processing status, pending queues, and the ability to de-queue or clear messages reliably.

- Drive the subscriber configuration model, defining how users specify which alerts they receive, through which channels, and on whose behalf.

- Establish technical standards for integration development that keep the channel surface area maintainable as it grows.

- Identify and resolve cross-team dependencies early, particularly where Command|Alert's routing and enrichment logic depends on upstream classification, ingestion, or security signal contracts.

- Mentor engineers working within and adjacent to the alerting domain, and raise the bar on reliability and delivery-correctness across the team

- Takes on additional responsibilities and projects as needed to support the success of the team and organization.

What you'll need for success:
Required:

- Demonstrated experience designing and operating high-reliability notification or alerting systems at production scale.

- Strong integration engineering background across channel brokers: PagerDuty, Slack, email/SMS, ticketing platforms, SOAR, and webhooks.

- Hands-on production experience with Temporal or a comparable workflow orchestration platform, including long-running workflow design and failure recovery.

- Experience reasoning across distributed system state, particularly in contexts where delivery guarantees and idempotency are non-negotiable.

- Ability to operate across ambiguous problem spaces and make durable architectural decisions without complete requirements.

- Track record of cross-team technical influen