寻找你的下一个职业机会

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

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

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

清除筛选

搜索结果: 14,068

← 返回搜索结果

Engineering Manager, Automation Intelligence

Fingerprint

远程工作

地点
Remote (United States)
薪资
USD 159000-215000 per annual
工作安排
Full Time
发布日期
2026年10月18日

申请前,请在雇主网站确认职位仍在招聘,并检查完整要求和条件。

职位描述

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

Fingerprint empowers enterprises to detect and stop online fraud with the world’s most accurate device intelligence. We lead our industry with bleeding-edge identification capabilities and work on turning new ideas and discoveries in the fraud detection space into reality. Our customers range from innovative startups to leading enterprise companies, including Plaid, Dropbox, and Booking.com. Fingerprint is a globally dispersed, 100% remote company. We were named on on the 2026 Forbes Best Startup Employers list and ranked #803 on the 2026 Inc. 5000 list of America’s fastest-growing private companies. We have raised $77M and are backed by Craft Ventures (Tesla, Facebook, Airbnb ), Nexus Venture Partners ( Postman, Apollo.io,MinIO, Druva) and Uncorrelated Ventures ( Redis, Rollbar, Gradle). The Role in Context Fingerprint's device intelligence platform processes billions of identification events for companies that need to know who — or what — is on the other end of a request. Increasingly, the answer is not a person. AI agents, AI assistants, crawlers, headless browsers, and malicious automation now make up a large and fast-growing share of internet traffic, and telling them apart from humans — and from each other — is becoming one of the most important problems our customers ask us to solve. We are standing up a dedicated Automation Intelligence engineering team to own that problem end to end: detection in the browser, detection at the edge, the classification taxonomy that tells customers what kind of automation they're seeing and how confident we are, and the API that customers and their agents call. We're looking for an Engineering Manager to lead this team. You'll inherit a small, senior group (three engineers to start, growing to four or five) and a clear mandate. You report directly to the VP of Engineering. Your Mission Ship the product — Take the automation intelligence product through Beta to GA, and then to a standalone commercial launch. You own engineering readiness: scope, estimates, service reliability, operating limits, API and MCP coverage, and the evidence that it's ready Make detection accurate and keep it that way — Build the team's quality loop: a test corpus of known bots, agents, and automation frameworks; continuous false-positive and false-negative testing; a regression test for every confirmed gap; and coverage benchmarked against the best in the industry. Detection quality is the product Build a team that runs itself — Set the team up so adding a detection, shipping a change, or running a staged rollout doesn't depend on another team's calendar. Grow the engineers, hire the next seats, and create an environment where senior people do their best work Lead the AI-native engineering model — AI agents write the code by default and engineers decide what gets built and whether it's right. You'll operate that model, measure it honestly, and produce the playbook the rest of engineering adopts What You'll Do Delivery & Product Readiness Own the engineering plan for Beta → GA → standalone launch: PRD partnership with the product manager, estimates, sequencing, and the readiness evidence that gates each stage Define and prove the service's operating envelope — throughput, latency tails, rate limiting, availability SLOs — before customers depend on it Run staged rollouts for detection changes that affect customer bot rates, with feature flags, rollback, and clear go/no-go evidence for customer-facing teams Turn design-partner feedback and customer-reported false positives into prioritized, owned engineering work Detection Quality & Coverage Stand up and run a weekly detection quality loop: prioritized test corpus, automated FP/FN testing across browser and edge detection, regression coverage, and drift monitoring Drive coverage of the automation that matters most to customers — AI agents and assistants first — benchmarked against industry leaders, and prioritized by customer exposure rather than catalogue size Guide the hard problems: self-hosted agents, stealth and anti-detect browser automation, and fingerprinting agent infrastructure across browser, network, and runtime evidence Evolve the classification contract from "automation detected" to rich agent context — automation type, verified vs. inferred identity, confidence, and reason codes — and keep detection and attribution measured separately Team Leadership Manage, coach, and grow a team of senior engineers; run hiring for the next seats, starting with a detection research and quality engineer Set the team's goals against its charter and bring them to leadership for alignment, not approval; communicate decisions as intent with reasoning before acting Establish healthy engineering practice from day one: written ownership lines, review tiers per repository, specs before epics, and baselines for cycle time, throughput, predictability, change failure rate, and recovery time Negotiate clean working agreements with the sibling team the codebase is shared with today, and drive gradual decoupling prioritized by what blocks independent deploys AI-Native Engineering Operate the agent-first development model: spec → coding agent → review agent → security review → human merge, with low-risk changes merging on agent approval and mandatory human review on critical paths Treat the agent harness — repository instructions, skills, review personas — as infrastructure maintained like code, and publish it so other teams start ahead Measure the model against the team's own baseline, run 30- and 60-day reviews, and write up what worked and what didn't for the rest of engineering Contract-First APIs Ensure every surface the team ships is contract-first: OpenAPI in the repo, breaking-change detection in CI, generated docs and SDKs, and the API kept readable by both developers and AI agents Own the team's observability: logs, metrics, traces, and SLOs for the detection service What We're Looking For Required Engineering management experience: 3+ years managing software engineers, ideally including senior and staff-level ICs, with a track record of shipping products — not just features — through launch Strong technical foundation: 8+ years in software engineering before or alongside management. You can read a design doc and a PR critically, engage senior engineers on architecture, and make technical calls when the team is split Relevant domain depth in at least one of: bot detection or bot management, fraud or abuse prevention, web security, browser or client-side engineering, or high-volume API services. You understand that this is an adversarial problem where the other side adapts Quality-driven mindset: Experience building or running measurement-driven engineering — test corpora, precision/recall or FP/FN tracking, regression suites, SLOs — and using that data to prioritize Hands-on with AI coding tools: You use AI coding agents in your own work, have opinions about where they help and where they don't, and are excited to lead a team where they are the default Cross-functional operator: You've worked closely with product managers, researchers, and customer-facing teams, and you're comfortable making dependencies and trade-offs explicit rather than absorbing them Clear communicator: You write well, make decisions visible with your reasoning, and can explain detection quality and launch readiness to executives and customers alike Nice to Have Direct experience with bot detection, bot management, or anti-automation products (e.g. at a CDN, WAF, fraud, or security vendor) Familiarity with AI agent ecosystems: agent frameworks, verified-agent protocols, and how agents interact with websites and APIs Experience with browser internals or headless/automation frameworks and the techniques used to detect or evade them Experience running API-first products with public OpenAPI specs, SDKs, and MCP or similar agent-facing surfaces Experience forming a new team out of an existing one — separating codebases, setting ownership lines, and keeping the sibling relationship healthy Experience in a high-growth SaaS company with enterprise customers The Shape of This Role This is a hands-on-adjacent engineering manager role for a small, senior, high-leverage team. You are not expected to write the production code — your engineers and their agents do that — but you are expected to be close enough to it to set direction, evaluate the work, and hold the quality bar. The team has unusual autonomy and unusual visibility. It owns a product that leadership considers strategically critical, it is the first team operating Fingerprint's AI-native engineering model, and its results — good and bad — will be used as evidence for how the rest of engineering works. That means two things: you'll have real room to decide how the team operates, and you'll need to be honest about what the data shows. In the first 90 days you will likely: finalize the roster and ownership lines with the sibling team, get the quality loop and engineering baselines running, deliver the engineering evidence for the Beta gate, and run the first review of the AI-native operating model. Why This Role? A problem that is getting harder and more important every quarter: The internet is filling with agents. Customers need to tell useful automation from abuse, and the answer isn't "block everything." The team that solves this well defines a category A product with a clear path to market: Beta to GA to standalone launch, with product, go-to-market, and executive support already lined up A senior team and a dedicated PM from day one: You're not starting from zero. The engineers already know the problem; your job is to focus them and remove what's in their way Lead how engineering will work next: AI-native development, contract-first APIs, and a self-directed team model — piloted here first, with your findings shaping the whole organization VP direct line: You report to the VP of Engineering, set your own goals against a clear charter, and bring recommendations rather than requests for direction Compensation & Transparency At Fingerprint, we believe in pay transparency — it's part of how we operate as a distributed, remote-first team. Salaries are based on function, level, and geographic location, benchmarked against similar stage growth companies. Because this role is open across the United States and can be based anywhere our team members work from, the salary range reflects that geographic breadth: $159k - $215k Some example salaries for specific locations are below: NYC: $187k - $215k Chicago: $159k - $183k Final offer amounts are determined by multiple factors, including the successful candidate's location, experience, and expertise, and may vary from the amounts listed above. Due to regulatory and security reasons, there’s a small number of countries where we cannot have Fingerprint teammates based. Additionally, because Fingerprint is an all-remote company and people can join our workforce from almost any country, we do not sponsor visas. Fingerprint teammates need to be authorized to work from their home location. We are dedicated to creating an inclusive work environment for everyone. We embrace and celebrate the unique experiences, perspectives and cultural backgrounds that each employee brings to our workplace. Fingerprint strives to foster an environment where our employees feel respected, valued and empowered, and our team members are at the forefront in helping us promote and sustain an inclusive workplace. We highly encourage people from underrepresented groups in tech to apply. If you are applying as a resident of California, please read our CCPA notice here. If you are applying as a resident of the EU, please read our GDPR notice here. **We have noticed a rise in recruiting impersonations across the industry, where scammers attempt to access candidates' personal and financial information through fake interviews and offers. All Fingerprint recruiting email communications will always come from the @fingerprint.com domain. Any outreach claiming to be from Fingerprint via other sources should be ignored. Originally posted on Himalayas

查找职位、比较要求,再准备申请

从你希望从事的职位或运用的技能开始搜索。调整地点和职业筛选,打开职位比较工作职责。如果没有结果,可以使用更短的关键词,或逐一移除筛选条件。

区分必备要求和优先条件,检查已列出的工作安排、薪资和地点。远程职位也可能要求特定居住国家、工作许可或工作时间重合。请向雇主确认职位信息和完整条件。

选择能够回应职位要求的真实经历,说明你的贡献,只使用能够证实的数字。遵循雇主的申请说明,并在提交前检查联系方式、文档内容和 PDF。

提交申请前的检查清单

求职常见问题

为什么有些职位使用英文?

职位名称和描述由招聘企业撰写。为避免改变招聘要求或工作条件,我们保留原文。操作界面和本指南使用简体中文。如果中文搜索没有结果,可以尝试使用职位发布语言中的名称或技能,例如“software engineer”。搜索词不会自动翻译,界面语言也不代表企业要求的申请语言。

远程职位是否允许从任何国家工作?

不一定。企业可能对居住国家、工作许可或工作时段有要求。请查看原始招聘页面中的具体条件。如果未说明,应先向企业确认,再判断能否从你所在的地区工作。“远程”标签本身并不代表没有地点限制。

搜索没有结果时应该怎么办?

尝试更通用的职位名称或单个技能,并逐一移除筛选条件。不同企业可能用不同名称描述相似工作。如果某个职位已经消失,请在企业招聘页面搜索其职位编号。扩大搜索范围不会让已经关闭的职位重新开放。

申请会通过 ResumizeAI 直接提交吗?

申请按钮会打开外部网站。请按照企业或招聘服务的说明,在该网站完成并确认提交。在 ResumizeAI 中准备简历并不等于已经申请职位。如果链接只打开企业网站,请先找到对应职位,再继续申请流程。

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

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