次の仕事の機会を見つけましょう

職種、スキル、勤務地で求人を検索できます。応募書類を準備する前に募集要件を確認しましょう。

魅力的な職種名を見つけることは、仕事探しの出発点です。業務内容、応募条件、働き方を自分の経験と照らし合わせましょう。このガイドでは、候補の絞り込み、応募書類の準備、提出先の確認を順番に進めるためのポイントを紹介します。

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

条件をクリア

検索結果: 9,367

← 検索結果に戻る

Senior Software Engineer - Data Search (remote, Europe)

Modash OÜ

リモート勤務

勤務地
Remote (France)
報酬
EUR 100000-130000 per annual
勤務時間
Full Time
掲載日
2026年10月8日

応募する前に、企業のウェブサイトで現在も募集中かどうかと詳しい条件を確認してください。

仕事内容

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

Remote — Data Search Team — Full-time Hey, I'm Adrian. I’m hiring a Senior Software Engineer to join the Data Search team at Modash. Modash helps brands find, understand, and work with creators across Instagram, TikTok, and YouTube. More than 2,700 companies—including Stanley 1913, Sennheiser, and NordVPN—use us to manage and scale their creator partnerships. Behind that product is a fascinating search problem: helping customers find the right people across 400M+ creator profiles and billions of media files. We’re combining large-scale data processing, traditional retrieval, vector search, multimodal embeddings, and LLMs to make that possible. That’s where you come in. Why we're hiring Search at Modash isn't an internal platform or a support function. It is one of the core products customers use to discover creators. The scale is large, the data is messy, and the search intent is often complex. A customer might be looking for creators in a specific niche, people whose content conveys a certain visual style, or accounts that resemble a group they already know. Solving that well requires more than adding another filter or calling an LLM API. We need a senior engineer who can work across the full retrieval system—from data and indexing pipelines to embeddings, ranking, relevance, and low-latency serving—and take ambiguous product problems all the way to production. You’ll join the specialised Data Search team and work closely with Data Core, Data Insights, product teams, customers, and company leadership. You’ll have real autonomy, but you won’t work in isolation. If you want a feel for how we think about building software, check our Engineering Blog. What you'll actually own 1. Make creator search meaningfully better. You’ll improve how customers discover creators across 400M+ profiles and billions of media files. That includes retrieval, filtering, ranking, relevance, speed, and the product decisions that connect them. 2. Turn multimodal data into searchable intelligence. You’ll build systems that generate and use embeddings from images, video, text, and audio at massive scale—then make those signals useful in a real customer-facing search experience. 3. Ship new search capabilities into production. You’ll evaluate models and technologies pragmatically, understand tradeoffs around cost, latency, and quality, and move promising approaches from experiment to a reliable production system within weeks rather than quarters. 4. Own the system end to end. You’ll help shape the problem, gather requirements, design the architecture, write the code, release it, measure the outcome, and improve it. Senior engineers here own results, not just implementation tasks. What the day-to-day looks like Here’s what a typical week might include: Monday. A customer search is returning technically relevant but unhelpful results. You inspect the retrieval and ranking stages, identify where intent is being lost, and propose a measurable improvement. Tuesday. Deep-focus time. You build a pipeline to generate multimodal embeddings across a large batch of creator content and test how the new representation affects retrieval quality and cost. Wednesday. You work with Data Insights on a new in-house datapoint. Together, you agree on its definition, coverage, and data-quality requirements, then expose it in Search to give customers more ways to discover creators. Thursday. You test a reranking model on a fixed set of real customer queries. You measure how much it improves relevance against the latency and inference cost it adds, then decide what's ready for production. Friday. You review production metrics, investigate a relevance regression, and share what you learned with the team. The fix may be in the model, the data, the query logic, or the product itself—you follow the evidence. We keep meetings purposeful and protect time for deep work. You’ll have a short standup, close collaboration when it helps, and plenty of space to design, build, optimise, and launch. Requirements What you've done before Built large-scale data or backend products. You have solid experience working with systems where volume, latency, reliability, and cost all matter. Shipped products from concept to production. You’ve owned scoping, architecture, implementation, release, measurement, and iteration—not just one layer of the solution. Designed distributed systems. You can reason clearly about throughput, failure modes, data flow, scalability, and operational tradeoffs. Built LLM-powered or agentic features in production. You understand the practical differences between models and can balance capability against latency and cost. Worked autonomously on ambiguous problems. You know how to gather requirements, ask useful questions, and turn incomplete context into forward motion. Communicated clearly across teams. You can explain technical tradeoffs to engineers and non-engineers, give direct feedback, and collaborate without creating unnecessary process. Worked in a fast-moving product environment. You’re comfortable learning quickly, shipping incrementally, and changing direction when the evidence does. Bonus points if you’ve worked with multimodal embeddings, vector databases, semantic search, ranking algorithms, model deployment, self-hosted models, or GPU infrastructure. Curiosity about the creator economy helps too, but we’ll get you up to speed. Our stack AWS and GCP, with Pulumi for infrastructure as code Python, TypeScript, and Node.js PySpark on AWS EMR Airflow Milvus Vector DB through Zilliz Elasticsearch LLM batch APIs Apache Iceberg SageMaker, DynamoDB, S3, Glue, Kinesis, Lambda, ECS, and Aurora Slack, GitHub, Linear, Notion, and Cursor The interview process We move quickly and can complete the process in under a week: Intro chat Coding interview System design interview Team interview Culture and alignment conversation with our CEO, Avery Schrader Benefits What we offer Fully remote in Europe 🏠 Work from wherever you do your best work, with some overlap with GMT+3. Compensation. Your compensation is made up of salary and stock options. As we're growing fast, the stock option package is especially significant. Annual salary range is 100,000€ - 130,000€ for this role. We hire across Europe, so the exact number depends on your location, employment type, skills, and experience. Flexible hours ⏱ We care about outcomes, not when you log on. Unlimited paid vacation 🌴 If you’re rested and happy, you do better work. Take what you need. Personal development support 🧠 Courses, books, and conferences are on us when they help you grow. Real ownership 💡 Take difficult search problems from idea to production without layers of unnecessary process. Regular offsites ✈️ We’re remote-first, but we make time to connect, collaborate, and have fun together in person. And a little more about us... Founded in 2018 by a high-school dropout and a Canadian (yes, we’re also shocked it’s going so well), Modash is building a suite of tools that help brands scale partnerships with online content creators. 2,700+ companies like Stanley 1913, Sennheiser, and NordVPN already use Modash to manage and scale their influencer marketing work. And we're just getting started. Over the coming decade, brand investment in creators will continue to boom, and Modash will be at the centre of it all. Modash is here to stay. We have 8-figures in ARR across two products, a $12M series A investment, and we are default alive. We are building a company that will still be here in 20 years; not rushing towards an exit. We’re almost 100 people distributed across 20+ countries, operating with a fast, async-first culture. If you join Modash, you’ll be surrounded by people who truly want to be the greatest at their craft. People who make you better. Interesting people too, who have done everything from building solar cars, to hanging out with Metallica and Bon Jovi. Come join us. Be great, do great things, create great memories, all while making a great impact. Do it. Originally posted on Himalayas

検索して比較し、応募を準備しましょう

次の仕事で活かしたい職種やスキルから検索を始めましょう。勤務地と職種の条件を調整し、求人を開いて担当業務を比較してください。結果がない場合は、短い検索語を試すか、条件を一つずつ外してみましょう。

必須条件と歓迎条件を分けて確認し、勤務時間、報酬、勤務地が掲載されている場合は目を通しましょう。リモート勤務でも、居住国、就労資格、勤務時間帯が指定されることがあります。現在の募集状況と詳しい条件は企業に確認してください。

募集要件に関連する実際の経験を選び、自分の役割と貢献を説明しましょう。数値は根拠がある場合にのみ使ってください。企業の応募方法に従い、送信前に連絡先、内容、PDFの表示を確認しましょう。

応募前の確認リスト

仕事探しに関するよくある質問

英語の求人が表示されるのはなぜですか?

職種名や説明文は企業が作成したものです。条件や要件を変えないように原文を掲載しています。操作画面とこのガイドは日本語です。日本語の検索で見つからない場合は、「software engineer」のように、掲載言語の職種名やスキル名でも検索してみてください。検索語が自動翻訳されるわけではありません。

リモート求人なら、どの国からでも働けますか?

必ずしもそうではありません。居住国、就労資格、勤務時間帯が指定されている場合があります。元の求人ページで条件を確認してください。記載がない場合は、自分の居住地から応募できると判断する前に企業へ確認しましょう。リモートという表示だけでは、勤務地の制限がないことは分かりません。

検索結果が出ない場合はどうすればよいですか?

より一般的な職種名や一つのスキルで検索し、条件を一つずつ外してみてください。同じような仕事でも企業によって呼び方が異なります。特定の求人が見つからなくなった場合は、企業の採用ページで求人番号を探しましょう。検索条件を広げても、終了した募集が再開するわけではありません。

ResumizeAIから応募が送信されますか?

応募ボタンは外部サイトを開きます。企業または採用サービスの案内に従い、そのサイトで送信を完了してください。ResumizeAIで応募書類を作成しただけでは応募は送信されません。リンク先が企業のトップページの場合は、該当する募集を探してから手続きを進めましょう。

応募書類とカバーレターはどう調整すればよいですか?

募集要件と、自分が説明できるプロジェクト、業務、成果を結び付けます。経験していない技術や実績を加えず、関連する経験を分かりやすく示してください。カバーレターでは応募理由を具体例とともに伝えます。指定された言語とファイル形式に従い、送信前に両方の書類を確認しましょう。