Senior Solutions Engineer | DX
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Content:
Overview Working at Atlassian Atlassians can choose where they work – whether in an office, from home, or a combination of the two. That way, Atlassians have more control over supporting their family, personal goals, and other priorities. We can hire people in any country where we have a legal entity. DX's Solutions Engineering Team at Atlassian is seeking a highly skilled and passionate Pre-Sales Senior Solutions Engineer to be a key driver in the growth of the DX product ( getdx.com ). You will serve as the solution expert throughout the sales cycle, dedicated to solving our Enterprise prospects' most complex business problems using our products and solutions, and ultimately helping to close critical deals.
Responsibilities list: bullet points.
Compensation: includes description about equitable compensation, pay zones, ranges, benefits, bonuses, commissions, equity.
Qualifications: Technical Skills list, Consultative Skills list.
Benefits & Perks: description.
About Atlassian: description.
We need to decide sections.
We have Overview (maybe "About the role"?). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings based on content.
We have Overview: could be "About the role". We'll include that.
Responsibilities: we have list.
Qualifications: we have Technical Skills and Consultative Skills; could combine under "Qualifications" or separate "Technical Skills" and "Consultative Skills". The instruction says we can use headings like Qualifications, Skills. We could have "Qualifications" with sublists? But we need to output only headings and content; we can have multiple sections.
We have Benefits & Perks: we can have "Benefits". Also Pay: we have pay ranges.
Schedule: not mentioned; we should not create Schedule section.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO etc. The posting includes EEO statements at end: "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 . In line with local law, identity verification (which may include use of biometric data) is a condition of employment with Atlassian for employment fraud purposes."
These are boilerplate/EEO; we should remove them.
Also "Overview Working at Atlassian ..." includes some generic statements; we keep substantive.
We need to preserve all substantive information: the description of role, responsibilities, qualifications, benefits, pay ranges, about Atlassian (maybe we keep as "About the company"? Not listed but could be under "About Atlassian". The instruction didn't list "About the company" but we could use "About the role" for overview and maybe "About Atlassian" as separate? The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but says use those for section headings (e.g. ...). Likely we should stick to those. However we have "About Atlassian" content; we could incorporate into "About the role" or maybe drop? The instruction says preserve ALL substantive information; we cannot drop Atlassian description. So we need a section for it. Could use "About the company" but not in list. Perhaps we can treat it as "About the role" includes both role and company overview. But the overview already includes some company info. The "About Atlassian" paragraph is more generic about mission. We could include it under "About the role" as additional prose.
Thus sections: About the role (overview + Atlassian mission), Responsibilities, Qualifications (maybe split into Technical Skills and Consultative Skills as subheadings? But we only allow h3 headings; we could have separate sections for Technical Skills and Consultative Skills under Qualifications? The instruction says we can use headings like Qualifications, Skills. Could have "Technical Skills" and "Consultative Skills" as separate sections under Skills? Might be okay.
Better: Have sections: About the role, Responsibilities, Technical Skills, Consultative Skills, Benefits, Pay.
We need to ensure we don't create Schedule.
Now format: each heading
Heading
. Then content: if list, use - ...
. If prose, ...
.
We need to preserve all substantive information: let's extract.
Overview paragraph:
"Working at Atlassian Atlassians can choose where they work – whether in an office, from home, or a combination of the two. That way, Atlassians have more control over supporting their family, personal goals, and other priorities. We can hire people in any country where we have a legal entity. DX's Solutions Engineering Team at Atlassian is seeking a highly skilled and passionate Pre-Sales Senior Solutions Engineer to be a key driver in the growth of the DX product ( getdx.com ). You will serve as the solution expert throughout the sales cycle, dedicated to solving our Enterprise prospects' most complex business problems using our products and solutions, and ultimately helping to close critical deals."
We'll keep that as prose.
Responsibilities bullet points:
- Lead Technical Evaluations: Partner closely with Account Executives to drive and lead all technical aspects of the sales cycle, including Proof-of-Concepts (POCs) and Pilots, ensuring clear demonstration of platform value and technical feasibility.
- Discovery and Strategy: Lead technical discovery sessions to deeply understand client needs, existing engineering workflows, and high-level goals.
- Consultative Questioning: Ask thoughtful, detailed questions to uncover critical information about the client’s engineering processes, branching strategies, deployment workflows, and existing tooling.
- Solution Design: Design and propose tailored technical solutions for integrating the company's APIs with complex client workflows to meet evaluation success criteria.
- Trusted Advisory: Act as a trusted advisor to potential clients, providing strategic guidance on best practices for deployment methodologies and analytics integrations.
- Feedback Loop: Capture and synthesize technical feedback from prospects to collaborate closely with the Product and Engineering teams, informing product enhancements and roadmap priorities.
We'll list each as - .
Compensation section: includes description about equitable compensation, pay zones, ranges, benefits, bonuses, commissions, equity. Also mention "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." Also "This role may also be eligible for benefits, bonuses, commissions, and equity."
Then Pay Ranges: 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: $168,079 - $219,437 Zone B: $151,271 - $197,493 Zone C: $139,506 - $182,132
We need to preserve all that. We'll put under Pay section.
We should not include the link text as separate? We can keep as prose.
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 put under Benefits.
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 . In line with local law, identity verification (which may include use of biometric data) is a condition of employment with Atlassian for employment fraud purposes."
But we need to remove EEO boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we must remove the EEO statements. That includes the sentence about never discriminate, EEO guidelines, accommodations, identity verification? The identity verification line might be considered legal? It says "In line with local law, identity verification (which may include use of biometric data) is a condition of employment with Atlassian for employment fraud purposes." That's legal boilerplate; we should remove it as well.
Thus we need to keep only substantive parts: the mission statement about unleashing potential, software products help teams, team collaboration makes impossible alone possible together, unique contributions create success. Possibly also the sentence about "To learn more about our culture and hiring process, visit go.atlassian.com/crh ." That's not EEO; it's a link to culture/hiring process; we can keep.
Thus About Atlassian section will contain:
"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 learn more about our culture and hiring process, visit go.atlassian.com/crh ."
We removed EEO and identity verification.
Now Technical Skills bullet list:
- Exposure to programming (Ruby/Rails preferred) with a solid understanding of APIs and RESTful services.
- Experience with version control systems like Git and the GitHub CLI.
- Familiarity with SQL.
- Knowledge of CI/CD pipelines, deployment workflows, and branching strategies.
Consultative Skills bullet list:
- Excellent communication and presentation skills, with extensive experience leading high-stakes client discussions and product demonstrations.
- Ability to translate complex technical concepts into clear business value.
- Strong organizational
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: Overview Working at Atlassian Atlassians can choose where they work – whether in an office, from home, or a combination of the two. That way, Atlassians have more control over supporting their family, personal goals, and other priorities. We can hire people in any country where we have a legal entity. DX's Solutions Engineering Team at Atlassian is seeking a highly skilled and passionate Pre-Sales Senior Solutions Engineer to be a key driver in the growth of the DX product ( getdx.com ). You will serve as the solution expert throughout the sales cycle, dedicated to solving our Enterprise prospects' most complex business problems using our products and solutions, and ultimately helping to close critical deals. Responsibilities list: bullet points. Compensation: includes description about equitable compensation, pay zones, ranges, benefits, bonuses, commissions, equity. Qualifications: Technical Skills list, Consultative Skills list. Benefits & Perks: description. About Atlassian: description. We need to decide sections. We have Overview (maybe "About the role"?). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings based on content. We have Overview: could be "About the role". We'll include that. Responsibilities: we have list. Qualifications: we have Technical Skills and Consultative Skills; could combine under "Qualifications" or separate "Technical Skills" and "Consultative Skills". The instruction says we can use headings like Qualifications, Skills. We could have "Qualifications" with sublists? But we need to output only headings and content; we can have multiple sections. We have Benefits & Perks: we can have "Benefits". Also Pay: we have pay ranges. Schedule: not mentioned; we should not create Schedule section. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO etc. The posting includes EEO statements at end: "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 . In line with local law, identity verification (which may include use of biometric data) is a condition of employment with Atlassian for employment fraud purposes." These are boilerplate/EEO; we should remove them. Also "Overview Working at Atlassian ..." includes some generic statements; we keep substantive. We need to preserve all substantive information: the description of role, responsibilities, qualifications, benefits, pay ranges, about Atlassian (maybe we keep as "About the company"? Not listed but could be under "About Atlassian". The instruction didn't list "About the company" but we could use "About the role" for overview and maybe "About Atlassian" as separate? The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but says use those for section headings (e.g. ...). Likely we should stick to those. However we have "About Atlassian" content; we could incorporate into "About the role" or maybe drop? The instruction says preserve ALL substantive information; we cannot drop Atlassian description. So we need a section for it. Could use "About the company" but not in list. Perhaps we can treat it as "About the role" includes both role and company overview. But the overview already includes some company info. The "About Atlassian" paragraph is more generic about mission. We could include it under "About the role" as additional prose. Thus sections: About the role (overview + Atlassian mission), Responsibilities, Qualifications (maybe split into Technical Skills and Consultative Skills as subheadings? But we only allow h3 headings; we could have separate sections for Technical Skills and Consultative Skills under Qualifications? The instruction says we can use headings like Qualifications, Skills. Could have "Technical Skills" and "Consultative Skills" as separate sections under Skills? Might be okay. Better: Have sections: About the role, Responsibilities, Technical Skills, Consultative Skills, Benefits, Pay. We need to ensure we don't create Schedule. Now format: each heading
Heading
. Then content: if list, use- ...
...
. We need to preserve all substantive information: let's extract. Overview paragraph: "Working at Atlassian Atlassians can choose where they work – whether in an office, from home, or a combination of the two. That way, Atlassians have more control over supporting their family, personal goals, and other priorities. We can hire people in any country where we have a legal entity. DX's Solutions Engineering Team at Atlassian is seeking a highly skilled and passionate Pre-Sales Senior Solutions Engineer to be a key driver in the growth of the DX product ( getdx.com ). You will serve as the solution expert throughout the sales cycle, dedicated to solving our Enterprise prospects' most complex business problems using our products and solutions, and ultimately helping to close critical deals." We'll keep that as prose. Responsibilities bullet points: - Lead Technical Evaluations: Partner closely with Account Executives to drive and lead all technical aspects of the sales cycle, including Proof-of-Concepts (POCs) and Pilots, ensuring clear demonstration of platform value and technical feasibility. - Discovery and Strategy: Lead technical discovery sessions to deeply understand client needs, existing engineering workflows, and high-level goals. - Consultative Questioning: Ask thoughtful, detailed questions to uncover critical information about the client’s engineering processes, branching strategies, deployment workflows, and existing tooling. - Solution Design: Design and propose tailored technical solutions for integrating the company's APIs with complex client workflows to meet evaluation success criteria. - Trusted Advisory: Act as a trusted advisor to potential clients, providing strategic guidance on best practices for deployment methodologies and analytics integrations. - Feedback Loop: Capture and synthesize technical feedback from prospects to collaborate closely with the Product and Engineering teams, informing product enhancements and roadmap priorities. We'll list each as