- Company Name
- LoopMe
- Job Title
- Vice President, Enterprise Sales
- Job Description
-
<think>
Alright, let's tackle this query. The user wants to normalize a job description into a concise mini-job profile for job matching. First, I need to understand the structure they want. The example response shows specific sections: Job Title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications. They want it in English, translated if needed, under 500 words, excluding company details, location, benefits, and fluff.
Looking at the job posting for Vice President, Enterprise Sales at LoopMe. The company uses AI in digital advertising. The role is for a VP to scale their Curation and AMP platforms. The core responsibilities include owning the enterprise platform business, building partnerships, scaling the platform, and leading the team. Requirements mention 10+ years of experience in ad tech, revenue targets, and team leadership.
I need to extract the essential info without company fluff. Let me start with the job title. Then the role summary should encapsulate the main purpose. Expectations would be the core what they're looking for. Key responsibilities are the tasks. Required skills are the qualifications. Education and certifications, though none are specified here, so maybe just note relevant education.
Wait, the job description mentions a degree in business or tech as part of requirements? Let me check. The original job description under Requirements says "senior ad tech leader with experience across programmatic, curation, audience measurement, and marketplace platforms" but no formal education mentioned. So maybe just say "Relevant bachelor’s or master’s degree in Business, Technology, or related field" as a placeholder since it's common for senior roles, but the user might not want assumptions. Wait, the user instructions say to exclude fluff and provide factual info. Since the job description doesn't specify education, maybe omit it. But the example response has a section, so perhaps infer based on the role. Hmm. The example response included "Relevant bachelor’s or master’s degree in Business, Technology, or related field" for a VP role. Since the user example includes it even if the original job description doesn't, perhaps they expect that. Maybe the user wants it inferred. But maybe not. The user's instruction says "exclude fluff" but also include "Required Education & Certifications" as a section. Since the job description doesn't mention any, perhaps leave it blank. But in the example response, they included it. Maybe it's better to infer based on the role's seniority. Since it's a VP, it's expected to have a bachelor's. But the user might prefer to only include what's in the job description. Let me check the job description again. The "Who You Are" section under Requirements mentions a senior ad tech leader with 10+ years, but no specific education. So perhaps just leave it as "Not specified" or omit. However, the example provided by the user includes it, so maybe the user expects a standard placeholder. Let's go with the example and include a standard one.
Now, the required skills: the job requires experience in programmatic, curation, audience measurement, marketplace platforms; revenue targets; team leadership; building partnerships; global team management; etc. Need to condense that into a concise list.
Key responsibilities: owning the business, developing GTM strategy, driving adoption, strategic partnerships, defining metrics, shaping roadmap, cross-functional collaboration, leading the team.
Expectations would be the core expectations, maybe the key responsibilities but phrased differently. Wait, the user wants separate sections: Role Summary, Expectations, Key Responsibilities. Wait, let me check the example structure again. The example has Role Summary, Expectations, Key Responsibilities, etc. Wait, in the example response, it's:
Role Summary: [concise summary]
Expactations: [list of expectations]
Key Responsibilities: [list]
Required Skills: [list]
Required Education & Certifications: [list]
Wait, in the example, the user wrote "Expactations" (probably a typo for Expectations). The user's example is from a similar role. Let me make sure. The user's example has:
Role Summary: Lead and scale enterprise platform business...
Expectations: Own the Enterprise Platform Business, Build Strategic Partnerships... [but maybe the example's expectations align with the core responsibilities? Hmm, maybe the user wants Expectations as the key expectations for the candidate, like required experience, etc. Wait, need to clarify.
Looking at the original instruction: The user says "Provide a concise summary for job matching. Max 500 words. Exclude company details, location, benefits, or fluff. Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications."
So the sections are to be:
Job title, Role Summary, Expectations, Key Responsibilities, Required Skills, Required Education & Certifications.
So "Expectations" might be the things the candidate must meet, like experience, skills, etc. Whereas Key Responsibilities are the tasks.
But the example from the user's own response (the one they provided after the query) shows under Expectations: "10+ years in ad tech leadership... Proven track record... Strategic leadership..." which seems like the required experience and expectations from the candidate. Then Key Responsibilities are the tasks they need to perform.
So in the user's sample, the Expectations are more about the qualifications and experience the candidate must have, while Key Responsibilities are the job tasks.
Therefore, in this case, the Expectations section should list the candidate's required experience and background. For example, "10+ years of delivering revenue $25M ARR+" etc.
So let's structure that. The original job description under "Who You Are" has:
- Senior ad tech leader with experience across programmatic, curation, audience measurement, and marketplace platforms
- 10+ years of delivering revenue $25M ARR+
- Proven in scaling enterprise-facing products...
- Proven success in building, mentoring and leading global teams...
- Comfortable working directly with strategic app developers...
- Commercially minded, highly collaborative, and metrics-driven
- Able to operate at strategic and hands-on levels with executive presence
These points should go into Expectations. So "Expectations" would be the candidate's required background and experience.
Key Responsibilities would be the tasks: own enterprise platform business, develop GTM strategy, drive adoption, etc.
Required Skills: programmatic, curation, audience measurement, marketplace platforms, revenue targets, team leadership, strategic partnerships, global management.
Required Education & Certifications: Since not specified, maybe "Not specified" or infer based on the role. The example included "Relevant bachelor’s or master’s degree in Business..." So maybe follow that standard.
Putting it all together concisely, making sure to stay under 500 words, excluding fluff, and using the required sections. Avoid any ATS-unfriendly words. Use bullet points where possible, but the user example uses commas-separated lists in some sections. Wait, the example uses bullet points for Key Responsibilities but commas for others. Let me check the example again. In the example, under Key Responsibilities, they used commas to separate each point. Hmm, perhaps use bullet points (dashes) as the user's example does.
Wait, the user's example uses:
Role Summary: [sentence]
Expectations: [list with bullet points? Or commas?] Wait, in the actual example the user provided, it's:
Role Summary: Lead and scale enterprise platform business...
Expectations:
- 10+ years in ad tech leadership...
- Proven track record in...
- Strategic leadership in...
Key Responsibilities:
- Own enterprise platform business...
- Develop GTM strategy...
So bullet points with dashes. Therefore, use dashes for each point in the sections.
But the user's instruction says "Provide a concise summary for job matching. Max 500 words. Exclude company details, location, benefits, or fluff. Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications."
So the sections are to be bullet points or commas? The example uses comma-separated lists in some sections. Wait, no, looking at the example, the user's example response uses dashes for each bullet point. For example:
Role Summary: [sentence]
Expectations:
- 10+ years...
- Proven track record...
Key Responsibilities:
- Own enterprise...
- Develop GTM strategy...
Etc. So using dashes as bullet points.
Therefore, format each section with dashes for each item, keeping it clear and concise.
Now, translating the job description into that structure, ensuring that the required sections are covered without company fluff, location, benefits, etc. So, for the Role Summary:
LoopMe seeks a VP of Enterprise Platforms to lead and scale Curation and AMP businesses. This role drives enterprise adoption, revenue growth, and strategic partnerships across curated supply and audience measurement. The VP defines go-to-market strategies and ensures platform innovation to differentiate LoopMe for enterprise buyers and premium app developers.
Expectations:
- Minimum of 10 years in senior ad tech leadership with focus on programmatic, curation, audience measurement, and marketplace platforms.
- Demonstrated ability to achieve $25M ARR+ revenue through scaling enterprise-facing solutions connecting supply, demand, and data.
- Proven leadership in building and mentoring global/distributed teams to meet revenue targets.
- Experience in strategic partnership development with enterprise buyers and premium consumer app developers.
- Strong commercial acumen, cross-functional collaboration, and metrics-driven approach.
Key Responsibilities:
- Own enterprise platform business: drive revenue growth, adoption, and performance of Curation and AMP platforms.
- Develop and execute enterprise GTM strategies for curated supply and audience measurement solutions.
- Foster strategic relationships with enterprise partners and app developers to align measurement and monetization.
- Define metrics, benchmarks, and roadmaps for scaling platform capabilities.
-
San francisco, United states
Hybrid
Senior
10-03-2026