Algolia
Software Engineer, Growth
Remote - United States (Remote)From $196.1kmidAdded today
About this role
Algolia is seeking a Software Engineer for the Growth team to help developers quickly adopt and maximize the AI Search platform. You'll build user-facing solutions, run experiments, and scale growth infrastructure while collaborating across product, design, and engineering teams.
What you'll do
- Build solutions that help users onboard and succeed with Algolia's search platform
- Design and execute A/B tests and experiments to validate growth initiatives
- Collaborate with Product and Design teams to identify and explore growth opportunities
- Develop and scale the Growth platform infrastructure to support customer and internal needs
- Write high-quality, well-tested code and participate in code reviews
- Contribute to engineering best practices, processes, and tooling improvements
What they're looking for
- Backend development with Ruby or Go
- Full-stack development with TypeScript and React
- Event-driven architecture on GCP or AWS
- Data-driven decision making and analytics
- A/B testing and experimentation frameworks
- Production application development and scaling
- API design and integration
- SQL and database optimization
Benefits
- Remote work flexibility with option for fully remote arrangement
- Competitive base salary ($136,400–$196,100)
- High-trust environment with autonomy and impact-focused work
- Global presence with offices in Paris, NYC, London, Sydney, and Bucharest
- Opportunity to shape UX for diverse user segments across industries
- Ownership of projects from discovery through delivery
Opens the official application on the employer’s site. No login required.
Algolia
Algolia builds an AI-powered search platform for enterprise customers. The company is hiring Solutions Engineers and Customer Success Engineers to drive pre-sales technical engagement and guide customers through implementation and optimization.
- Website
- algolia.com
Likely interview questions
- Can you describe a time you shipped a feature iteratively and used data to drive decisions on what to build next?
- What experience do you have with A/B testing frameworks or experimentation platforms?