Solutions Engineer, Mid Market

We need to output HTML fragment with sections: Overview? The instructions: 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. We need to include sections only when posting has real specific content. The posting includes Overview (some generic about Atlassian), "Your future team", "Responsibilities", "Qualifications", "Compensation" (pay), "Benefits & Perks", "About Atlassian". Also maybe "Overview" could be considered "About the role"? But we have "Overview Working at Atlassian" and "Your future team". We can combine into an "About the role" section? The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have responsibilities list. Qualifications list. Compensation details (pay ranges). Benefits & Perks. About Atlassian (company overview). Also maybe "Overview" could be part of About the role. We must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO statement at end: "All your information will be kept confidential according to EEO guidelines...". Must remove that. Also "To provide you the best experience..." etc. Remove. Also "Please visit go.atlassian.com/payzones for more information..." is part of compensation; keep? It's a link but not boilerplate; it's info about pay zones. We can keep as part of compensation paragraph. "Please confirm the zone for your specific location with your recruiter." Keep. "To learn more, visit go.atlassian.com/perksandbenefits." Keep as part of benefits. "To learn more about our culture and hiring process, visit go.atlassian.com/crh." That's about Atlassian; keep. We need to output only HTML fragment, no markdown fences. Structure:

About the role

... combine overview and your future team paragraphs.

Responsibilities

• ... each responsibility line.

Qualifications

... maybe combine bullet points? The qualifications are a paragraph with multiple sentences. Could be

with sentences. Or we could break into

• but instruction: Use
  • for any list of duties/requirements/benefits. Qualifications is a list of requirements; we could treat as list. But the text is a paragraph with multiple sentences separated by periods. Might be better as

    . However instruction says use

    • for any list of duties/requirements/benefits. Qualifications are requirements, so we should use list. Let's split each sentence into
    • . Ensure we preserve all info. Qualifications sentences: - "Your Background: 3+ years of experience interacting with mid-market customers in a pre-sales capacity, with excellent communication, strong presentation skills to multi-level audiences, and unmatched agility to do what it takes to get the job done." - "You’re a creative problem solver who can interpret complex business problems, boil them down into solutions, and collaborate with prospects, partners, and the Atlassian sales team to deliver compelling value-based solutions." - "You’re equally comfortable in both a business and technical context, interacting with executives or talking shop with strong technical audiences." - "You love to learn and continuously grow and challenge yourself, are open to giving and receiving feedback, tolerate failure, love to win, hate to lose, and are passionate about making customers and Atlassian successful." - "If you’re looking to be a cog in the system, this job isn’t for you. You’ve got a customer-centric mindset, with a proven track record in building executive relationships with customers and rally the internal teams to collaborate across the company to meet our customers needs." We could split into separate
    • each sentence. Keep the content.

      Pay

      ... compensation paragraph with zones and note about benefits, bonuses, commissions, equity.

      Benefits

      ... Atlassian offers a wide range of perks and benefits... To learn more, visit go.atlassian.com/perksandbenefits.

      About Atlassian

      ... At Atlassian, we're motivated... To learn more about our culture and hiring process, visit go.atlassian.com/crh.

      We should not include Schedule section because not present. Check for any duplicated lines: The responsibilities section includes a first line that seems duplicated: "Responsibilities Responsibilities Join Atlassian’s Solutions Engineering Core Team..." Actually the text: "Responsibilities Responsibilities Join Atlassian’s Solutions Engineering Core Team..." It appears the word Responsibilities repeated. We need to preserve substantive information; we should not duplicate the heading. In the responsibilities paragraph we should start after the duplicated word. The raw text: "Responsibilities Responsibilities Join Atlassian’s Solutions Engineering Core Team to partner with direct sales, partners and larger account teams on Mid-Market Accounts, tracking the overall customer profile, business problems and complexities, roadmaps, and solution success to optimize the customers within your account team territory". Likely a mistake; we should output only one "Responsibilities" heading and then the paragraph starting "Join Atlassian’s Solutions Engineering Core Team...". So we need to remove the duplicate word. Similarly, there may be duplicated lines elsewhere; we need to check. Let's extract responsibilities lines from the posting: "Responsibilities Responsibilities Join Atlassian’s Solutions Engineering Core Team to partner with direct sales, partners and larger account teams on Mid-Market Accounts, tracking the overall customer profile, business problems and complexities, roadmaps, and solution success to optimize the customers within your account team territory Participate in customer discovery to understand the customer's current state, what business problems they want to solve, and map back to the Atlassian products, platforms and solutions that will get them where they want to be Probe for and identify additional opportunities for cross-product/solution expansion Investigate, discover, and assess client pain points Be a product expert of Atlassian software in the pre-sales process, articulating and showing the customer the value of the software and how it can change their way of working Have a broad understanding of full Atlassian product and solution offerings and paint a compelling story of how they work together to unlock the power of teams Lead compelling value-based demonstrations, both standard and customized, flexing across multiple different stakeholder needs, from deep individual product demos to selling the large vision of the whole portfolio Understand, lead, and guide the customer's technical needs in the sales process to gain buy-in from the customer on Atlassian being the right decision Proactively forge strong partnerships with aligned account executives, regularly discussing pipeline, current and upcoming opportunities and needs, bi-directional feedback, and ways to improve the selling cycle together Understand, track and document product feedback and competitive intelligence from customers and advocate for the development internally by documenting and sharing with product management Continuously learn, develop and refine your pre-sales and product, solution and platform offering knowledge and sales processes and Atlassian products progress" We need to turn each line into
    • . Ensure we keep the content exactly. Now Qualifications: we have paragraph "Your Background: 3+ years of experience interacting with mid-market customers in a pre-sales capacity, with excellent communication, strong presentation skills to multi-level audiences, and unmatched agility to do what it takes to get the job done. You’re a creative problem solver who can interpret complex business problems, boil them down into solutions, and collaborate with prospects, partners, and the Atlassian sales team to deliver compelling value-based solutions. You’re equally comfortable in both a business and technical context, interacting with executives or talking shop with strong technical audiences. You love to learn and continuously grow and challenge yourself, are open to giving and receiving feedback, tolerate failure, love to win, hate to lose, and are passionate about making customers and Atlassian successful. If you’re looking to be a cog in the system, this job isn’t for you. You’ve got a customer-centric mindset, with a proven track record in building executive relationships with customers and rally the internal teams to collaborate across the company to meet our customers needs." We'll split each sentence into
    • . Note the last sentence has two sentences combined with a period after "system". Actually: "If you’re looking to be a cog in the system, this job isn’t for you. You’ve got a customer-centric mindset, with a proven track record in building executive relationships with customers and rally the internal teams to collaborate across the company to meet our customers needs." That's two sentences. We'll split accordingly. Now Pay section: The compensation paragraph: "Compensation At Atlassian, we strive to design equitable, explainable, and competitive compensation programs. To support this goal, the baseline of our range is higher than that of the typical market range, but in turn we expect to hire most candidates near this baseline. Base pay within the range is ultimately determined by a candidate's skills, expertise, or experience. Role In the United States, we have three geographic pay zones. For this role, our current base pay ranges for new hires in each zone are: Zone A: $137,700 - $179,775 Zone B: $124,200 - $162,150 Zone C: $114,300 - $149,225 This role may also be eligible for benefits, bonuses, commissions, and equity. Please visit go.atlassian.com/payzones for more information on which locations are included in each of our geographic pay zones. However, please confirm the zone for your specific location with your recruiter." We need to remove the heading "Compensation" and maybe "Role" weird. The text includes "Role In the United States". Likely a formatting error; we should keep the substantive content. We'll produce a paragraph with that content, but we should clean up duplicated words: "Compensation At Atlassian" -> start with "At Atlassian". Also "Role In the United States" -> maybe just "In the United States". We'll produce a clean paragraph. Benefits: "Benefits & Perks Atlassian offers a wide range of perks and benefits designed to support you, your family and to help you engage with your local community. Our offerings include health and wellbeing resources, paid volunteer days, and so much more. To learn more, visit go.atlassian.com/perksandbenefits ." We'll produce paragraph. About Atlassian: "About Atlassian At Atlassian, we're motivated by a common goal: to unleash the potential of every team. Our software products help teams all over the planet and our solutions are designed for all types of work. Team collaboration through our tools makes what may be impossible alone, possible together. We believe that the unique contributions of all Atlassians create our success. To ensure that our products and culture continue to incorporate everyone's perspectives and experience, we never discriminate based on race, religion, national origin, gender identity or expression, sexual orientation, age, or marital, veteran, or disability status. All your information will be kept confidential according to EEO guidelines. To provide you the best experience, we can support with accommodations or adjustments at any stage of the recruitment process. Simply inform our Recruitment team during your conversation with them. To learn more about our culture and hiring process, visit go.atlassian.com/crh ." We need to remove EEO boilerplate and accommodation lines. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we must delete the EEO lines and accommodation lines. Also the line about "All your information will be kept confidential according to EEO guidelines." and "To provide you the best experience, we can support with accommodations or adjustments at any stage of