Want to know if this job is worth applying to?
Remote, Oregon, United States
Remote only
Location: Remote
Employment: Full-Time
Start Date: ASAP
Experience: 5+ years
Language: Fluent English required | French is a PLUS
Industry: Cloud Infrastructure / GPU Compute / AI Infrastructure
You are the technical owner of our B2B customers, from the first call to production and every month after. You run discovery, design the setup, prove it in a POC, onboard it and keep it healthy. At its core this is a pre-sales and technical account management role. You know our stack well enough toanswer most customer questions yourself, and you bring in our engineers only for the deep end, with thecontext and first diagnosis already done.This is a new, hands-on individual contributor role. No quota. You work side by side with sales and reportto the Compute product lead. Today the product lead covers this job on top of product, while newcustomer channels open at three times the pace of earlier this year.
Responsibilities
What you'll do
Pre-sales
Run technical discovery with customers' engineers: workload, models, serving stack, latency and throughput targets, storage, network, security and data-residency constraints.
Turn that into the right setup and size it: model to GPUs, CPU, RAM, NVMe and network per server, and bare metal vs full-server VM vs instances vs managed inference.
Answer technical due diligence: bill of materials, PCIe topology, NICs and network design,out-of-band access, data-centre power and connectivity, security and compliancequestionnaires. You answer most of it yourself, with infrastructure and security behind you forthe deep end.
Represent us in enterprise and public-sector workshops, mapping our stack against theirs: Kubernetes, identity, logging, storage APIs, integration.
Check every technical commitment before it reaches a contract: SLA, performance minimums, acceptance tests, dates for roadmap features.
Proofs of concept
Design each POC with written success criteria, a timebox, reserved capacity and a data-handling plan.
Run the benchmarks with the customer, using standard tools (NCCL tests, fio, vLLM or SGLang load tests) or their own method. Write up the results and the go or no-go.
Onboarding
Own technical onboarding end to end: accounts and access, private networking, public IPs and firewalling, load balancing, storage, server handover against an acceptance checklist, first workload live.
Work with infrastructure on new server batches, from burn-in to handover.
Running accounts
Be the technical owner for a portfolio of enterprise accounts after go-live. First line on their technical questions. Triage to SRE and infrastructure with full context, and own each issue to root cause and closure, not to the reboot.
Lead incident communication, write customer-facing RCAs, report uptime against each SLA, run monthly technical reviews, and plan maintenance with customers across time zones.
Spot risk early (repeat hardware failures, firmware and security advisories, capacity gaps) and flag it to the account team.
Building the playbook
Turn repeat work into assets: a technical due-diligence pack, a POC playbook, onboarding docs, reference architectures for shared storage, private networking and inference at scale.
Bring customer requirements back to product and engineering, with evidence.
How you work with the team
Sales wins accounts; you make them work. Every deal sales closes lands with you, and you are in the room before it closes so the contract matches what we can deliver.
Sales owns relationships, pricing, contracts and quota.
Support handles day-to-day tickets. SRE and infrastructure fix the platform and the fleet. They respond to issues; you get ahead of them and own the customer side end to end.
Product and engineering get the customer's voice from you, backed by data.
What the role is not: a quota-carrying sales role, a support queue, an on-call SRE rotation, or a people-management role.
How we measure success
We measure you on time to first workload, POC conversion, and escalations avoided: the customer questions you close without pulling in engineering, and how often we catch a problem before thecustomer does.
Your first 90 days:
First month: learn the platform and the fleet, take over the technical side of our live enterprise accounts and the POCs in flight, and own onboarding for December's new server deliveries. By the end of it, you run your portfolio on your own.
By day 60: a POC playbook and a technical due-diligence pack are live and in use.
By day 90: every enterprise account has a monthly technical review and an uptime report against its SLA, and the first reference architectures are published.
Pragmatike is an Equal Opportunity Employer and is committed to providing equal employment opportunities to all applicants without discrimination. We recruit on behalf of our clients and prohibit discrimination and harassment based on race, color, religion, age, sex, national origin, disability status, genetics, protected veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by federal, state, or local laws. This policy applies to all terms and conditions of employment, including recruiting, hiring, placement, promotion, termination, layoff, recall, transfer, leaves of absence, compensation, and training.We are committed to a fair and inclusive hiring process. We process your personal data solely for recruitment purposes, in accordance with applicable privacy laws, and maintain reasonable safeguards to protect your information. Your data may be shared with our client(s) for hiring consideration, but will not be disclosed to third parties outside of the recruitment process.
