Job Seeking
Cloud infrastructure sales can involve compute, storage, networking, infrastructure management, migration services and support. Identify exactly what an employer sells: provider capacity, a managed service, consulting or software that helps customers operate infrastructure. AWS, Azure, GCP and IaaS are useful search terms, not interchangeable job descriptions.
Potential stakeholders include infrastructure leaders, platform engineers, security teams, finance, procurement and application owners. A sales cycle may involve workload assessment, architecture review, testing, security approval and purchasing. Ask which steps are typical for the employer’s customers rather than assuming every cloud deal follows one sequence.
Start with Salesfolks sales jobs and employer career pages. Try specific searches: “cloud infrastructure SDR,” “IaaS account executive,” “cloud consumption account manager,” “managed cloud sales” and “cloud migration sales.” Add your preferred customer segment or vertical, such as enterprise or healthcare, when relevant.
Build a shortlist with columns for product, customer, role, territory and technical support. Distinguish a cloud provider from a reseller, managed service provider or infrastructure software vendor; the same title can describe different selling work.
For United States roles, verify eligible work locations, remote-state restrictions, time-zone coverage, travel and territory boundaries in the current posting or with the recruiter. Assess industry fit through customer examples and product documentation. Ask whether you would sell into an existing network of accounts or build a new territory.
Your resume should separate personal results from team outcomes. Describe the customer segment, product, sales motion, quota period and your contribution. Include attainment or revenue only when accurate and shareable. If you lack cloud experience, show transferable evidence: complex discovery, technical coordination, recurring-revenue sales or disciplined prospecting.
Prepare a one-page scenario: a hypothetical business wants to move an application from its own servers to a cloud environment. Do not present the exercise as a real customer win.
AWS describes security responsibilities as divided between provider and customer, with customer obligations depending on the selected service; consult its shared responsibility model. Do not apply that vendor’s model universally. Finish your exercise with open questions and a proposed technical discovery meeting, not an unsupported savings promise.
Request the written compensation plan before accepting. Separate guaranteed base pay from variable compensation and understand what earns credit: signed contracts, booked commitments, consumption, renewals or another measure. An on-target earnings figure is not guaranteed income.
For a wage benchmark, use the BLS occupational wage tables. Read occupation descriptions to choose the closest match to the actual duties, then select the relevant geography and available year. Do not treat a broad national occupation as a local cloud-sales salary quote or assume its wage measure matches the offer’s base-plus-variable structure.
Test how the job works, not just whether the product sounds interesting. Ask the manager for a recent, anonymized deal walkthrough: buyer, trigger, technical validation, approval process and reasons for delay. Clarify whether sales engineering, partner teams and customer success are available throughout the cycle.
Compare answers across the recruiter, manager and a prospective peer. Request clarification when definitions differ, particularly around pipeline ownership and account coverage.
One unclear answer warrants follow-up, not an automatic rejection. Repeated contradictions about territory, pay or support deserve greater caution.
Use the same checklist for every offer. Mark each item confirmed, unresolved or unacceptable, and record the written evidence.
For example, hypothetical Offer A has higher advertised earnings but an unresolved territory and consumption-based crediting. Hypothetical Offer B has lower advertised earnings, named accounts and documented ramp terms. Neither is automatically better. Compare the uncertainty you can tolerate, your household needs and the selling motion you can execute. Ask each employer to resolve missing terms before deciding.
Track applications by role fit and unresolved questions, not just submission count.
Check each posting. A certification may support your preparation, but ask which credentials are required. Demonstrate discovery judgment and accurate technical boundaries regardless.
Yes, consider roles that match your selling motion. Explain transferable work with multiple stakeholders, recurring revenue or technical specialists, and show how you are closing knowledge gaps.
Do not assume so. Confirm approved work locations, customer travel, time-zone expectations and whether the territory could change after you join.
Use O*NET to research occupation tasks and skills, then compare them with actual postings. Verify current compensation benchmarks through BLS and service responsibilities through the relevant vendor’s documentation. Employer-specific terms require direct confirmation, ideally in writing.
Next, browse sales jobs or create a Salesfolks account. Bring your shortlist, work sample and unanswered questions to each application and interview.
Employer perspective: Hiring Cloud Infrastructure Salespeople: A Practical Employer Guide.