DEV Community: xiaowei

Equity vs Salary: How to Compare a Startup Offer Without Fooling Yourself

xiaowei — Thu, 26 Mar 2026 08:27:39 +0000

Equity vs Salary: How to Compare a Startup Offer Without Fooling Yourself

A lot of job offers try to make lower cash feel acceptable by showing a big equity number.

Sometimes that trade-off is worth it.
Often it isn't.

The mistake most candidates make is treating equity like delayed salary. It isn't. Salary is money you can use next month. Equity is a future possibility that depends on vesting, dilution, company performance, and whether a real liquidity event ever happens.

If you compare them as if they are equally real, you will almost always overvalue the upside story.

Here is the framework I use when comparing an offer with more salary against an offer with more equity.

1. Start with the cash gap, not the narrative

Before you get pulled into the startup story, calculate the real cash difference.

Ask:

How much lower is the base salary?
How much does that change my monthly life?
Does the lower salary create stress around rent, family, debt, or savings?

A lot of people say they are "fine with less cash" in theory. In practice, lower cash often changes how much pressure they feel every week.

That matters.

If the lower-salary offer makes your real life tighter, the equity has to clear a much higher bar.

2. Treat equity as uncertain upside, not guaranteed compensation

This is the core mental model.

Salary is guaranteed unless you get laid off.
Equity is probabilistic.

Its value depends on things like:

vesting schedule
dilution over time
exercise cost
company survival
future valuation growth
whether the company ever reaches liquidity

So when a company says:

"The package is lower in cash, but the equity could be worth a lot."

The important word is could.

That doesn't make equity useless. It just means you should discount it heavily unless you have strong reasons not to.

3. Ask whether the company quality is high enough for equity to matter at all

Not all equity deserves serious weight.

If the business is weak, unstable, or vague about fundamentals, the equity may be more motivational theater than compensation.

I would ask:

Is the company growing or stalling?
Do I trust the leadership?
Is there real traction?
How strong is the funding or revenue base?
Would I still want this job if the equity ended up being worth nothing?

That last question is especially important.

If the answer is no, the offer is probably too dependent on a best-case scenario.

4. Compare career upside separately from financial upside

People often bundle these together, but they are different.

Sometimes a lower-cash startup offer is still the better decision because it gives you:

much broader scope
stronger ownership
faster learning
better long-term positioning
a more impressive story for the next role

In that case, the decision is not really "salary vs equity."
It is more like:

lower salary today in exchange for better career capital + some upside

That can be a smart move.

But if the lower-cash role is also weaker on manager quality, stability, and day-to-day fit, then the equity story is doing too much work.

5. Watch for the four ways candidates overvalue equity

I see the same mistakes over and over:

1) Anchoring on the headline number

A company mentions a big potential number and your brain starts treating it as half-real.

2) Ignoring dilution

Your percentage today is not necessarily your effective value later.

3) Confusing paper value with liquid value

A valuation on paper is not the same as cash in your account.

4) Underestimating personal cash pressure

Lower salary sounds manageable until it starts affecting your life every month.

6. Use a simple comparison table

When I want to get more objective, I score each offer across these dimensions:

Factor	What to check
Cash gap	How much monthly breathing room do I lose?
Company quality	Is the upside story credible enough to count?
Equity terms	Vesting, dilution, exercise, liquidity path
Career upside	Scope, learning, network, future signaling
Lifestyle fit	Can I live with the lower salary without resentment?
Risk concentration	Am I stacking company risk, role risk, and cash risk at the same time?

This is much better than asking, "Which offer sounds more exciting?"

7. When taking less salary for more equity actually makes sense

I think this trade-off can make sense when:

you have enough financial cushion
the company quality is genuinely strong
the role gives much better growth and scope
you understand the equity terms clearly
you would still feel okay about the job even if the upside never fully materialized

In other words: the equity is a bonus on top of an already strong decision.

8. When it usually does not make sense

I would be much more cautious when:

you need the higher cash for real life stability
the company is vague about equity details
the company is risky and the role itself is not especially compelling
the offer relies on urgency or hype
you are telling yourself the upside is basically guaranteed

That last one is the classic trap.

The simplest rule

If one offer pays more cash and the other offers more equity, ask yourself:

If the equity ends up being worth little or nothing, would I still be happy I chose this role?

If yes, then the lower-cash offer may still be a smart long-term bet.
If no, you are probably overpaying for uncertainty.

Final thought

The best job decision is usually not the one with the most exciting story.
It is the one that balances:

financial reality
career upside
manager and company quality
personal risk tolerance

If you want a clearer side-by-side way to think through salary, equity, growth, and risk, I built a free comparison workflow at JobMirror.

And if you want the original long-form version of this topic, the canonical article is here:

https://jobmirror.app/blog/equity-vs-salary

How I Built a Free AI Job Offer Comparison Tool on Cloudflare Pages (Next.js + Edge Runtime)

xiaowei — Mon, 23 Mar 2026 03:09:26 +0000

I built JobMirror — a free AI toolkit for job seekers — and deployed it entirely on Cloudflare Pages with Next.js. Here's what I learned, what broke, and how I fixed it.

Why I Built It

Most job seekers face the same three problems:

They apply to jobs without knowing how well their resume actually matches
They accept the first offer they get without comparing alternatives
They leave salary on the table because they don't have data

I wanted to fix all three with a single, free tool. The result is JobMirror: resume review, job fit analysis, offer comparison, career assessment, and cover letter generation in one place.

The Stack

Next.js 14 (App Router)
Cloudflare Pages with @cloudflare/next-on-pages
DeepSeek API for AI inference
next-auth v5 beta for Google OAuth
No database — JWT sessions + localStorage

The Hard Parts

1. Edge Runtime Is Not Node.js

Cloudflare Pages runs your code on V8 isolates, not Node.js. This means:

No fs, no crypto from Node
No prisma (uses native bindings)
Any library that assumes Node.js internals will silently fail or loudly crash

Every API route needs this at the top:

export const runtime = 'edge';

Forget it on one route and you get a cryptic build error or a 500 in production.

2. next-auth v4 Breaks on Edge

next-auth v4 imports Node's crypto module internally. On Cloudflare Pages, this throws:

Module not found: Can't resolve 'crypto'

The fix: upgrade to next-auth v5 beta (5.0.0-beta.30), which is built for Edge from the ground up.

npm install next-auth@5.0.0-beta.30

v5 also changes the config shape significantly — AUTH_SECRET instead of NEXTAUTH_SECRET, and the provider setup is slightly different. Worth it though.

3. The Correct Build + Deploy Command

This tripped me up for a while. The output directory is NOT .next — it's .vercel/output/static:

# Build
npx @cloudflare/next-on-pages@1

# Deploy
CLOUDFLARE_API_TOKEN="your_token" \
CLOUDFLARE_ACCOUNT_ID="your_account_id" \
npx wrangler pages deploy .vercel/output/static \
  --project-name=your-project \
  --branch=main

Deploying .next directly results in a site that returns 404 or 500 on every route. Ask me how I know.

4. SessionProvider Can't Be in a Server Component

If you put <SessionProvider> directly in layout.tsx, Next.js tries to prerender it as a server component and throws during build. Wrap it:

// components/ClientProviders.tsx
'use client';
import { SessionProvider } from 'next-auth/react';

export default function ClientProviders({ children }: { children: React.ReactNode }) {
  return <SessionProvider>{children}</SessionProvider>;
}

Then use <ClientProviders> in your layout — works cleanly.

5. AI on the Edge

For AI inference, I'm calling DeepSeek's API directly from Edge functions. Since it's just HTTP, it works perfectly — no special SDK needed:

export const runtime = 'edge';

export async function POST(req: Request) {
  const { resume, jobDescription } = await req.json();

  const response = await fetch('https://api.deepseek.com/v1/chat/completions', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'Authorization': `Bearer ${process.env.DEEPSEEK_API_KEY}`,
    },
    body: JSON.stringify({
      model: 'deepseek-chat',
      messages: [
        { role: 'system', content: 'You are a career coach...'},
        { role: 'user', content: `Resume: ${resume}\n\nJob: ${jobDescription}` }
      ],
      stream: true,
    }),
  });

  return new Response(response.body, {
    headers: { 'Content-Type': 'text/event-stream' },
  });
}

Streaming works out of the box because Edge functions support ReadableStream natively.

What I'd Do Differently

Start with Edge constraints in mind. Don't pick libraries and then discover they don't work on Edge — check first.
Use Cloudflare D1 or KV early. I'm using localStorage for user data right now, which works but isn't ideal for any kind of persistence.
Don't use pnpm with Cloudflare Pages. The lockfile version mismatch errors are frequent and annoying. Use npm.

The Result

JobMirror is live and free to use:

🎯 Job Fit Analyzer — paste any JD, get a match score and keyword gaps
📝 Resume Review — 6-dimension AI audit with specific fixes
⚖️ Offer Comparison — side-by-side AI breakdown of multiple offers
🧠 Career Assessment — Big Five personality mapped to role fit

No account required for core tools. Feedback welcome — especially if you've hit similar Edge Runtime issues.

Built with Next.js 14, Cloudflare Pages, and more late nights than I'd like to admit.

How I Built an AI PDF Summarizer on Cloudflare Edge (Next.js + next-auth v5)

xiaowei — Tue, 17 Mar 2026 09:39:27 +0000

The Problem
I was tired of reading 50-page reports just to find 3 key points.

Existing tools either cost too much, require a desktop install, or just do dumb text extraction with no intelligence. I wanted something that could summarize, explain, and answer questions about any PDF — in the browser, for free.

So I built SumifyPDF.

What It Does
🤖 AI Summary — upload a PDF, get key insights in ~10 seconds
💬 Chat with PDF — ask "what are the risks?" or "summarize section 3"
🗺️ Mind Map — auto-generated visual overview
📝 PDF → Word conversion
🖼️ PDF → Image export
🔗 Merge PDFs
🔒 Encrypt / Decrypt
📷 OCR for scanned documents
All running in the browser. No install. Free to start.

Tech Stack
Next.js 14 on Cloudflare Pages (Edge Runtime)
Advanced AI models for summarization and chat
OCR API for scanned document support
next-auth v5 beta for Google OAuth
PayPal for Pro subscriptions
Cloudflare Workers for all API routes
The Hard Parts

Cloudflare Edge + next-auth = Pain This was the biggest headache. next-auth v4 depends on Node.js crypto module — which doesn't exist on Cloudflare Edge Runtime.

The error:

Module not found: Can't resolve 'crypto'

Fix: Migrate to next-auth v5 beta (5.0.0-beta.30), which is Edge-compatible.

// src/lib/auth.ts
import NextAuth from 'next-auth';
import Google from 'next-auth/providers/google';

export const { handlers, auth, signIn, signOut } = NextAuth({
providers: [Google],
trustHost: true,
session: { strategy: 'jwt' },
});

// src/app/api/auth/[...nextauth]/route.ts
export const runtime = 'edge'; // ← this is the key line
export { handlers as GET, handlers as POST } from '@/lib/auth';

Also: SessionProvider can't be used directly in layout.tsx — it causes prerender crashes on /_not-found. Wrap it in a 'use client' component:

// src/components/ClientProviders.tsx
'use client';
import { SessionProvider } from 'next-auth/react';
export function AuthProvider({ children }: { children: React.ReactNode }) {
return {children};
}

Wrong Deploy Path First deployment: the site showed only 404 pages.

I was deploying .next/export — which only contains the 404/500 pages when using next-on-pages.

Correct path:

npx @cloudflare/next-on-pages@1
npx wrangler pages deploy .vercel/output/static --project-name=my-project

The build output goes to .vercel/output/static, not .next/.

Prisma / SQLite on Edge Early version used Prisma + SQLite for session storage. Edge Runtime doesn't support Node.js file system APIs.

Fix: Switched to JWT sessions (stateless). No database needed for auth.

pnpm Lockfile Conflicts Cloudflare Pages build kept failing with:

ERR_PNPM_OUTDATED_LOCKFILE

Fix: Delete pnpm-lock.yaml and let it regenerate. Or switch to npm.

Architecture Overview
User Browser
│
▼
Cloudflare Pages (Edge)
├── Next.js App Router (SSR on Edge)
├── /api/summarize → AI summarization
├── /api/chat → Conversational Q&A
├── /api/ocr → Scanned PDF processing
└── /api/auth → next-auth v5 (Edge)

All API routes run as Cloudflare Workers — globally distributed, ~0 cold start.

What I'd Do Differently
Start with next-auth v5 — don't waste time on v4 for Edge projects
Test the deploy path early — wrangler pages deploy has specific requirements
Keep auth stateless — JWT sessions are simpler and Edge-compatible
Ship fast, iterate — the first version had 3 features. Now it has 8.
Try It
👉 sumifypdf.com — free to use, no signup required for basic features.

If you're building on Cloudflare Edge with Next.js, happy to answer questions in the comments. The auth + Edge combination has a lot of undocumented gotchas.