Find your next opportunity
Browse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert rolesBrowse expert rolesBrowse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert roles14067 openings
6873-6880 of 14067
Rivet
Free to start · No card · 5 credits the moment you sign up
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 50 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.
We don't run an internship program. There's no cohort, no intern project graveyard, no summer showcase. We open this role when we meet someone we're excited to work with, and the work is the same work everyone else is doing.
That means a few things you should take literally:
You'll ship to production. Not a sandbox, not a prototype someone archives in September. Real users, real returns, real consequences.
Ownership from first commit to production. You design, build, ship, and maintain your work — with someone experienced sitting close, not reviewing from a distance.
Decisions happen at the edge. Engineers talk to clients and tax preparers directly. You will too.
Clear is kind. You'll get direct feedback early and often. We're kind by being honest, not by being vague.
We're hiring you for slope, not credentials. What you've built on your own matters more than where you're enrolled.
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.
Own a scoped feature end to end — Postgres schema, Go service, protobuf contract, React screen. Scoped so you can finish it, not so it doesn't matter.
Pair with the engineer who owns that module. You'll have a named mentor from day one and a standing weekly with them.
Work on the automation problems. Our industry never built APIs. Parsing filings that arrive as scanned paper and reconciling ledgers that disagree with each other is most of the interesting work here, and plenty of it is well-scoped.
Talk to accountants every day. They're on Slack, they'll tell you exactly what's broken, and they're the reason the thing you build matters.
Ask questions in public. We'd rather you ask in a channel than spend two days stuck.
You've built things outside of coursework — side projects, open source, a company, something you shipped because you wanted it to exist
Working knowledge of at least one of Go or React, and real interest in the other
You can read unfamiliar code and make progress without a tutorial
You write clearly. Remote and asynchronous means most of the job is writing
You want feedback and do something with it
Enrolled in or recently out of a degree program, or self-taught and at an equivalent point
Any exposure to protobuf, gRPC, or typed API clients
You've used LLMs to build something real, and have opinions about where they fail
Curiosity about tax, accounting, or other domains where a wrong number has consequences
A named mentor, a real project, and a direct line to the CEO
A fully remote team, plus twice-yearly company offsites
A well-funded, fast-moving environment with minimal layers of management
An honest conversation about a full-time offer at the end, in either direction - we've brought on our first two interns full-time (even while they wrapped up school) in the last 2.5 years
We open this role rarely and only for people we're excited to mentor. If that sounds like a reason not to apply, apply anyway.
Originally posted on Himalayas
Start with a role or skill you want to use in your next job. Use the location and role filters to narrow the results, then open a listing to review the description. A title alone rarely explains the level of responsibility, working arrangement, or experience a team needs. Compare those details before deciding which opportunities deserve a tailored application.
Employers use different titles for similar work. If an exact phrase produces no results, try a shorter title, a core skill, or an alternative name for the role. Remove one filter at a time to understand which requirement is narrowing your search. A broader search can reveal suitable work without asking you to change your actual qualifications.
For each promising listing, read the responsibilities and separate essential requirements from preferences. Note the location, schedule, employment type, and compensation when provided. Missing details are questions to confirm with the employer. A remote opening may still require a particular country, work authorization, or time-zone overlap, so check the full posting before treating it as a location-independent opportunity.
Choose a few examples that demonstrate the skills this employer names. Explain your contribution and its outcome, using accurate numbers where available. Put the most relevant experience first and keep your resume easy to scan. Avoid adding technologies, qualifications, or achievements simply because they appear in a description. Your application should make your existing strengths easier to understand.
Follow the employer’s instructions for resumes, cover letters, work samples, and screening questions. Review the exported file before submitting it: confirm that contact details are correct, text can be selected, and links reach the intended pages. A resume check can help you spot unclear writing before you apply. Its feedback is advisory and does not predict a hiring decision.
Listings are collected from external sources and may change after they appear here. The employer or recruiting destination controls whether applications are open. If an original link is unavailable, check the company’s careers page for the title or move to another opening. An employer website link is a place to check current vacancies, rather than confirmation that a particular job is still accepting applications.
Keep a simple record of the company, role, job reference, application date, and documents you sent. Record any follow-up instructions and the next action you plan to take. This makes it easier to prepare for interviews, compare opportunities, and avoid applying repeatedly to the same opening through different boards. Review your shortlist as employers update their listings and prioritize opportunities with clear requirements that match the work you want to do.