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 roles14274 openings
4881-4888 of 14274
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 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.
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.
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.
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.
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
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
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
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.