
We’re hiring one of the earliest members of the Web Engineering team at amo. In the first few months, you’ll work closely with the team to build and own the systems that power our operations, analytics, and distribution. As an early member of the team, we’re looking for versatile engineers who are comfortable owning entire surfaces, from architecture to implementation to monitoring.
We value engineers who go deep, develop strong subject-matter expertise, and take full responsibility for their area. You’ll contribute to scaling our web stack, our internal product philosophy, and the speed at which the company can learn and scale.
The Web team at amo builds the backbone of our internal platform: from Backoffice tools to growth dashboards, from experimentation systems to invite-page infrastructure, from analytics instrumentation to the UI and backend layers that empower other teams to operate effectively.
Building Internal Tools & Backoffice Systems
Developing internal platforms for data access, monitoring, and operational workflows, working directly with internal users to uncover their needs and bottlenecks, and translating them into scalable, well-engineered solutions that fit seamlessly into our stack.
Owning Growth & Distribution Infrastructure
Implementing systems for growth levers, distribution flows, acquisition, activation and retention tracking, and invite pages with rich OG metadata.
Orchestrating / Segmentation
Leveraging workflow orchestration system (Restate) to architect durable, event-driven workflows that support growth mechanisms, data processing, segmentation logic, and lifecycle automation across the platform.
Creating Metrics Dashboards & Data Visualizations
Developing real-time dashboards and transforming metrics into self-serve actionable insights for the team.
(Optional) AI-Driven Automation
Contributing to AI/LLM-powered pipelines for scalable content and metadata generation, delivery, and publishing, with systems that adapt and improve based on observed performance and/or manual scoring.
End-to-End Ownership
Taking responsibility for architecture, implementation, performance, monitoring, and reliability.
Continuous Improvement
Sharing best practices, participating in code reviews, and helping to maintain and elevate our engineering standards and patterns.
We’re hiring for multiple levels; please specify your years of experience when applying.
We wanted to make sure coming to the office was as comfortable as possible for you:
Because life outside of work should also be stress-free, we cover:
Vacation days: 8-9 weeks (total) per year (European summer?).
We shut down entirely twice a year, two weeks in summer and one week in winter to allow everyone to truly recharge and to avoid prolonged slowdowns (especially in the summer). These pauses are part of your total vacation time, giving everyone a real chance to unplug and recharge. No Slack, no email, no FOMO.
We love the diverse perspectives we get from having people from all over the world join us (68% of our team is international), and so we of course support relocation to Paris with:


Amo is a social technology company that develops consumer applications focused on online communication between friends. The company positions itself as a multi-app ecosystem where a single user profile and social graph are shared across products.
Its product portfolio includes ID, Bump, and Sugar. ID provides a collaborative social profile, Bump focuses on mapping friends and places, and Sugar enables chat-based communication using a free-form canvas instead of traditional messaging interfaces.
All amo applications are connected through a unified account system, allowing users to move between apps without reconfiguring profiles, settings, or connections. New applications can be introduced independently without being constrained by a single app interface.
The company states that it builds standalone applications rather than a single super-app, with each product designed around a specific use case. Product development follows a principle of iterative experimentation across multiple apps.
Amo defines internal principles that guide product decisions, including prioritizing creation over passive consumption and avoiding engagement driven by metrics such as likes or followers. The company emphasizes responsibility in designing products intended for long-term use in social communication.




