寻找你的下一个职业机会

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

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

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

清除筛选

搜索结果: 14,274

← 返回搜索结果

Full-Stack Engineer (Go or similar)

Rivet

远程工作

地点
Remote (United States)
工作安排
Full Time
发布日期
2026年10月15日

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

职位描述

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

About Rivet Rivet is an AI-native accounting firm. In less than 3 years, we've built a T500 firm in the US, combining corporate and personal income tax, sales tax, R&D credits, and bookkeeping into a single, all-inclusive experience that eliminates the worst parts of tax season for real businesses and the people who run them. Our platform is designed to feel invisible: it guides clients through their tax to-dos, automates the drudgery for preparers, and gets out of the way when it's not needed. We measure success in time saved and returns completed, not vanity usage metrics. We run Rivet (the firm) on Rivet (the platform) because owning the stack makes it possible to deeply embed AI into every step of our workflows, far more than our competition will ever be able to relying on third-party/off-the-shelf tooling. Our team of 75 supports more than 1,300 clients, including some of the most innovative companies in the US — Cursor, Cognition, and ModRetro — and their executives, investors, and employees. And while we may have just gotten started a little over two years ago, this isn't our first rodeo: Nick Abouzeid (cofounder & CEO) comes from Ramp, where he ran three of their Growth teams from $100M → $600M in ARR Kyle Christenson (cofounder & Head of Tax) comes from the IRS, where he spent six years as an auditor before leaving to start his own firm over a decade ago We're well-funded, growing quickly, and sustainable. We've raised over $7M to date, from investors like XYZ Ventures, Susa Ventures, Haystack Ventures, and 40+ executives from Ramp, Anduril, Physical Intelligence, & more. Why this role is different At six engineers, features don't stop at an API boundary. The person who designs the schema is the person who ships the screen and the person who hears about it when a preparer can't find the button. Ownership from first commit to production. Engineers design, build, ship, and maintain their work — no handoffs, no middle-management mazes. Decisions happen at the edge. Engineers talk to clients and tax preparers directly. We optimize for speed and context, not committee consensus. Clear is kind. We surface problems early, talk about tradeoffs openly, and don't sugarcoat. We're kind by being honest, not by being vague. Pragmatic stacks. We pick tools that solve real problems. If it doesn't help us ship faster, safer, or better, we don't use it. Skin in the game. We ship things we'd be proud to put our name on — and if something breaks, we own it and fix it fast. Our stack Six engineers today, five languages. You'd work across the first two: Platform: Go, as a modular monolith — Connect RPC over protobuf, Go Fx for wiring, sqlc and goose against Postgres, River Pro for background jobs, Watermill for pub-sub over RabbitMQ. Frontend: React and TanStack, deployed to Cloudflare Workers. AI and eval: Python, in their own repos — ModelBridge (a gRPC service for AI building blocks) and TaxBench, our internal eval suite. Legacy integration: a C# Windows agent that drives Drake, one of the tax platforms our industry never built APIs for. Infrastructure: AWS — ECS Fargate, Amazon MQ, AMP, Loki, Tempo — provisioned by Pulumi, itself written in Go. Around the edges: Buildkite for CI, OpenTelemetry throughout, Doppler for secrets, Linear for tracking. What you'll do Ship features end to end — Postgres schema, Go service, protobuf contract, React screen, and the alert that pages you when it breaks. Move where the quarter needs you. Client portal in the fall, preparer workspace before January, platform work when filing season quiets down. This role is for someone who finds that energizing rather than scattered. Take AI from prototype to product. Plenty of things demo well here. Deciding what graduates into a workflow preparers depend on, and hardening it so it can be, is the job. Talk to accountants and clients directly, then go build the thing they actually needed. Leave the codebase better than you found it. We have five languages and six engineers. Some of that is deliberate; some of it isn't, and we want opinions about which is which. We're fully distributed — but if you want an office, we'll help you find one through our investor network. What makes you a fit 5+ years shipping full-stack web applications, with production experience in both Go and React Have owned features end to end on a small team, where there was nobody to hand the other half to Comfortable choosing where the complexity should live — in the schema, the service, or the UI — and defending the call Know how to prototype fast and then decide, honestly, what it takes to make it real Comfortable operating in a fast-changing, early-stage environment Excellent verbal and written communication skills Nice to haves Were the first or second engineer on a product that made it to real users Connect RPC, gRPC, or protobuf-first API design, and generated typed clients TanStack in production, or edge deployment on Cloudflare Workers Shipped LLM systems into production paths and evaluated them properly, not as prototypes Built tax-adjacent software — fund administration, payroll, accounting platforms, filing systems Started a company yourself, however small What we offer Benefits and meaningful equity A fully remote team, plus twice-yearly company offsites A well-funded, fast-moving environment with minimal layers of management A world-class client base that values your time and pays for the premium experience The chance to build production-grade software your teammates use and love every day We encourage you to apply even if you don't meet every qualification. Strong candidates rarely check every box. Originally posted on Himalayas

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

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

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

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

提交申请前的检查清单

求职常见问题

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

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

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

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

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

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

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

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

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

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