Staff Software Engineer

About the role

This role leads the architecture and delivery of Braze's core data platform as a hands-on technical leader. You partner with product and engineering teams to shape foundational data structures and drive high-scale solutions in a fast-growth, globally distributed environment that values work-life harmony.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Software design, coding, and operational best practices are guided by example and mentorship from the lead engineer. Opportunities to research and adopt new technologies are identified and advocated for where appropriate, supporting ongoing system improvement.

Requirements

Professional software engineering experience includes hands-on full-stack and back-end work on high-scale, high-throughput systems for 7+ years. A proven track record of building foundational, data-driven systems at scale, such as streaming, real-time pipelines, or large-scale data platforms, is demonstrated. Architectural direction is driven, large efforts are scoped, technical debt is managed, and complex technical concepts are communicated precisely. Strong fundamentals in software design, data structures, and algorithms are required. Thriving in team environments is demonstrated through strong communication and organizational skills.

Nice to have

Familiarity with Ruby, Ruby on Rails, React, Go, and SQL/NoSQL databases. Experience with MongoDB, Snowflake, or other data lake solutions. Proficiency in container orchestration (Kubernetes) and cloud services (AWS, GCP, Azure). Background in distributed systems, API design, monitoring, and best practices. A passion for customer experience.

Skills & tools

Core Data Objects, Ruby, Ruby on Rails, React, Go, SQL/NoSQL databases, MongoDB, Snowflake, Kubernetes, AWS, GCP, Azure, monitoring tools.

Practical notes

This role is based in Toronto under a hybrid work arrangement. Candidates in Canada receive comprehensive benefits, hybrid work options, and structured career development. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

The role focuses on foundational data systems and large-scale platform design. Team members work with modern cloud and containerized infrastructure. The organization invests in learning, career pathing, and structured professional development. Collaboration, transparency, and customer-centricity are emphasized. Continuous learning and innovation are supported through formal and informal programs.

Questions to ask

Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question. Keep the list short and pick the questions that matter most to you.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.