[Hiring] Software Engineer @Oyster

Role Description

Our team owns Oyster’s APIs, connected architecture (including Model Context Protocol services) and identity and access management systems. In this role you’ll build and maintain the Ruby on Rails APIs that help our internal teams get work done more effectively.

You’ll partner directly with colleagues across the business to understand how they work, find where an API can remove manual effort, clarify requirements and deliver real productivity improvements. You’ll take well-scoped projects from design through release, with the team’s support on design choices and on unfamiliar or higher-risk areas. Along the way, you’ll grow your ownership of projects within the team.

What You’ll Build & Own

• Internal API use cases, from discovery to delivery.
• Work with internal stakeholders to understand their workflow, define acceptance criteria and break the work into manageable increments.
• Production Rails APIs.
• Design, implement, test, review and release changes within established architecture and security practices, raising dependencies and risks early.
• Secure, careful code.
• Reliable, maintainable systems.
• Measurable impact.
• A strong team culture.

What You’ll Bring

Essential

• 3+ years of professional software development experience with a focus on Ruby.
• Proven experience developing and maintaining Ruby on Rails applications. You can explain your API implementation choices and use Git effectively.
• The ability to refine straightforward stakeholder requirements into well-scoped work, and to ask for support when risk or dependencies exceed the agreed scope.
• Strong code quality habits: readable code, automated tests (TDD where appropriate), continuous integration, meaningful reviews and secure coding awareness.
• Fluency with AI-assisted development, including independent verification of generated code, tests and assumptions.
• Clear communication and effective collaboration in an agile, remote team. You adapt as priorities change and document decisions so others can work asynchronously.

Nice to have

• Front-end experience with React and TypeScript.
• Exposure to internal developer-facing APIs, identity and access management, or Model Context Protocol services. This is not required.

Benefits

• Direct, visible impact.
• Growing ownership with real support.
• A meaningful technical domain.
• Thoughtful remote culture.