Business Development, Elastic Compute

We're looking for someone who knows how to find customers before they find us. The focus is Zenlayer Elastic Compute — our cloud infrastructure platform — targeting companies whose businesses are built on moving a lot of traffic. These buyers have real technical requirements and tend to be skeptical of vendor claims. Your job is to get into the communities where they operate, build credibility, surface qualified opportunities, and feed intelligence back internally so we're building and positioning the right things.

Zenlayer has real infrastructure advantages for high-traffic, globally distributed workloads — particularly in Southeast Asia, the Middle East, and Latin America where hyperscaler coverage is thin. For the right buyer, the product genuinely fits. The gap is awareness, and that's what this role exists to fix.

Duties & Responsibilities:

Map the ecosystem — forums, communities, conferences, private groups — and build a recognizable presence wherever high-traffic operators actually talk to each other

Generate pipeline through outreach, community participation, events, and referral relationships, handing qualified opportunities to sales with enough context to close

Build and maintain relationships with resellers, ISVs, and channel partners, with the goal of having 2–3 actively sourcing leads within the first year

Develop a clear read on where Zenlayer wins and loses in the market, and bring that intelligence back to product and marketing in a form the team can act on

Work with product and marketing to develop positioning and materials that resonate with technically sophisticated buyers

Required Qualifications:

Experience in cloud infrastructure, networking, or a closely adjacent space — technically credible enough to earn the first conversation without backup, and curious enough to go deeper as deals develop

A demonstrated ability to build pipeline from cold

Strong instincts for where to find buyers and how to get their attention 

Comfortable operating without a lot of structure; this is an early-stage function and you'll be setting up the playbook, not inheriting one