Senior Solutions Architect I, Pre-Sales - US Government Defense & Intelligence
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. 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. We need to extract substantive content. Let's parse the posting: Intro paragraph about Planet (company description). This is not a section heading but could be a
before sections. Then "About The Role" heading. Under that: description of role: "As a Pre-Sales Sr. Solutions Architect, you'll design complex solutions to demonstrate the value of Planet's data and services to help organizations within the United States Defense and Intelligence community overcome their earth data challenges. You'll collaborate with internal cross-functional teams, including Customer Success, Product Management, and Business Development, to act as the voice of the customer and enhance Planet's industry offerings. The ideal candidate enjoys helping customers get the most out of their work. This role will appeal to candidates who don't mind frequent travel and are comfortable working in the defense and intelligence sector. This is a full-time, hybrid role which will require you to work from our Washington D.C. office located in Arlington, VA 3 days per week. This role requires travel up to 25%." Then "Impact" heading with bullet list of responsibilities. Then "What You Bring" heading with list of qualifications. Then "Benefits While Working At Planet" heading with list of benefits. Then "Compensation" heading with salary range. Also there is mention of "Application Deadline", "EAR/ITAR Requirements", "San Francisco Fair Chance Ordinance", "Why We Care So Much About Belonging", "EEO Statement", "Know Your Rights. Accommodations", "Privacy Policy", "AI in Our Interviewing Process", "Candidate AI Policy". Those are boilerplate/legal; we should remove them. Also "About Planet" intro maybe we keep as a paragraph before sections. We need to output only HTML fragment, no /, no markdown fences. We need to use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide which sections to include: About the role (maybe we combine intro paragraph under that heading? Actually "About The Role" is a heading; we can put the prose under it as
. Then Responsibilities (Impact) as a section with heading
Responsibilities
and list. Then Requirements/Qualifications (What You Bring) as heading Qualifications
(or Requirements). Benefits as Benefits
. Pay as Pay
. Schedule as Schedule
(maybe include hybrid and travel). However we need to ensure we only include sections if posting has real specific content. The posting does have schedule info: "full-time, hybrid role which will require you to work from our Washington D.C. office located in Arlington, VA 3 days per week. This role requires travel up to 25%." That's specific. So we can include Schedule section.
Pay: salary range given: "$116,340—$145,390 USD". Also mention discretionary short-term and long-term incentives. That's specific. So include Pay.
Benefits: list given. So include Benefits.
Now we need to avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from those sections.
Let's extract each section's content.
**About The Role** (heading). Content: The paragraph(s) after that heading up to before "Impact". Let's capture:
"As a Pre-Sales Sr. Solutions Architect, you'll design complex solutions to demonstrate the value of Planet's data and services to help organizations within the United States Defense and Intelligence community overcome their earth data challenges. You'll collaborate with internal cross-functional teams, including Customer Success, Product Management, and Business Development, to act as the voice of the customer and enhance Planet's industry offerings. The ideal candidate enjoys helping customers get the most out of their work. This role will appeal to candidates who don't mind frequent travel and are comfortable working in the defense and intelligence sector. This is a full-time, hybrid role which will require you to work from our Washington D.C. office located in Arlington, VA 3 days per week. This role requires travel up to 25%."
Note: The last two sentences about hybrid and travel could also go to Schedule section, but they are part of About The Role. However we might split them out to Schedule to avoid duplication. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we move those sentences to Schedule section, we still preserve them, just under a different heading. That's acceptable as long as we don't lose them. However we need to ensure we don't duplicate. We could keep them in About The Role and also have Schedule section referencing them? That would duplicate. Better to keep them in Schedule section and maybe keep a brief summary in About The Role? But we must preserve all detail; we can keep them in Schedule and not repeat in About The Role. However the About The Role paragraph currently includes them; if we remove them, we lose that detail from About The Role unless we keep them elsewhere. We can keep them in Schedule and still have About The Role paragraph without those sentences. That would still preserve the information (just moved). That's acceptable.
Thus About The Role paragraph will be:
"As a Pre-Sales Sr. Solutions Architect, you'll design complex solutions to demonstrate the value of Planet's data and services to help organizations within the United States Defense and Intelligence community overcome their earth data challenges. You'll collaborate with internal cross-functional teams, including Customer Success, Product Management, and Business Development, to act as the voice of the customer and enhance Planet's industry offerings. The ideal candidate enjoys helping customers get the most out of their work. This role will appeal to candidates who don't mind frequent travel and are comfortable working in the defense and intelligence sector."
Now we need a Schedule section with details: full-time, hybrid role, work from Washington D.C. office in Arlington, VA 3 days per week, travel up to 25%.
We could phrase as a paragraph or list. Since it's not a list, we can use .
**Responsibilities** (Impact). The bullet list:
- Architect and deliver solution demonstrations and presentations and highlighting technical capabilities and value of Planet’s offerings and our ability to fulfill customer’s business needs.
- Build relationships with customers’ technical and management staff as a trusted advisor to their business.
- Act as a senior technical advisor to the customer to recommend a solutions architecture that fits their business challenges.
- Craft the technical response to tenders, RFI’s/RFP’s, and unsolicited proposals with respect to Planet’s products and solutions.
- Partner with your sales team colleagues to architect and drive the technical strategy across customer and prospect account plans, shaping how accounts are engaged and won.
- Collaborate with internal cross-functional teams including Customer Success, Product Management, and Business Development to act as the voice of the customer, assist with RFP and RFI preparation and submissions.
- Attain quarterly and annual sales and operational objectives assigned by management.
- Represent the needs of Planet's Defense and Intelligence customers to Sales leadership by communicating forecasts, pipeline opportunities, deal reviews, CRM data, and customer feedback.
- Present to key executive Government stakeholders within the US Federal Government.
- Act as a mentor to team members and lead training to drive their development.
We need to preserve all detail. Use
- for each.
**Qualifications** (What You Bring). List:
- 6+ years of experience in supporting the US Defense and Intelligence community in a technical capacity.
- Bachelor’s degree in a relevant field.
- Ability to travel, including internationally, up to 25%.
- Excellent verbal and written communication skills.
- Experience working with GIS and Remote Sensing users within the Defense industry.
- Experience in IMINT, ISR, and related fields.
- Experience with QGIS, SocetGXP, ArcGIS, GDAL, Python, other common geospatial software packages and programming languages, and emerging technologies such as AI/ML.
- Experience designing and presenting complex systems and solutions that bridge the gap between business problems and technology to meet organizational goals, budget, and scalability needs.
- Ability to communicate and coordinate effectively with both technical and non-technical stakeholders.
- Excellent problem-solving skills and a proactive working style.
- Ability to multitask, prioritize, and manage time effectively.
- Ability to process imagery, manipulate geospatial data, interact with APIs, and build data pipelines.
- Ability to lead technical customer engagements.
- Ability to run workshops or training sessions with users.
- Obtaining and maintaining eligibility for a US Government TS/SCI security clearance is required.
We need to keep all.
**Benefits** (Benefits While Working At Planet). List:
- Comprehensive Medical, Dental, and Vision plans
- Health Savings Account (HSA) with a company contribution
- Generous Paid Time Off in addition to holidays and company-wide days off
- 16 Weeks of Paid Parental Leave
- Wellness Program and Employee Assistance Program (EAP)
- Home Office Reimbursement
- Monthly Phone and Internet Reimbursement
- Tuition Reimbursement and access to LinkedIn Learning
- Equity
- Commuter Benefits (if local to an office)
- Volunteering Paid Time Off
We need to keep all.
**Pay** (Compensation). Content:
"The US base salary range for this full-time position at the commencement of employment is listed below. Additionally, this role might be eligible for discretionary short-term and long-term incentives (bonus and equity). The final salary range is determined by job related experience, skills and location. The range displays our typical hiring range for new hire salaries in US locations only. Your recruiter can share more about the specific salary range for your preferred location during the hiring process. US National Salary Range $116,340—$145,390 USD"
We need to preserve all. Could be a paragraph.
**Schedule** (maybe we already have). Content: "This is a full-time, hybrid role which will require you to work from our Washington D.C. office located in Arlington, VA 3 days per week. This role requires travel up to 25%."
We could also mention that it's full-time. Already in that sentence.
Now we need to decide ordering. Typically: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Or any order. We'll follow logical flow.
We must not include any boilerplate like "Application Deadline", "EAR/ITAR Requirements", "San Francisco Fair Chance Ordinance", "Why We Care So Much About Belonging", EEO, etc.
Also we need to remove duplicated lines. Ensure we don't repeat any content.
Now produce HTML fragment.
We'll start with maybe a
for the company description intro? The intro paragraph about Planet is not under a heading; we could keep it as a leading
before sections.
for prose. We need to decide which sections to include: About the role (maybe we combine intro paragraph under that heading? Actually "About The Role" is a heading; we can put the prose under it as
. Then Responsibilities (Impact) as a section with heading
Responsibilities
and list. Then Requirements/Qualifications (What You Bring) as headingQualifications
(or Requirements). Benefits asBenefits
. Pay asPay
. Schedule asSchedule
(maybe include hybrid and travel). However we need to ensure we only include sections if posting has real specific content. The posting does have schedule info: "full-time, hybrid role which will require you to work from our Washington D.C. office located in Arlington, VA 3 days per week. This role requires travel up to 25%." That's specific. So we can include Schedule section. Pay: salary range given: "$116,340—$145,390 USD". Also mention discretionary short-term and long-term incentives. That's specific. So include Pay. Benefits: list given. So include Benefits. Now we need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from those sections. Let's extract each section's content. **About The Role** (heading). Content: The paragraph(s) after that heading up to before "Impact". Let's capture: "As a Pre-Sales Sr. Solutions Architect, you'll design complex solutions to demonstrate the value of Planet's data and services to help organizations within the United States Defense and Intelligence community overcome their earth data challenges. You'll collaborate with internal cross-functional teams, including Customer Success, Product Management, and Business Development, to act as the voice of the customer and enhance Planet's industry offerings. The ideal candidate enjoys helping customers get the most out of their work. This role will appeal to candidates who don't mind frequent travel and are comfortable working in the defense and intelligence sector. This is a full-time, hybrid role which will require you to work from our Washington D.C. office located in Arlington, VA 3 days per week. This role requires travel up to 25%." Note: The last two sentences about hybrid and travel could also go to Schedule section, but they are part of About The Role. However we might split them out to Schedule to avoid duplication. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we move those sentences to Schedule section, we still preserve them, just under a different heading. That's acceptable as long as we don't lose them. However we need to ensure we don't duplicate. We could keep them in About The Role and also have Schedule section referencing them? That would duplicate. Better to keep them in Schedule section and maybe keep a brief summary in About The Role? But we must preserve all detail; we can keep them in Schedule and not repeat in About The Role. However the About The Role paragraph currently includes them; if we remove them, we lose that detail from About The Role unless we keep them elsewhere. We can keep them in Schedule and still have About The Role paragraph without those sentences. That would still preserve the information (just moved). That's acceptable. Thus About The Role paragraph will be: "As a Pre-Sales Sr. Solutions Architect, you'll design complex solutions to demonstrate the value of Planet's data and services to help organizations within the United States Defense and Intelligence community overcome their earth data challenges. You'll collaborate with internal cross-functional teams, including Customer Success, Product Management, and Business Development, to act as the voice of the customer and enhance Planet's industry offerings. The ideal candidate enjoys helping customers get the most out of their work. This role will appeal to candidates who don't mind frequent travel and are comfortable working in the defense and intelligence sector." Now we need a Schedule section with details: full-time, hybrid role, work from Washington D.C. office in Arlington, VA 3 days per week, travel up to 25%. We could phrase as a paragraph or list. Since it's not a list, we can use. **Responsibilities** (Impact). The bullet list: - Architect and deliver solution demonstrations and presentations and highlighting technical capabilities and value of Planet’s offerings and our ability to fulfill customer’s business needs. - Build relationships with customers’ technical and management staff as a trusted advisor to their business. - Act as a senior technical advisor to the customer to recommend a solutions architecture that fits their business challenges. - Craft the technical response to tenders, RFI’s/RFP’s, and unsolicited proposals with respect to Planet’s products and solutions. - Partner with your sales team colleagues to architect and drive the technical strategy across customer and prospect account plans, shaping how accounts are engaged and won. - Collaborate with internal cross-functional teams including Customer Success, Product Management, and Business Development to act as the voice of the customer, assist with RFP and RFI preparation and submissions. - Attain quarterly and annual sales and operational objectives assigned by management. - Represent the needs of Planet's Defense and Intelligence customers to Sales leadership by communicating forecasts, pipeline opportunities, deal reviews, CRM data, and customer feedback. - Present to key executive Government stakeholders within the US Federal Government. - Act as a mentor to team members and lead training to drive their development. We need to preserve all detail. Use
- for each.
**Qualifications** (What You Bring). List:
- 6+ years of experience in supporting the US Defense and Intelligence community in a technical capacity.
- Bachelor’s degree in a relevant field.
- Ability to travel, including internationally, up to 25%.
- Excellent verbal and written communication skills.
- Experience working with GIS and Remote Sensing users within the Defense industry.
- Experience in IMINT, ISR, and related fields.
- Experience with QGIS, SocetGXP, ArcGIS, GDAL, Python, other common geospatial software packages and programming languages, and emerging technologies such as AI/ML.
- Experience designing and presenting complex systems and solutions that bridge the gap between business problems and technology to meet organizational goals, budget, and scalability needs.
- Ability to communicate and coordinate effectively with both technical and non-technical stakeholders.
- Excellent problem-solving skills and a proactive working style.
- Ability to multitask, prioritize, and manage time effectively.
- Ability to process imagery, manipulate geospatial data, interact with APIs, and build data pipelines.
- Ability to lead technical customer engagements.
- Ability to run workshops or training sessions with users.
- Obtaining and maintaining eligibility for a US Government TS/SCI security clearance is required.
We need to keep all.
**Benefits** (Benefits While Working At Planet). List:
- Comprehensive Medical, Dental, and Vision plans
- Health Savings Account (HSA) with a company contribution
- Generous Paid Time Off in addition to holidays and company-wide days off
- 16 Weeks of Paid Parental Leave
- Wellness Program and Employee Assistance Program (EAP)
- Home Office Reimbursement
- Monthly Phone and Internet Reimbursement
- Tuition Reimbursement and access to LinkedIn Learning
- Equity
- Commuter Benefits (if local to an office)
- Volunteering Paid Time Off
We need to keep all.
**Pay** (Compensation). Content:
"The US base salary range for this full-time position at the commencement of employment is listed below. Additionally, this role might be eligible for discretionary short-term and long-term incentives (bonus and equity). The final salary range is determined by job related experience, skills and location. The range displays our typical hiring range for new hire salaries in US locations only. Your recruiter can share more about the specific salary range for your preferred location during the hiring process. US National Salary Range $116,340—$145,390 USD"
We need to preserve all. Could be a paragraph.
**Schedule** (maybe we already have). Content: "This is a full-time, hybrid role which will require you to work from our Washington D.C. office located in Arlington, VA 3 days per week. This role requires travel up to 25%."
We could also mention that it's full-time. Already in that sentence.
Now we need to decide ordering. Typically: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Or any order. We'll follow logical flow.
We must not include any boilerplate like "Application Deadline", "EAR/ITAR Requirements", "San Francisco Fair Chance Ordinance", "Why We Care So Much About Belonging", EEO, etc.
Also we need to remove duplicated lines. Ensure we don't repeat any content.
Now produce HTML fragment.
We'll start with maybe a
for the company description intro? The intro paragraph about Planet is not under a heading; we could keep it as a leading
before sections.