Senior Software Engineer - Stability

Benefits

Parental leave

Not verified not verified - source not recorded; timestamp not recorded

Non-birth-parent leave

Not verified not verified - source not recorded; timestamp not recorded

Family-building benefits

• Fertility benefits: Not verified
• Adoption assistance: Not verified
• Surrogacy assistance: Not verified

Mental health support

Not verified

Relocation assistance

Not verified

Childcare support

Not verified

Learning budget

Not verified

Verification

Not verified

Salary

Not verified not verified - source not recorded; timestamp not recorded

Was this benefit information wrong? Tell us.

Schedule

Shift type

Not verified

Weekend work

Not verified

Application

Cover letter

Not verified

Assessment

Not verified

Deadline

Not stated

Where they hire

State eligibility is not yet verified.

About this role

Senior Software Engineer - Stability San Francisco, CA, New York, NY, Portland, OR, or Remote within Canada or United States The year is 1969. The location: Stuttgart, West Germany. Engineers are pacing with strained expressions. They are looking over the Porsche 917, the company's latest attempt at a race car. It's not working properly. The car is one of the most powerful ever built. But drivers describe it as terrifyingly unstable… "a monster". Despite this, Porsche runs it in Le Mans to disastrous results. One of the cars crashes on lap one, ending in tragedy for its driver. All other 917s break down in the race. Enter John Wyer, a British race engineer, whom the factory calls upon for help. After a long day of testing, John recognizes a lack of smashed bugs on the rear wing and deduces that the wing is not working properly. The team modifies the design to be more upward swept and the 917K takes on a new winning character. It wins LeMans outright in 1970 and goes on to be the most successful race car design of the 70s. Stability, it turns out, was the missing ingredient. Mercury prides itself in providing powerful banking* services. But if those services aren't reliable, Mercury will fail. The Stability team exists to help product engineers see patterns of instability and remedy them. We champion and improve observability. We've helped define incident response. We have introduced and support robust background work processing. We monitor and build tooling around

Read the full description at job-boards.greenhouse.io. FewerJobs shows a source-linked preview and links to the original posting.