Alchemy Pays $350k Yet Demands Unpaid Open‑Source Proof

The Surge: 18 Roles, Six Departments, One Bet

Alchemy posted 18 hybrid, full-time roles, Alchemy Jobs reported, across six departments — seven in engineering, five in sales, two each in product and people, one each in design and finance. Zero G Talent's board shows 14 salaried positions with a median band of $233,000, ranging from $140,000 to $304,000. A Director of Engineering role in San Francisco pushes the top to $350,000, Alchemy Jobs found.

Geography shows the bet: San Francisco, New York, and Bucharest each host multiple listings, with some roles posted in multiple cities. Bucharest's cluster includes three backend and DevOps roles. The newest postings in New York and San Francisco tilt toward revenue: a Revenue Operations Lead at $175,000–$220,000 and paired recruiter roles at $160,000–$210,000.

LinkedIn shows 518 historical openings, but the current 18 concentrate across product, infrastructure, and go-to-market, a simultaneous push. The careers page cites "building the world's open economy" and values like "Extreme ownership" and "The fast eat the slow." That language, with the salary bands and San Francisco concentration, signals a bet on scaling the platform layer, not experimenting at the edges.

Equity grants price at the last round ($10.2B, February 2022), not a fresh 409A, inflating paper value if secondary markets trade higher. The company front-loads 25% of equity after year one, unusual in a sector where four-year linear vesting is standard, and adds a 0.02% refresh at 12 months worth roughly $30k–$45k. Alchemy applies a 1.15x location multiplier for San Francisco hires but not remote roles, compressing remote total comp versus Bay Area peers.

Levels.fyi places software engineering at $150k–$250k. The PM ladder tells a sharper story: L4 total comp $260k–$310k, $30k–$45k above Coinbase and Ripple. L5 PM: $210k–$240k base, 20% target bonus, 0.07% equity for $340k–$420k total. After year one, L6 climbs to $380k–$460k as vesting acceleration and a 25% bonus ceiling kick in. These exceed most protocol-layer competitors, and candidates have noticed.

Inside the Screen: Three Rounds, Five Weeks, Four Pillars

Alchemy's process runs three rounds over three to five weeks: a recruiter screen, a technical phone interview, then a full onsite. Dataford's guide shows the phone and onsite stages cover system design, problem solving, Java, SQL, and behavioral questions, with emphasis on architectural judgment and protocol fluency.

The phone screen opens with algorithmic tasks: binary search, linked-list reversal, two-sum. These filter for clean code and clear reasoning under time pressure. Dataford rates the binary search "medium" difficulty, testing not just correctness but the ability to articulate edge cases and complexity trade-offs. Interviewers also probe Java fundamentals.

System design dominates the onsite. The "Microservices vs Monolith" question tests architectural judgment hard, candidates defend operational complexity, scaling strategy, deployment boundaries, failure isolation. Interviewers demand explicit trade-off discussion: consistency vs availability, latency vs throughput, build vs buy. Reciting patterns without context fails.

Database fundamentals get direct tests: optimize a query, explain stack vs queue. The four OOP pillars (encapsulation, inheritance, polymorphism, abstraction) remain a staple, showing Alchemy values foundational CS literacy alongside distributed-systems chops.

Blockchain knowledge forms a separate filter. Candidates report protocol questions covering consensus mechanisms, EVM internals, gas economics, Solidity patterns, token standards, Merkle trees, forks, oracles, sharding, the blockchain trilemma. Candidates who can't explain how a node validates a block or why a 51% attack threatens finality stall before the onsite.

Behavioral rounds test leadership, influence, cultural alignment: "Describe a significant technical challenge," "Tell us about influencing a team decision." Even these ladder back to technical credibility, interviewers check whether past decisions reflect the scalability and trade-off thinking the design rounds demand.

Nine Dataford interviews rate overall difficulty "medium," but the screen compounds multiple independent filters, algorithmic fluency, distributed-systems architecture, database internals, blockchain protocol depth. Miss one pillar and the loop ends.

Why GitHub Now Outweighs the Résumé

Recruiters skim GitHub before résumés. Technical interviewers read pull-request threads before asking candidates to code. Hiring managers at FAANG labs, OpenAI, Hugging Face, and Anthropic now open calls with, "I saw your PR on the Hugging Face Transformers repo, tell me more." LinkedIn's 2025 Tech Hiring Report found 41% of ML hiring managers prioritize active GitHub over equivalent experience with no public trail. Open source is no longer extra credit — it's the living portfolio of trust.

A strong open-source trail reveals maturity better than any take-home. It shows how candidates behave unwatched: how they respond to review, iterate after rejection, document for the next contributor. That intrinsic motivation signals engineering curiosity, one of the rarest traits in technical hiring. It also proves collaboration beyond the team: handling reviews, aligning with maintainers, debating trade-offs publicly. Those are leadership behaviors in disguise. A Meta AI recruiter, speaking to Interview Node, said: "We don't care about stars. We care whether your pull requests show you learn, iterate, and improve. That's the mindset we hire for."

Alchemy applies the same logic to blockchain infrastructure. A community guide — "JOBS‑OS‑2026‑LILY" tells applicants: "Speak Their Language." Before each interview, candidates absorb Alchemy's mission, map every question to the company's framework, answer with stories reframed in Alchemy's context. The goal: make the interviewer think, "This person already works here." That means extracting Alchemy's top values verbatim, adopting their phrasing, understanding their scaling challenges, and showing how past open-source work maps to the protocol problems Alchemy solves daily.

The signal is specific. Backend infrastructure, testing frameworks, or data tools show transferable skills, blockchain-native or not. Personal projects with community adoption or meaningful feedback count equally. Interviewers read GitHub like a system-design diagram: structure, clarity, judgment. They check pull-request history, issue discussions, commit quality for professionalism and collaboration. Presentation matters: pin three to four impactful repos, write clear READMEs, use concise commit messages, archive inactive experiments.

The biggest mistake: chasing brand-name projects — PyTorch, TensorFlow, Ethereum core, with minimal ownership. Interviewers value outcomes over logos. A doc fix that unblocked a maintainer, a bug report with a reproducible test case, an example notebook that accelerated onboarding: these say you improve what you use. Frame contributions as collaborative, not ego-driven. "I collaborated with maintainers to address a recurring issue and proposed a patch refined through review" beats "I fixed an issue the maintainers missed." Unmerged work counts if framed honestly: a rejected PR that led to profiling, a discovered I/O bottleneck, a resubmission with benchmarks, that's growth under review, not failure.

For engineers without corporate blockchain experience, impactful open-source work proves skill, reliability, collaboration. Many companies now treat strong contributors as peers to mid-level engineers who've shipped internal tools. The guide's final note captures the stakes: "You're not there to prove you can code. You're there to explain how you already make code better for others."

Market Impact: Pay Jumps, Skepticism Lingers

Candidates prepare differently. Glassdoor reviews show consistent themes: deep protocol knowledge, practical coding tests, system-design prompts on API reliability at scale. The PM Interview Playbook includes Alchemy-specific debriefs. Negotiation scripts isolate each component: base anchored to ConsenSys and Chainlink, equity tranche schedules, bonus tied to product-line profitability not individual OKRs, sign-on bonuses framed as risk-adjustment for the 12-month equity liquidity ramp. One shared script asks hiring managers to model a 0.04% grant at $2.2B valuation, testing whether the recruiter can translate percentage into dollars.

Community sentiment splits. Reddit debates whether seasonal hiring surges apply to Web3 or mask pipeline-building. The 2023 layoffs — one in four staff, still echo in backchannels; some see a rebound play, others a volatility hedge. Alchemy's mentorship and high-stakes project exposure draw early-career talent, but seniors weigh crypto-market dependency and regulatory overhang from the company's own SWOT. The hiring push hasn't erased that tension, it's made compensation the primary filter for who stays in the process.

Clearing the Screen: Protocol, Systems, Proof

Alchemy's screen rewards candidates who treat blockchain infrastructure as a systems discipline, not a buzzword. Recruiters and recent hires name three preparation vectors: protocol fluency, design rigor, proven open-source work. The company's interview guides structure the loop around practical coding and architecture discussions mirroring daily production problems.

Start with fundamentals. The screen assumes you can explain Ethereum's execution model, gas mechanics, state roots vs receipt roots without documentation. Successful candidates spend weeks reading the Yellow Paper, consensus-specs, Erigon or Geth codebases, not tutorials, the implementations. Recent hires report building minimal EVM tracers to internalize opcode semantics; others cited client sync PRs onsite. The salary bands reflect the premium on this depth.

Systems design at Alchemy skips generic "design Twitter." Interviewers check whether you identify bottlenecks — connection pooling, backpressure, idempotency keys, and defend trade-offs between consistency and availability in a Byzantine environment. The dataford.io guide lists recent prompts; candidates who study them advance.

Open-source contributions carry outsized weight. Engineers with merged PRs in Ethereum clients, foundational libraries, or Alchemy's SDKs skip the phone screen. No merged work? Threads advise opening draft PRs, fixing a lint warning, adding a test case, documenting an undocumented RPC method, and treating the review cycle as behavioral-round rehearsal. Recruiters check GitHub before the first call; a sparse profile of tutorial forks signals low signal.

The coding test uses Alchemy's control plane and SDK languages. Practice a concurrent-safe LRU cache, a circuit breaker with exponential backoff, a Merkle proof verifier, all appear in recent screens. Time-box each; interviewers penalize perfect-but-late solutions.

Behavioral questions probe maturity: "Describe a production incident you owned end-to-end," "How do you decide rollback vs patch-forward?" Candidates citing metrics, p99 latency before/after, burn rate, action items, score higher than those narrating heroics without data.

Align your narrative with Alchemy's product. Live listings — Director of Engineering, Infrastructure & Platform; Data Analytics Engineer; Account Executive, Solana, show emphasis on multi-chain reliability and tool ergonomics. Reference the alchemy_notify webhook architecture or the eth_getBlockReceipts optimization. It proves you've read the docs, not just the job description.

Eighteen roles. Multiple filters. One GitHub profile that proves you've already done the work.

Working in frontier tech? Zero G Talent tracks the openings: see every open Alchemy role, browse frontier tech jobs, the companies hiring, and the people building the field.