
In the initial months, you'll be working closely with the founding team, gradually taking ownership of central components.
We are on the brink of something monumental, anticipating a tidal wave of traffic. You'll be at the forefront of ensuring our systems not only handle the influx but thrive under the pressure.
We focus on performance and reliability, our traffic is live and our latency is the most important metric we need to watch. We work very closely with the backend team, helping everyone to bring code in production. Automation is key as it is for most of our industry, if you need to repeat a task, automate it; for everything.
Vision and leadership
System Design and Management
Automation and Efficiency
Backend Team Partnership
Software Engineering and Development
To ensure that everyone is set up for success within our way of working, we work together onsite 5 days a week.
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:
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.




