Web3 Business Development jobs: How much technical depth do you actually need? (Analyzing a real JD)
I was looking at an active JD today for a Web3 Business Development Manager at a DeAI/DePIN data protocol, and it brought up a debate we see here a lot: how technical does a BD actually need to be to get deals done?
They are looking for someone to expand their ecosystem. They want 5+ years of traditional Enterprise Data/PaaS or Web3 sales experience, but they also explicitly require a "solid technical foundation" to align partnerships directly with their engineering roadmap.
It highlights the massive gap between traditional Web2 SaaS sales and Web3 partnerships manager responsibilities. It got me thinking:
The Technical Reality: If you are doing BD for infrastructure or data protocols, can you actually close a partnership without being able to read architecture docs or explain consensus models to a CTO?
The Hiring Reality: For the founders here—is it easier to hire a killer Web2 enterprise sales rep and teach them DePIN/DeFi, or hire a Web3 native and teach them pipeline discipline?
Curious to hear from the BDs and founders in the community. What does the day-to-day actually look like for you, and where is the line drawn on technical knowledge?