寻找你的下一个职业机会

按职位、技能和地点搜索招聘信息。准备申请前,先仔细了解职位要求。

找到一个吸引人的职位名称只是求职的起点。请将工作职责、招聘要求和工作条件与你的实际经历进行比较。本指南帮助你筛选机会、准备有针对性的申请材料,并确认每份申请应该在哪里提交。

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

清除筛选

搜索结果: 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 中准备简历并不等于已经申请职位。如果链接只打开企业网站,请先找到对应职位,再继续申请流程。

如何针对职位调整简历和求职信?

将招聘要求与能够解释清楚的项目、任务和成果联系起来。突出相关经历,不要添加未经实际掌握的技能或虚构成绩。在求职信中用具体例子说明申请动机,并遵守企业要求的语言和文件格式。提交前检查两份文件,确保内容准确、联系方式正确、链接可用。