- Company Name
- Celonis
- Job Title
- Business Development Representative (SaaS Sales)
- Job Description
-
<think>
Okay, let's tackle this job description normalization. The user wants a concise job profile for matching. First, I need to parse through the given job description and extract the necessary elements.
The title is clear: Business Development Representative (SaaS Sales). Now, the role summary. The main points are about the Business Development Team's role in growth and expanding market presence by engaging decision-makers. The Role section says the BDR's main focus is identifying and creating opportunities for Account Executives in specific verticals in the US. I need to condense that into a one-sentence summary.
Next, expectations. The job mentions evangelizing the platform, strategic prospecting, generating pipeline, owning territory, partnering with sales and marketing, and supporting complex sales cycles. Those are the key responsibilities. I should list them clearly but concisely.
Qualifications include a BA/BS, 1-3 years in SaaS sales, communication skills, adaptability, results-driven attitude, and being coachable. Need to make sure these are translated into a skills section with required education and certifications. The education is BA/BS or equivalent.
I have to exclude company details, location (hybrid role, 3 days in-office is mentioned but the user said to exclude location), benefits, and any fluff. Also, visa sponsorship is noted but since location is excluded, maybe just mention that it's a hybrid role briefly? Wait, the user said to exclude location, so maybe not include the hybrid part. Wait, the instructions say to exclude location, benefits, or fluff. So the hybrid part is under location, so it should be excluded.
Check the required fields: Job title, Role Summary, Expectations (maybe renamed Key Responsibilities?), Expactations (probably a typo, should be Expectations?), Required Skills, Education & Certifications. Wait, the user wrote "Expactations", probably a typo for "Expectations". So need to correct that. Let me confirm the user's exact output fields.
User's output fields: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications. The typo might be intentional, but since the user provided "Expactations", I need to use it as is. But maybe that's a mistake. Let me see the user's input again. Looking at the user's problem statement: "Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications." So "Expactations" is likely a typo, but I have to follow as per user's instruction. Hmm, maybe the user intended "Expectations". But the typo is there. I need to output "Expactations" as written. Maybe the user made a mistake, but it's better to follow their exact output format.
Wait, looking at the user's instruction again. They wrote: "Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications." So "Expactations" is part of the output. But that's a typo. Maybe "Expectations"? But the user wrote it as Expactations. Should I correct it or keep as is? The user might have meant "Expectations", but since they wrote it with a typo, I should output it as they specified. Maybe the user wants to test if I can process the typo correctly. So I need to use the exact words given.
Now, moving on. Let's structure each section.
Role Summary: Should be a short summary. Original description mentions being on the front lines of growth, expanding market presence, identifying key decision-makers. So the Role Summary would be concise.
Expactations (Expectations?) but user said to follow their typo. The user's original job description mentions the work you'll do, which includes evangelizing, prospecting, generating pipeline, owning territory, collaborating with sales & marketing, supporting sales cycles. These are the key responsibilities.
Key Responsibilities: The same as the work you'll do. Maybe rephrase each point.
Required Skills: The qualifications include communication, adaptability, results-driven attitude, coachable, etc. Need to list them.
Education & Certifications: BA/BS from a top university or equivalent. The user said to exclude location, so not including the part about 3 days in-office.
I need to make sure everything is under 500 words. Let me check the original job description. The user's example response is concise, so I should aim for a similar structure.
Also, the user wants it ATS-friendly and globally neutral. So avoid any region-specific terms unless necessary.
So, putting it all together:
Job Title: Business Development Representative (SaaS Sales)
Role Summary: Lead enterprise business development by identifying and engaging key decision-makers, expanding market presence in specific US verticals for Account Executives.
Expactations (Expectations):
- Evangelize Celonis Process Intelligence Platform to new and existing customers.
- Strategically prospect using cold outreach and social channels to connect with prospects.
- Generate high-quality leads and build a robust pipeline for Account Executives.
- Manage assigned territory by developing new accounts and deepening existing customer relationships.
- Collaborate with sales and marketing teams on account-based strategies and campaigns.
- Navigate complex enterprise sales cycles to secure cross-departmental buy-in.
Key Responsibilities:
The responsibilities would be similar to Expactations, but maybe they want a separate section titled Key Responsibilities. Wait, in the user's output structure, after Expactations comes Key Responsibilities. But the user's example might combine both? Wait, the user's output structure is Role Summary, Expactations, Key Responsibilities. Maybe "Expactations" is a typo for "Expectations", and "Key Responsibilities" is the actual list. But the user might have meant to have "Expectations" (what they expect from the candidate) and "Key Responsibilities" (what the job entails). But according to the user's instruction, the output is: Role Summary, Expactations, Key Responsibilities, etc. So perhaps the Expactations are the expectations from the candidate, but the user's job description doesn't have that. Wait, the user's job description under the qualifications mentions what the candidate should have (skills, education, etc.), so maybe Expactations here refers to the requirements for the job, which is what the user calls "Expactations" but actually refers to the candidate's qualifications. But the user also has a separate section for Required Skills and Education. So I think the structure intended is:
- Role Summary: high-level overview of the role.
- Expactations (Expectations): the responsibilities and what the role entails.
- Key Responsibilities: same as above? Or maybe the Key Responsibilities is the actual list of what the job involves, and Expactations refers to the qualifications or what the company expects from the applicant? The user's job description says under "The work you'll do" which lists the responsibilities, which in the user's output should be under Expactations or Key Responsibilities. But since the user's instruction lists both Expactations and Key Responsibilities, maybe they are redundant. However, the user's example output has "Expactations" and "Key Responsibilities" as separate sections, so perhaps they are different. Wait, looking back, the user says "Expectations" refers to the qualifications? That doesn't make sense. Maybe the user made a mistake in their own structure. Alternatively, perhaps "Expactations" is meant to be "Expectations", and then Key Responsibilities are the duties. Alternatively, since the user has written "Expactations", maybe it's a typo for "Expectations" and they meant the expectations from the candidate, but the Required Skills and Education already cover that. This is confusing. Let me check the user's instruction again.
The user's instruction says: Output only: Job title, Role Summary, Expactations, Key Responsibilities, Required Skills, Required Education & Certifications.
So the sections are:
1. Role Summary
2. Expactations (Expectations)
3. Key Responsibilities
4. Required Skills
5. Required Education & Certifications
So maybe "Expactations" is a typo, and the correct section is "Expectations", perhaps referring to the candidate's expectations. But in the job description, the responsibilities are listed. Alternatively, maybe "Expactations" is meant to list the expectations from the candidate (i.e., what's expected of them), which would be the responsibilities.
But the user's job description has a section titled "The work you’ll do" which lists the responsibilities, which would map to "Expactations" and "Key Responsibilities", perhaps. However, since the user wants separate sections, perhaps "Expactations" is the expectations that the company has (i.e., what they expect the candidate to do), and "Key Responsibilities" is the same list? Maybe the user wants two sections with the same content. That might be a mistake. Alternatively, it's possible that "Expactations" is a typo for "Expectations" and "Key Responsibilities" is a separate list. Since the user has provided the instruction, I'll follow it as given, even if there's redundancy. So under "Expactations", list the main responsibilities, and under "Key Responsibilities", perhaps more detailed responsibilities.
But looking at the example given in the user's problem statement, the sample output (though not shown here) likely combines responsibilities into one section. Wait, the user's example response in the instructions is hypothetical, but since I can't see it, I need to rely on the user's own structure.
Given the confusion between "Expactations" and "Key Responsibilities", and since the job description lists the "work you’ll do" as the responsibilities, it's likely that "Expactations" refers to the expectations (duties) while "Key Responsibilities" is redundant. However, given the user's instruction, I have to
Raleigh-durham-chapel hill, United states
Hybrid
Fresher
16-03-2026