🚀 NOTRE RAISON D'ETRE Créée en 2010 et basée à Toulouse, Opisto est le spécialiste de la pièce auto d’occasion. Nous avons une double mission : accompagner la filière de la destruction automobile dans ses enjeux de digitalisation tout en facilitant l’accès pour tous à des pièces auto d’occasion. Aujourd’hui plus de 700 Centres VHU Agréés utilisent quotidiennement notre logiciel Opisto et diffusent plus de 10 millions de pièces de réemploi, disponibles en temps réel, sur nos sites Internet (opisto.fr / opisto.com / opisto.pro) Nous sommes une entreprise en pleine croissance résolument tournée vers l’avenir. 95 collaborateurs se dépassent chaque jour pour concevoir, développer, commercialiser des solutions innovantes afin de répondre aux problématiques des centres VHU et promouvoir l’utilisation de la pièce de réemploi. Dans ce contexte, nous recherchons notre futur(e) Développeur pour rejoindre notre équipe Engineering au sein de la Tribe Marketplace et plus particulièrement notre squad E-commerce. Vous contribuerez notamment à l’évolution de nos parcours utilisateurs avant-vente et après-vente, pour soutenir la croissance e-commerce de nos marketplaces Opisto. Si vous êtes motivé(e) à nous rejoindre et que vous justifiez d’une expérience significative dans un poste similaire alors ce poste est fait pour vous ! 🧩 VOTRE FUTUR TERRAIN DE JEU, EN TANT QUE DEVELOPPEUR CHEZ OPISTO : Vous occuperez un rôle polyvalent, combinant une expertise en architecture logicielle et un rôle de conseiller technologique à vision stratégique. A ce titre, vous interviendrez notamment : - Qualité du code et performance des développements Optimiser le code, le déploiement et la delivery pour améliorer les performances, la réactivité et la stabilité des applications. Élaborer des normes de codage pour garantir la lisibilité et la maintenabilité du code. Conduire des revues de code régulières pour garantir le respect des normes et la qualité du code. Contribuer activement à l'amélioration de la lisibilité et de la maintenabilité de la codebase. Participer activement aux revues de conception technique, en veillant à l'alignement sur les objectifs architecturaux. Définir des critères de qualité pour mesurer l'efficacité des pratiques de développement. Mettre en place des processus et des outils pour évaluer la qualité du code et des livrables. Mettre en œuvre des mécanismes de surveillance des performances sur le code et la productivité. - Qualité de la delivery Optimiser le système et process de delivery et proposer des améliorations. Être prêt à intervenir et apporter un soutien immédiat en OPS en cas de bug de criticité très élevée. Anticiper les problèmes en OPS en investiguant, en les résolvant, ou en créant des tickets pour les équipes concernées. - Infrastructure Surveiller les performances des serveurs applicatifs. Gérer le relationnel avec le partenaire d’infrastructure, en collaboration avec le Platform Engineer (BSO, OVH). Gérer le relationnel avec le partenaire de test automatisés, en collaboration avec les Engineering Manager. - Architecture Logicielle et Conseil Technologique Concevoir des architectures logicielles alignées sur la stratégie de l'entreprise. Collaborer avec les équipes de développement pour garantir une mise en œuvre conforme aux meilleures pratiques architecturales. Etre proactif dans la veille technologique afin de repérer les nouvelles tendances et d'anticiper leur impact sur nos solutions. Accompagner les équipes internes et les partenaires lors des échanges projet en collaboration avec le Product Manager, afin de contribuer à la définition des processus et interfaces les plus adaptés aux besoins. Favoriser une culture de collaboration, d'apprentissage continu, et d'excellence technique, en documentant les processus et décisions techniques de la squad. Mickaël, notre Manager Engineering vous accompagnera au quotidien sur votre montée en compétences. STACK TECHNIQUE : - Angular - API en .NET - Base de données : SQL Server - Déploiement : Kubernetes - Cache : Redis - CI/CD : Azure devOPS - Obervabilité : Datadog 🎯 COMPETENCES RECHERCHEES : - Vous avez une expérience de 5 ans dans le développement de logiciel avec une expérience significative en .NET, C# et SQL Server. - Vous maitrisez les tendances technologiques, la sécurité informatique et les méthodologies de développement logiciel. - Vous avez idéalement une connaissance approfondie sur la définition et la mise en œuvre d’architectures logicielles robustes et évolutives. - Vous êtes à l’aise pour communiquer, et savez prioriser vos actions face aux changements. - Dynamique, rigoureux(se), motivé(e) et curieux(e), vous êtes force de proposition sur la recherche de solutions techniques innovantes et adaptées aux enjeux d’une structure. - Vous êtes familier avec les notions de containerisation, intégration web, Angular et le déploiement de micro-services. - Bonus 1 : Compréhension des enjeux de SEO/SEA. - Bonus 2 : Avoir déjà travaillé à l’intégration d’un système de paiement. Alors ce poste est fait pour vous ! 🤝 LES VALEURS DE NOS EQUIPES : - La responsabilité et l’autonomie - L’esprit d’équipe : confiance & fiabilité - Satisfaction client : performer par la qualité - Have fun ! 💼 LE POSTE : - Type de contrat : CDI, statut cadre - Rémunération : selon profil et expérience - Lieu de travail : Toulouse - Prise de poste : Dés que possible - Télétravail : jusqu’à 5 jours par semaine 🏢 LES AVANTAGES EN REJOIGNANT OPISTO : - Des titres restaurants - Une participation aux frais de télétravail - Une participation aux frais de transport en commun - Une prime de vacances - Une prime de cooptation - Une prime d'ancienneté - Une mutuelle pris en charge à 100% par nos soins - Un équilibre vie pro / vie perso : 37h30 par semaine avec 16 jours de RTT par an Vous pourrez être amené à adapter vos horaires de travail pour répondre aux objectifs du poste. - Des événements internes : afterwork, auberge espagnole, game en ligne, etc... 💭 NOS FUTURS ECHANGES : - Premier contact avec Mélissa, HRPB, par courriel - Echange avec Mélissa en visio (1h) - Echange avec Jérémy, Mickaël, Manager Engineering (1h) - Mise en situation avec des membres de l’équipe engineering (1h-1h30) - Echange avec Sébastien et Olivier, CEO & Head of Engineering (1h) Pour faciliter l’accès à tous à la pièce automobile d’occasion et contribuer au développement de l’économie circulaire, nous avons besoin de vous ! Si vous vous reconnaissez dans cette offre, n’hésitez plus nous attendons votre candidature !

• Own and evolve the core architecture of our platforms • Define and guide the strategy for our cloud environments • Own the design and governance of data systems • Design and evolve automated pipelines for code deployment • Serve as the technical voice during product ideation • Partner with Engineering Manager to manage technical debt

Hi! I'm Ryan, the Head of Marketing at Modash. I'm looking for a GTM Engineer to join our marketing team for the first time. Here's a little background, examples of the things you might work on, and things you probably want to know. Background & reason for hiring There are two major gaps in our team that are driving this hiring decision: The first is a gap in ownership between marketing & sales around call bookings. For context, we have a hybrid go-to-market that includes both self-serve free trials, and sales-led demo calls. Marketing is responsible for all pipeline generation (both trial & call booking KPIs), but there isn’t one clear person responsible (in either marketing or sales) for various things on the call bookings side. Things like: - How do we qualify demo requests? Who should our sales team spend their time with? - What happens when we decline a demo request? Is the user experience as good as it should be? - Improving the percentage of ICP trial sign ups who book with sales (since sales-closed deals are more likely to close, adopt, and retain long-term). The second gap relates to outbound. We’ve grown to 8-figure ARR solely with inbound marketing, but now it’s time to introduce outbound. I've already taken the first steps to get off the ground, but this needs dedicated ownership to make it world-class. I believe these two things can be handled together by the right person! Scope of the role & example projects The background above covers the broad scope pretty well, but here I'll elaborate a little more on what these initial projects might look like for you. Example 1: Taking ownership of call qualificiation We use a custom internal AI tool (lovingly referred to as “Leadgate”) that sits in front of our demo booking flow. Your job will be to own this end-to-end. You’ll need to collaborate with leadership to iterate on how we qualify calls, and what kind of prospects make the most sense to spend human sales time with. You’ll also own our demo booking page. The copy, the design, the form fields, everything. That means you can test & iterate on what expectations we set, what information we gather, and how that is used to route demos. Example 2: Building the “rejection experience” We want to focus our human sales time on ICPs, which means declining some demo requests (as above). However, “non-ICP” doesn’t mean “gets zero value from Modash”. We want to route those people through self-serve, with the best possible experience. Currently, the experience & flow is simply not good enough — because, once again, nobody owns it. You could create resources, implement demos with AI agents, write better copy, imagine new flows, and more. The goal is to improve brand perception, and increase self-serve revenue from non-ICP segments. Example 3: Taking ownership of the cold outbound program Our outbound cold email program is being run by an external agency, managed by me. Initially, it will be your job to replace me as their point of contact. That includes, for example: - Approving outreach lists - Approving / writing email copy - Strategizing new ideas (e.g. what happens when folks respond negatively) - Ensuring everything runs smoothly & quickly with positive replies Further into the future, you will decide how things run. You can double-down and scale with external agencies, you can build in-house, or a mix. Example 4: Reaching out to ICPs who start trials, but don’t book calls Approximately 10% of trial sign ups that we identify as ICP speak to the sales team. We believe that there’d be significant business impact if we can increase that. Currently, absolutely nothing is being done here. It’s a blank slate for you to come in and figure it out. Team structure To clarify again, this role is in the marketing team. You will report to me (Ryan), your primary KPIs will be around API call bookings, and you’ll collaborate often with the sales team. A few more things that may be useful to know about the team: - Our early-stage outbound project is currently ran by an external agency - We have a full-time software engineer in the marketing team (e.g. for iterations on Leadgate) - You will always write copy yourself; no assistance from a copywriting resource - We have a Product Marketer who will provide product messaging guidance where needed - Our CRM is managed by Steven Perroto (sales team); you will likely collaborate closely

Hi! I'm Ryan, the Head of Marketing at Modash. I'm looking for a GTM Engineer to join our marketing team for the first time. Here's a little background, examples of the things you might work on, and things you probably want to know. Background & reason for hiring There are two major gaps in our team that are driving this hiring decision: The first is a gap in ownership between marketing & sales around call bookings. For context, we have a hybrid go-to-market that includes both self-serve free trials, and sales-led demo calls. Marketing is responsible for all pipeline generation (both trial & call booking KPIs), but there isn’t one clear person responsible (in either marketing or sales) for various things on the call bookings side. Things like: - How do we qualify demo requests? Who should our sales team spend their time with? - What happens when we decline a demo request? Is the user experience as good as it should be? - Improving the percentage of ICP trial sign ups who book with sales (since sales-closed deals are more likely to close, adopt, and retain long-term). The second gap relates to outbound. We’ve grown to 8-figure ARR solely with inbound marketing, but now it’s time to introduce outbound. I've already taken the first steps to get off the ground, but this needs dedicated ownership to make it world-class. I believe these two things can be handled together by the right person! Scope of the role & example projects The background above covers the broad scope pretty well, but here I'll elaborate a little more on what these initial projects might look like for you. Example 1: Taking ownership of call qualificiation We use a custom internal AI tool (lovingly referred to as “Leadgate”) that sits in front of our demo booking flow. Your job will be to own this end-to-end. You’ll need to collaborate with leadership to iterate on how we qualify calls, and what kind of prospects make the most sense to spend human sales time with. You’ll also own our demo booking page. The copy, the design, the form fields, everything. That means you can test & iterate on what expectations we set, what information we gather, and how that is used to route demos. Example 2: Building the “rejection experience” We want to focus our human sales time on ICPs, which means declining some demo requests (as above). However, “non-ICP” doesn’t mean “gets zero value from Modash”. We want to route those people through self-serve, with the best possible experience. Currently, the experience & flow is simply not good enough — because, once again, nobody owns it. You could create resources, implement demos with AI agents, write better copy, imagine new flows, and more. The goal is to improve brand perception, and increase self-serve revenue from non-ICP segments. Example 3: Taking ownership of the cold outbound program Our outbound cold email program is being run by an external agency, managed by me. Initially, it will be your job to replace me as their point of contact. That includes, for example: - Approving outreach lists - Approving / writing email copy - Strategizing new ideas (e.g. what happens when folks respond negatively) - Ensuring everything runs smoothly & quickly with positive replies Further into the future, you will decide how things run. You can double-down and scale with external agencies, you can build in-house, or a mix. Example 4: Reaching out to ICPs who start trials, but don’t book calls Approximately 10% of trial sign ups that we identify as ICP speak to the sales team. We believe that there’d be significant business impact if we can increase that. Currently, absolutely nothing is being done here. It’s a blank slate for you to come in and figure it out. Team structure To clarify again, this role is in the marketing team. You will report to me (Ryan), your primary KPIs will be around API call bookings, and you’ll collaborate often with the sales team. A few more things that may be useful to know about the team: - Our early-stage outbound project is currently ran by an external agency - We have a full-time software engineer in the marketing team (e.g. for iterations on Leadgate) - You will always write copy yourself; no assistance from a copywriting resource - We have a Product Marketer who will provide product messaging guidance where needed - Our CRM is managed by Steven Perroto (sales team); you will likely collaborate closely