Menu

How I Debugged Expensify Bugs & Got Paid
📰

How I Debugged Expensify Bugs & Got Paid

DEV Community: career·Tushar Bhendarkar·3 days ago
#HEqLcir1
#devtocareer#devto#dev#expensify#bugs
Reading 0:00
15s threshold

Expensify paid me $500 for fixing two bugs in their app. I don't work there. Nobody assigned me the work. I found the bugs on GitHub, wrote up the root causes, and my fixes were merged into a React Native app used by more than 10 million people.

The money is the hook, but it's not the story. The story is what it takes to get a fix merged into a codebase that size when nobody knows who you are. Here is how both bugs went down, plus two investigations that never became PRs but taught me just as much. (The contracts, payments and review are in the Expensify case study .)

How Expensify's bounty system works

Expensify runs one of the most open contributor programs of any production app. Bugs are filed as public GitHub issues, most carry a bounty (typically $250), and anyone can submit a proposal: a written explanation of the root cause and the fix you intend to make.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.