Account Executive - Mid Market
Oracle · Chicago, IL · 1 mo ago
Sales$25.29–$40.43/hrFull-time
We need to output HTML fragment with sections: About the Team? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content. The posting includes: "About the Team:" but not "About the role". There's a job description paragraph at top: "You have a minimum of 3 years of SaaS/Technology sales..." That's about the role? Could treat as About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we can create sections based on content present.
We have:
- Intro paragraph: "You have a minimum of 3 years of SaaS/Technology sales and a desire to succeed. A strong understanding of accounting solutions, business solutions, ecommerce, ERP or CRM in a sales capacity is essential, as well as the ability to negotiate pricing and contractual terms to close a sale. You are a regular on your company’s top producer’s list and have the stats to back it up. You are known for your tremendous work ethic, laser focus, passion, and dedication. You enjoy learning technology and can translate that into value for prospects. You’re curious, insightful, and perceptive." This is basically qualifications/requirements. Could be under "Requirements" or "Qualifications". We'll decide.
- "About the Team:" paragraph: "We value outstanding writing skills and a friendly, thoughtful, and effective communication style. We strive for attention to detail, emotional intelligence, and quick turnaround times. We get stuff done. And fast." That's about the team; could be "About the Team" but not in list of allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Team" not allowed. Could map to "About the role"? Might be okay to treat as "About the role"? But it's about team. However we must only use allowed headings. Could we omit that section? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". We can choose not to include a heading for About the Team if not allowed. But we need to preserve ALL substantive information; we cannot drop content. So we need to embed that content somewhere else, maybe under "About the role" or "Qualifications". Since "About the Team" is about team values, could fit under "About the role" as description of role environment. We'll put it under
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we can create sections based on content present.
We have:
- Intro paragraph: "You have a minimum of 3 years of SaaS/Technology sales and a desire to succeed. A strong understanding of accounting solutions, business solutions, ecommerce, ERP or CRM in a sales capacity is essential, as well as the ability to negotiate pricing and contractual terms to close a sale. You are a regular on your company’s top producer’s list and have the stats to back it up. You are known for your tremendous work ethic, laser focus, passion, and dedication. You enjoy learning technology and can translate that into value for prospects. You’re curious, insightful, and perceptive." This is basically qualifications/requirements. Could be under "Requirements" or "Qualifications". We'll decide.
- "About the Team:" paragraph: "We value outstanding writing skills and a friendly, thoughtful, and effective communication style. We strive for attention to detail, emotional intelligence, and quick turnaround times. We get stuff done. And fast." That's about the team; could be "About the Team" but not in list of allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Team" not allowed. Could map to "About the role"? Might be okay to treat as "About the role"? But it's about team. However we must only use allowed headings. Could we omit that section? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". We can choose not to include a heading for About the Team if not allowed. But we need to preserve ALL substantive information; we cannot drop content. So we need to embed that content somewhere else, maybe under "About the role" or "Qualifications". Since "About the Team" is about team values, could fit under "About the role" as description of role environment. We'll put it under About the role
and include that paragraph.
- Travel: Up to 25% - This is schedule/travel info. Could be under Schedule? The posting includes Travel: Up to 25%. That's schedule info. So we can create a Schedule section with that.
- Responsibilities: a block starting with "Responsibilities" then bullet-like sentences. We'll put under Responsibilities
with - each sentence.
- Qualifications: there is a "Qualifications" heading in the posting, then a disclaimer about US based roles etc. Then "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from $25.29 - $40.43 per hour; from: $52,600 - $84,100 per year. May be eligible for equity. Eligible for commission with an estimated pay mix of 50 / 50." Then details about Oracle maintains broad salary ranges... Then "Oracle US offers a comprehensive benefits package which includes the following:" then list of benefits. Then later: "The role will generally accept applications for at least three calendar days from the posting date or as long as the job remains posted." That's application instruction, we must remove. Then "As part of Oracle's onboarding process..." that's boilerplate, remove. Then "About Us" etc, remove. Then EEO etc, remove.
Thus we need to extract:
- Pay: The hiring range and commission info. So we need a Pay section with that info.
- Benefits: list of benefits.
- Possibly Skills? Not explicit. Could combine skills under Qualifications.
We must not create sections with filler like "commensurate with experience". We have actual pay range and benefits.
We must not include Job ID/requisition numbers.
We must not include application instructions, EEO, etc.
We must preserve all substantive information: that includes the intro paragraph, About the Team content, Travel, Responsibilities, Qualifications (including disclaimer about immunization etc?), Pay range, Benefits, etc. Also the note about "May be eligible for equity. Eligible for commission with an estimated pay mix of 50 / 50." and the statement about Oracle maintains broad salary ranges... That is substantive? It's explanation of range; we can keep.
We also have "Disclaimer: Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements." That's substantive; keep under Qualifications maybe.
We also have "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from $25.29 - $40.43 per hour; from: $52,600 - $84,100 per year." That's pay.
We also have "May be eligible for equity. Eligible for commission with an estimated pay mix of 50 / 50." That's pay.
We also have "Oracle maintains broad salary ranges for its roles in order to account for variations in knowledge, skills, experience, market conditions and locations, as well as reflect Oracle's differing products, industries and lines of business. Candidates are typically placed into the range based on the preceding factors as well as internal peer equity." That's also pay explanation.
We also have benefits list.
We also have "The role will generally accept applications for at least three calendar days from the posting date or as long as the job remains posted." That's application instruction; remove.
We also have "As part of Oracle's onboarding process and consistent with applicable law, US-based employees are required to complete identity verification, which involves the collection and processing of their biometric information. Accommodations to this requirement may be granted following an individualized assessment." That's boilerplate/legal; remove.
We also have "About Us" etc; remove.
We also have EEO etc; remove.
Thus final HTML will have sections: About the role (including intro paragraph and About the Team paragraph), Responsibilities, Qualifications (including disclaimer and maybe skills?), Pay, Benefits, Schedule (Travel). Possibly Skills not needed.
We need to use
- for any list of duties/requirements/benefits. So for Responsibilities we need list. For Benefits we need list. For Qualifications maybe list? The qualifications are more prose; we could keep as
. But if we have list of requirements (like "minimum of 3 years...") we could make list. However the instruction: use
- for any list of duties/requirements/benefits. If we have a list of requirements we should use list. The intro paragraph contains multiple sentences that could be considered requirements. Safer to convert to list.
Similarly, the About the Team paragraph could be list? Not required.
We'll decide:
- About the role: combine intro paragraph and About the Team paragraph into
maybe two paragraphs.
- Responsibilities:
- each sentence.
- Qualifications: include disclaimer and maybe the statement about "You have a minimum of 3 years..."? Actually we already used that in About the role. Might duplicate. Better to keep qualifications separate: maybe include the disclaimer and the statement about "You are a regular on your company’s top producer’s list..." etc. But we already used that in About the role. To avoid duplication, we need to decide where to place each piece. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include each piece somewhere. We can split: About the role includes the initial description of the role (maybe the first paragraph). Qualifications includes the disclaimer and maybe the statement about "You are a regular on your company’s top producer’s list..." etc. But that would duplicate content if we also put in About the role. Let's examine the original text:
"Job Description You have a minimum of 3 years of SaaS/Technology sales and a desire to succeed.A strong understanding of accounting solutions, business solutions, ecommerce, ERP or CRM in a sales capacity is essential, as well as the ability to negotiate pricing and contractual terms to close a sale.You are a regular on your company’s top producer’s list and have the stats to back it up.You are known for your tremendous work ethic, laser focus, passion, and dedication.You enjoy learning technology and can translate that into value for prospects.You’re curious, insightful, and perceptive. About the Team: We value outstanding writing skills and a friendly, thoughtful, and effective communication style.We strive for attention to detail, emotional intelligence, and quick turnaround times.We get stuff done. And fast. Travel: Up to 25% Responsibilities Works to achieve maximum sales profitability, growth, and account penetration within an assigned territory. Territory may be combination of geographic, product, industry and other customer / market dimensions. Sells to the territory directly or via partners. The territory that this rep covers does not have an Inside Sales Rep or Field Rep. Utilizes inbound and/or outbound techniques to identify, qualify and close new opportunities. Manages accounts throughout the entire sales process, and collaborates with team members in business development, consulting and support to uncover all customer needs. Responsible for understanding Oracle's product offerings and competitive issues to develop solution proposals encompassing all aspects of the application. Travels to customer sites to identify / develop sales opportunities. Participates in the development, presentation, and sales of a value proposition. Onsite customer presentation with C-levels to negotiate and close strategic and complex deals. Liaises with customer contacts for the purpose of managing the customer relationship, identifying new opportunities and maximizing sales. Qualifications Disclaimer: Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements. Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from $25.29 - $40.43 per hour; from: $52,600 - $84,100 per year. May be eligible for equity. Eligible for commission with an estimated pay mix of 50 / 50. Oracle maintains broad salary ranges for its roles in order to account for variations in knowledge, skills, experience, market conditions and locations, as well as reflect Oracle's differing products, industries and lines of business. Candidates are typically placed into the range based on the preceding factors as well as internal peer equity. Oracle US offers a comprehensive benefits package which includes the following: Medical, dental, and vision insurance, including expert medical opinion Short term disability and long term disability Life insurance and AD&D Supplemental life insurance (Employee/Spouse/Child) Health care and dependent care Flexible Spending Accounts Pre-tax commuter and parking benefits 401(k) Savings and Investment Plan with company match Paid time off: Flexible Vacation is provided to all eligible employees assigned to a salaried (non-overtime eligible) position. Accrued Vacation is provided to all other employees eligible for vacation benefits. For employees working at least 35 hours per week, the vacation accrual rate is 13 days annually for the first three years of employment and 18 days annually for subsequent years of employment. Vacation accrual is prorated for employees working between 20 and 34 hours per week. Employees working fewer than 20
- for any list of duties/requirements/benefits. So for Responsibilities we need list. For Benefits we need list. For Qualifications maybe list? The qualifications are more prose; we could keep as
. But if we have list of requirements (like "minimum of 3 years...") we could make list. However the instruction: use
- for any list of duties/requirements/benefits. If we have a list of requirements we should use list. The intro paragraph contains multiple sentences that could be considered requirements. Safer to convert to list.
Similarly, the About the Team paragraph could be list? Not required.
We'll decide:
- About the role: combine intro paragraph and About the Team paragraph into
maybe two paragraphs. - Responsibilities:
- each sentence. - Qualifications: include disclaimer and maybe the statement about "You have a minimum of 3 years..."? Actually we already used that in About the role. Might duplicate. Better to keep qualifications separate: maybe include the disclaimer and the statement about "You are a regular on your company’s top producer’s list..." etc. But we already used that in About the role. To avoid duplication, we need to decide where to place each piece. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include each piece somewhere. We can split: About the role includes the initial description of the role (maybe the first paragraph). Qualifications includes the disclaimer and maybe the statement about "You are a regular on your company’s top producer’s list..." etc. But that would duplicate content if we also put in About the role. Let's examine the original text: "Job Description You have a minimum of 3 years of SaaS/Technology sales and a desire to succeed.A strong understanding of accounting solutions, business solutions, ecommerce, ERP or CRM in a sales capacity is essential, as well as the ability to negotiate pricing and contractual terms to close a sale.You are a regular on your company’s top producer’s list and have the stats to back it up.You are known for your tremendous work ethic, laser focus, passion, and dedication.You enjoy learning technology and can translate that into value for prospects.You’re curious, insightful, and perceptive. About the Team: We value outstanding writing skills and a friendly, thoughtful, and effective communication style.We strive for attention to detail, emotional intelligence, and quick turnaround times.We get stuff done. And fast. Travel: Up to 25% Responsibilities Works to achieve maximum sales profitability, growth, and account penetration within an assigned territory. Territory may be combination of geographic, product, industry and other customer / market dimensions. Sells to the territory directly or via partners. The territory that this rep covers does not have an Inside Sales Rep or Field Rep. Utilizes inbound and/or outbound techniques to identify, qualify and close new opportunities. Manages accounts throughout the entire sales process, and collaborates with team members in business development, consulting and support to uncover all customer needs. Responsible for understanding Oracle's product offerings and competitive issues to develop solution proposals encompassing all aspects of the application. Travels to customer sites to identify / develop sales opportunities. Participates in the development, presentation, and sales of a value proposition. Onsite customer presentation with C-levels to negotiate and close strategic and complex deals. Liaises with customer contacts for the purpose of managing the customer relationship, identifying new opportunities and maximizing sales. Qualifications Disclaimer: Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements. Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from $25.29 - $40.43 per hour; from: $52,600 - $84,100 per year. May be eligible for equity. Eligible for commission with an estimated pay mix of 50 / 50. Oracle maintains broad salary ranges for its roles in order to account for variations in knowledge, skills, experience, market conditions and locations, as well as reflect Oracle's differing products, industries and lines of business. Candidates are typically placed into the range based on the preceding factors as well as internal peer equity. Oracle US offers a comprehensive benefits package which includes the following: Medical, dental, and vision insurance, including expert medical opinion Short term disability and long term disability Life insurance and AD&D Supplemental life insurance (Employee/Spouse/Child) Health care and dependent care Flexible Spending Accounts Pre-tax commuter and parking benefits 401(k) Savings and Investment Plan with company match Paid time off: Flexible Vacation is provided to all eligible employees assigned to a salaried (non-overtime eligible) position. Accrued Vacation is provided to all other employees eligible for vacation benefits. For employees working at least 35 hours per week, the vacation accrual rate is 13 days annually for the first three years of employment and 18 days annually for subsequent years of employment. Vacation accrual is prorated for employees working between 20 and 34 hours per week. Employees working fewer than 20
- for any list of duties/requirements/benefits. If we have a list of requirements we should use list. The intro paragraph contains multiple sentences that could be considered requirements. Safer to convert to list.
Similarly, the About the Team paragraph could be list? Not required.
We'll decide:
- About the role: combine intro paragraph and About the Team paragraph into