Braze
Software Engineer II, Channels
About this role
Join Braze's SMS team as a Software Engineer II to build and scale SMS and RCS messaging channels. You'll own fullstack features end-to-end, from composition and sending to analytics, while collaborating across teams to keep the platform reliable at scale.
What you'll do
- Design and ship fullstack features for SMS and RCS channels from concept to delivery
- Own key technical areas as a primary engineer and solve open-ended problems
- Build and maintain supporting services including click tracking and link shortening
- Ensure platform reliability and performance as traffic scales
- Collaborate across teams and functions on cross-channel messaging initiatives
- Drive technical decisions with clear communication to peers and leadership
What they're looking for
- Full-stack development (5+ years)
- Distributed systems design and implementation
- Data structures and algorithms
- Ruby or Rails
- PostgreSQL and MongoDB
- React or TypeScript
- Redis and Sidekiq
- Self-directed problem-solving and communication
Benefits
- Equity grants (RSUs)
- Flexible paid time off
- Comprehensive health, dental, vision, life, and disability coverage
- Professional development with learning stipend and career pathing
- Paid parental leave and fertility benefits
- Hybrid work environment
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Braze
Braze builds customer engagement and messaging technology for enterprise clients. The company is hiring Security & Privacy Solutions Engineers to serve as technical pre-sales experts who manage compliance questionnaires, advise on security architecture, and accelerate enterprise deals by building trust between customers and Braze's internal teams.
- Website
- braze.com
Likely interview questions
- Tell us about a distributed system you've built at scale and how you ensured its reliability under high traffic.
- Describe your experience with fullstack development—which backend and frontend technologies do you prefer and why?