Integration Reliability Engineer, Technical Operations

Requirements

• Have at least 2 years of industry experience
• Knowledge of and experience with payment technologies and ecosystems
• Ability to write high quality code. We work mostly in Ruby and Java. However, languages can be learned: we care much more about your general coding skill than knowledge of a particular language or framework
• Comfort using SQL to navigate Stripe's data and diagnose the scope and urgency of issues
• Comfort with developer tools (e.g. git), and an ability to make well-scoped code changes in Stripe's codebase
• Great technical problem-solving skills, with an ability to develop a working understanding of a technical system using a variety of methods. These include (but aren't limited to): reading/writing code, reading documentation or partner specifications, running debugging programs, reading logs, asking well-formed questions to domain experts, or digging into the raw data through various interfaces
• Great communication skills, with an ability to frame messages appropriately for technical and non-technical audiences
• The will to deliver results, with an ability to establish priorities and reliably execute on solutions (often with hard external deadlines)
• An instinct to produce work that increases the impact of others, and helps us scale and grow (e.g. documentation, tools)

What You'll Be Doing

Responsibilities

• Become a domain expert in Radar and other areas of the Payment Performance & Fraud stack
• Handle inquiries from internal Stripes and external partners' technical teams with detailed investigation and sometimes code changes
• Organize and direct complex technical changes as part of product releases and merchant migrations
• Identify and automate inefficient or unnecessary manual processes by making direct code changes, or coordinating more complex code changes across Stripe
• Design alerting systems using existing tools to respond to incidents quickly, or prevent them altogether
• Conduct data analysis to understand the impact of merchant configurations for Radar, and surface future product opportunities
• Technical Operations roles are one part coding and one part managing projects. The ideal candidate will have experience in both, but successful candidates may index more highly in one or the other

Nice to Haves

• No specific nice-to-have requirements mentioned