Operations Assistant
Supports founders or small teams with scheduling, documentation, research, CRM hygiene, recurring admin, and safe coordination of day-to-day work.
New to this area? Learn the foundations before building proof.
Also listed as
Web3 Operations Assistant · Executive Operations Assistant · Remote Operations Assistant
What this role actually does
Most days, the practitioner has to prepare meetings, update trackers, follow up on actions, organize files, and support routine communications.
Its decision rights usually cover administrative reliability, calendar and meeting systems, and basic research, while company strategy and unapproved wallet transactions remain outside the default remit.
Where the role sits
Operations Assistant usually sits inside Product, Operations, Customer Experience, or a founder-led operating team. Common reporting lines include Head of Product, COO, Product Operations Lead, Customer Experience Lead, or a functional founder. Most strategic roles are core-team positions; support and execution roles also appear as contractors, agencies, or fractional operations support. The role usually collaborates with Operations Associate, Product Operations, Customer Support Specialist, Grant Writer.
Core responsibilities
- Maintain calendars, agendas, notes, action items, and recurring reminders
- Organize documents, contacts, CRM records, and basic operational dashboards
- Prepare factual research briefs and meeting context
- Coordinate routine community, partner, event, or travel administration
- Track follow-up and make missing ownership visible
- Handle sensitive information and access according to least-privilege rules
Daily, weekly, and reactive work
A typical day
Prepare meetings, update trackers, follow up on actions, organize files, and support routine communications.
Weekly or monthly
Clean systems, review overdue items, compile a short operations report, and improve one recurring workflow.
When conditions change
Respond to schedule changes, missing documents, urgent logistics, access problems, or a founder request that crosses an approval boundary.
Deliverables
How success is judged
- Reliable follow-through
- Accurate records
- Fewer missed commitments
- Clear handoffs
- Safe access handling
- Time saved for the team
Read signals in context. Read reliable follow-through together with accurate records. Neither signal is meaningful without the relevant launch, incident, market, workload, or attribution context.
Tools in practice
- Google Workspace
- Draft, review, and maintain meeting pack and action tracker, with owners, source links, and change history.
- Notion
- Draft, review, and maintain meeting pack and action tracker, with owners, source links, and change history.
- Airtable
- Maintain the operating record behind meeting pack and action tracker, including owners, dates, exceptions, and unresolved dependencies.
- calendar tools
- Coordinate meetings, deadlines, review windows, and handoffs across time zones while protecting focus time and access boundaries.
- Slack, Telegram, or Discord
- Coordinate stakeholders and capture decisions or issues that feed into meeting pack and action tracker.
- password-management workflow
- Use approved credential-sharing and access-revocation workflows; never store seed phrases or private keys.
Skills and prerequisite knowledge
Hard skills
- Administration
- Research
- Documentation
- Spreadsheet basics
- Calendar and task management
Working skills
- Structured communication
- Prioritization
- Reliability
- Cross-functional coordination
- Comfort with ambiguity
Prerequisite knowledge
Understand confidentiality, approval boundaries, wallet safety, meeting etiquette, and how the team records decisions.
Expectations by level
Entry level
At entry level, a candidate should be able to complete a scoped assignment with review. That includes the ability to maintain calendars, agendas, notes, action items, and recurring reminders, to organize documents, contacts, CRM records, and basic operational dashboards, and to produce reviewable artifacts such as a meeting pack and an action tracker.
Mid level
At mid level, the practitioner normally owns administrative reliability, calendar and meeting systems, and basic research without constant supervision. They can coordinate adjacent teams and improve the workflow behind a meeting pack and an action tracker, including when the role must respond to schedule changes, missing documents, urgent logistics, access problems, or a founder request that crosses an approval boundary.
Senior
At senior level, the work shifts toward standards, decision rights, and review quality. A senior Operations Assistant defines how administrative reliability, calendar and meeting systems, and basic research are handled, reviews high-risk cases, and builds systems that do not depend on one person.
Proof of work and portfolio
Reviewers should be able to inspect a meeting pack and an action tracker, trace the inputs or decisions behind the work, and understand what the candidate personally owned.
Strong proof
- A founder-support SOP
- A meeting and action system
- A weekly dashboard
- A concise research brief with sources
Weak evidence
- A list of tools with no workflow
- Claims of being organized without examples
- Portfolios containing confidential client data
Common mistakes and misconceptions
- Taking responsibility for company strategy and unapproved wallet transactions without the mandate or approval to do so
Common misconception
Operations Assistant may overlap with Operations Associate, but the hiring evidence is different. This role is judged on administrative reliability, calendar and meeting systems, and basic research, not on ownership of company strategy and unapproved wallet transactions.
Scope boundaries
Usually owns
- Administrative reliability
- Calendar and meeting systems
- Basic research
- Documentation upkeep
- Routine follow-up
- Access hygiene
Usually does not own
- Company strategy
- Unapproved wallet transactions
- Legal or financial authority
- People management
- Specialist analysis presented as expert work
Interview focus
Expect questions about administration, research, and documentation, plus a scenario where the role must respond to schedule changes, missing documents, urgent logistics, access problems, or a founder request that crosses an approval boundary. Interviewers are looking for evidence that the candidate knows where administrative reliability and calendar and meeting systems stop and company strategy and unapproved wallet transactions begin.
How do you make async support visible without creating noise?
What would you do if asked to sign a transaction or share sensitive credentials?
How do you clarify priorities when several leaders assign urgent work?
Compensation and role risks
Reliable Web3-specific salary evidence is limited. Treat this as administrative or operations support and show hourly, monthly, or salaried context only when directly sourced.
No reliable role-specific range
KRAFT did not find a reliable role-specific range that meets the evidence standard. Compensation may still exist through salary, contract fees, retainers, grants, commissions, token or equity packages, creator revenue, or business economics. These models are described separately rather than compressed into an invented number.
Wider Web3 market, for scale
Typical advertised averages $65,000 – $200,000 / year
Individual postings run from about $40,000 to $350,000.
Across the role categories this index tracks, advertised averages sit between roughly $65,000 and $200,000 per year, with individual postings from about $40,000 to $350,000. This is whole-market scale from advertised roles - not a figure for this specific role, and not verified paid compensation.
Role risks
- Scope creep
- Sensitive access
- Off-hours expectations
- Being treated as a substitute for specialist roles
- Unclear priorities
Compensation can change materially by geography, seniority, employment model, company stage, market cycle, and the mix of cash, bonus, commission, equity, token, vesting, royalties, or fees. A published range is useful only when those dimensions match the role being considered.
How to read compensation evidence
- Direct
- Evidence from the same or a materially equivalent role.
- Adjacent
- Evidence from a neighbouring occupation, used only for context.
- Broad market
- Category-level Web3 or labour-market evidence.
- Unverified
- Estimates without enough source or methodology detail.
Confidence reflects the quality and comparability of the evidence, not the value or legitimacy of the role.
Career path and role fit
Common progression
May fit people who
People who value reliability, discretion, clear systems, and making other people's work easier without needing public credit.
May not fit people who
People who need broad decision authority immediately or who struggle to say no to unsafe access requests.
Practical next steps
How this guide is built. Role content is drawn from current first-party hiring material and reputable industry evidence, with compensation labelled by confidence and evidence tier rather than a single number.
Turn this role into evidence.
Choose a proof-of-work project, package the result, and practice the questions this role is likely to ask.