Senior Technical Advisor
for headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. There's a paragraph about AI tools etc. That's not boilerplate? It's about hiring process; maybe keep? It's not explicitly listed as boilerplate but it's about process; could be considered part of description? Might keep as prose under something like "Hiring Process". But we only include sections when there is real specific content. The AI paragraph is specific content about hiring process; we could include under a section like "Hiring Process" but not in the list of allowed headings? The allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should stick to those headings. The AI paragraph could go under "About the role" or "Description". Probably incorporate into description.
We need to preserve all substantive information. So we need to include content from each section.
Let's parse:
Who we are... Latitude is a growing Service-Disabled Veteran Owned (SDVOSB) Company within the Federal Sector. We have experience in working with various federal clients across multiple different agencies. We believe in adopting and growing a remote work-from-home culture wherever possible to ensure a healthy work-to-life balance. We believe in automating the mundane and investing in our employees helping them grow their careers over time. We strive for innovation and want to develop solutions that we can take pride in and help break through some of the barriers that exist in technology and the government sectors today.
That's "About the role"? Actually it's about the company. Could be "About the role" or maybe "About the company". But we only have allowed headings; "About the role" seems appropriate.
Description... We are hiring a Principal Technical Advisor to be the senior technical voice on a supply chain and logistics program for a federal health customer. You will advise delivery teams and customer stakeholders on the hard calls, resolve the technical disputes that stall work, and carry credibility in rooms where the decision gets made. This is an advisory seat, not a management track. This position is fully remote within the United States.
That's description; could be part of "About the role" or separate "Responsibilities"? Actually responsibilities are listed later under "What You Will Do...". So description could be part of "About the role". We'll combine.
What You Will Do... list bullet points:
- Advise delivery teams and customer stakeholders on technical strategy and the trade-offs behind it
- Resolve escalated technical questions that cross team boundaries
- Review designs and plans before they are committed to, and say what will not work
- Translate between what the customer is asking for and what the technology can deliver
- Build the technical judgment of the people around you
That's responsibilities.
Minimum Qualifications... list bullet points:
- Master's degree and 18+ years of technical experience in enterprise or federal IT
- Demonstrated advisory role on programs where your recommendations changed the outcome
- Depth in at least two of: systems architecture, data, security, or delivery engineering
- Experience working directly with government stakeholders at a decision-making level
- Track record of resolving technical disputes across teams you do not manage
- Advising on security accreditation, including Risk Management Framework activities and the documentation and remediation an authorization depends on
- Serving in a technical lead role within SAFe, across disciplines such as architecture, security or test
- Ability to obtain and maintain a federal background investigation (Public Trust)
Preferred Qualifications... list bullet points:
- Experience on federal health IT programs
- Supply chain, logistics or asset management domain depth
- Experience advising on Section 508 accessibility and Human Centered Design in product delivery
- Enterprise architecture framework experience (TOGAF, FEAF, DoDAF)
- Experience advising on cloud migration of legacy federal systems
- Experience advising on adoption of AI/ML capabilities under federal AI governance
- Familiarity with federal IT governance and approved-tooling processes
Clearance... Applicants selected will be subject to a Security Investigation and May need to Meet Requirements for Access to Protected and/or Classified Information
Citizenship... Applicants need to be a US Citizen to be considered for the position and have physically resided in the United States for a minimum of 3 years due to background investigation requirements
Employee Benefits... list bullet points:
- Medical, Vision, Dental
- Paid Vacation & Sick Time
- Paid Federal Holidays
- 401k Retirement Plan with 100% Company Matching
- Employer Paid Life Insurance
- Continued Education Assistance
- Employee Assistance Program (EAP)
- Commuter Benefits Program
- Health Savings Account (HSA)
Also there is a paragraph about AI tools in hiring process; we could include under "About the role" or maybe a separate "Hiring Process" but not in allowed headings. Could incorporate into description or about the role. Probably include as a paragraph under "About the role" after company description.
Also "The posted range is base annual salary, placement within the range depends on qualifications, relevant experience, and contract requirements." This mentions salary but no actual range; it's vague. According to rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. Here they mention salary range but not actual numbers; it's vague. Should we include a Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says they state "The posted range is base annual salary, placement within the range depends on qualifications, relevant experience, and contract requirements." That's stating there is a posted range but not giving numbers. It's still stating that there is a posted range. However they also say "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This is similar to "placement within the range depends on qualifications..." which is not a specific number but indicates that salary is based on qualifications. It's not a specific number; it's somewhat vague but not exactly placeholder like "commensurate with experience". It says "The posted range is base annual salary". That is a statement that there is a posted range, but they didn't give the range. Might be considered filler? Safer to not include Pay section because no actual numbers given. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that there is a posted range, but not the actual range. I'd interpret that as not enough to create a Pay section. So we omit Pay.
Schedule: they said "This position is fully remote within the United States." That's location, not schedule. No schedule info. So omit Schedule.
Thus sections: About the role (company description + hiring process note), Responsibilities (What You Will Do), Requirements (maybe Minimum Qualifications?), Qualifications (Preferred Qualifications?), Benefits (Employee Benefits). Also maybe Clearance and Citizenship could be under Requirements or Qualifications? They are separate but could be part of Requirements. However we have headings: Requirements, Qualifications, Skills. We could put Minimum Qualifications under Requirements, Preferred Qualifications under Qualifications. Clearance and Citizenship could be under Requirements as well (maybe as sub-bullets). But we must not invent headings not in list. We can include them as part of Requirements section as list items.
Thus:
About the role
Latitude is a growing Service-Disabled Veteran Owned (SDVOSB) Company within the Federal Sector. We have experience in working with various federal clients across multiple different agencies. We believe in adopting and growing a remote work-from-home culture wherever possible to ensure a healthy work-to-life balance. We believe in automating the mundane and investing in our employees helping them grow their careers over time. We strive for innovation and want to develop solutions that we can take pride in and help break through some of the barriers that exist in technology and the government sectors today. We are hiring a Principal Technical Advisor to be the senior technical voice on a supply chain and logistics program for a federal health customer. You will advise delivery teams and customer stakeholders on the hard calls, resolve the technical disputes that stall work, and carry credibility in rooms where the decision gets made. This is an advisory seat, not a management track. This position is fully remote within the United States. We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses and identifying potential inconsistencies or verification signals in application materials based on available information. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us.
Responsibilities
- Advise delivery teams and customer stakeholders on technical strategy and the trade-offs behind it
- Resolve escalated technical questions that cross team boundaries
- Review designs and plans before they are committed to, and say what will not work
- Translate between what the customer is asking for and what the technology can deliver
- Build the technical judgment of the people around you
Requirements
- Master's degree and 18+ years of technical experience in enterprise or federal IT
- Demonstrated advisory role on programs where your recommendations changed the outcome
- Depth in at least two of: systems architecture, data, security, or delivery engineering
- Experience working directly with government stakeholders at a decision-making level
- Track record of resolving technical disputes across teams you do not manage
- Advising on security accreditation, including Risk Management Framework activities and the documentation and remediation an authorization depends on
- Serving in a technical lead role within SAFe, across disciplines such as architecture, security or test
- Ability to obtain and maintain a federal background investigation (Public Trust)
- Applicants selected will be subject to a Security Investigation and may need to meet requirements for access to protected and/or classified information
- Applicants need to be a US Citizen to be considered for the position and have physically resided in the United States for a minimum of 3 years due to background investigation requirements
Qualifications
- Experience on federal health IT programs
- Supply chain, logistics or asset management domain depth
- Experience advising on Section 508 accessibility and Human Centered Design in product delivery
- Enterprise architecture framework experience (TOGAF, FEAF, DoDAF)
- Experience advising on cloud migration of legacy federal systems
- Experience advising on adoption of AI/ML capabilities under federal AI governance
- Familiarity with federal IT governance and approved-tooling processes
Benefits
- Medical, Vision, Dental
- Paid Vacation & Sick Time
- Paid Federal Holidays
- 401k Retirement Plan with 100% Company Matching
- Employer Paid Life Insurance
- Continued Education Assistance
- Employee Assistance Program (EAP)
- Commuter Benefits Program
- Health Savings Account (HSA)
for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. There's a paragraph about AI tools etc. That's not boilerplate? It's about hiring process; maybe keep? It's not explicitly listed as boilerplate but it's about process; could be considered part of description? Might keep as prose under something like "Hiring Process". But we only include sections when there is real specific content. The AI paragraph is specific content about hiring process; we could include under a section like "Hiring Process" but not in the list of allowed headings? The allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should stick to those headings. The AI paragraph could go under "About the role" or "Description". Probably incorporate into description. We need to preserve all substantive information. So we need to include content from each section. Let's parse: Who we are... Latitude is a growing Service-Disabled Veteran Owned (SDVOSB) Company within the Federal Sector. We have experience in working with various federal clients across multiple different agencies. We believe in adopting and growing a remote work-from-home culture wherever possible to ensure a healthy work-to-life balance. We believe in automating the mundane and investing in our employees helping them grow their careers over time. We strive for innovation and want to develop solutions that we can take pride in and help break through some of the barriers that exist in technology and the government sectors today. That's "About the role"? Actually it's about the company. Could be "About the role" or maybe "About the company". But we only have allowed headings; "About the role" seems appropriate. Description... We are hiring a Principal Technical Advisor to be the senior technical voice on a supply chain and logistics program for a federal health customer. You will advise delivery teams and customer stakeholders on the hard calls, resolve the technical disputes that stall work, and carry credibility in rooms where the decision gets made. This is an advisory seat, not a management track. This position is fully remote within the United States. That's description; could be part of "About the role" or separate "Responsibilities"? Actually responsibilities are listed later under "What You Will Do...". So description could be part of "About the role". We'll combine. What You Will Do... list bullet points: - Advise delivery teams and customer stakeholders on technical strategy and the trade-offs behind it - Resolve escalated technical questions that cross team boundaries - Review designs and plans before they are committed to, and say what will not work - Translate between what the customer is asking for and what the technology can deliver - Build the technical judgment of the people around you That's responsibilities. Minimum Qualifications... list bullet points: - Master's degree and 18+ years of technical experience in enterprise or federal IT - Demonstrated advisory role on programs where your recommendations changed the outcome - Depth in at least two of: systems architecture, data, security, or delivery engineering - Experience working directly with government stakeholders at a decision-making level - Track record of resolving technical disputes across teams you do not manage - Advising on security accreditation, including Risk Management Framework activities and the documentation and remediation an authorization depends on - Serving in a technical lead role within SAFe, across disciplines such as architecture, security or test - Ability to obtain and maintain a federal background investigation (Public Trust) Preferred Qualifications... list bullet points: - Experience on federal health IT programs - Supply chain, logistics or asset management domain depth - Experience advising on Section 508 accessibility and Human Centered Design in product delivery - Enterprise architecture framework experience (TOGAF, FEAF, DoDAF) - Experience advising on cloud migration of legacy federal systems - Experience advising on adoption of AI/ML capabilities under federal AI governance - Familiarity with federal IT governance and approved-tooling processes Clearance... Applicants selected will be subject to a Security Investigation and May need to Meet Requirements for Access to Protected and/or Classified Information Citizenship... Applicants need to be a US Citizen to be considered for the position and have physically resided in the United States for a minimum of 3 years due to background investigation requirements Employee Benefits... list bullet points: - Medical, Vision, Dental - Paid Vacation & Sick Time - Paid Federal Holidays - 401k Retirement Plan with 100% Company Matching - Employer Paid Life Insurance - Continued Education Assistance - Employee Assistance Program (EAP) - Commuter Benefits Program - Health Savings Account (HSA) Also there is a paragraph about AI tools in hiring process; we could include under "About the role" or maybe a separate "Hiring Process" but not in allowed headings. Could incorporate into description or about the role. Probably include as a paragraph under "About the role" after company description. Also "The posted range is base annual salary, placement within the range depends on qualifications, relevant experience, and contract requirements." This mentions salary but no actual range; it's vague. According to rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. Here they mention salary range but not actual numbers; it's vague. Should we include a Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says they state "The posted range is base annual salary, placement within the range depends on qualifications, relevant experience, and contract requirements." That's stating there is a posted range but not giving numbers. It's still stating that there is a posted range. However they also say "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This is similar to "placement within the range depends on qualifications..." which is not a specific number but indicates that salary is based on qualifications. It's not a specific number; it's somewhat vague but not exactly placeholder like "commensurate with experience". It says "The posted range is base annual salary". That is a statement that there is a posted range, but they didn't give the range. Might be considered filler? Safer to not include Pay section because no actual numbers given. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that there is a posted range, but not the actual range. I'd interpret that as not enough to create a Pay section. So we omit Pay. Schedule: they said "This position is fully remote within the United States." That's location, not schedule. No schedule info. So omit Schedule. Thus sections: About the role (company description + hiring process note), Responsibilities (What You Will Do), Requirements (maybe Minimum Qualifications?), Qualifications (Preferred Qualifications?), Benefits (Employee Benefits). Also maybe Clearance and Citizenship could be under Requirements or Qualifications? They are separate but could be part of Requirements. However we have headings: Requirements, Qualifications, Skills. We could put Minimum Qualifications under Requirements, Preferred Qualifications under Qualifications. Clearance and Citizenship could be under Requirements as well (maybe as sub-bullets). But we must not invent headings not in list. We can include them as part of Requirements section as list items. Thus:
About the role
Latitude is a growing Service-Disabled Veteran Owned (SDVOSB) Company within the Federal Sector. We have experience in working with various federal clients across multiple different agencies. We believe in adopting and growing a remote work-from-home culture wherever possible to ensure a healthy work-to-life balance. We believe in automating the mundane and investing in our employees helping them grow their careers over time. We strive for innovation and want to develop solutions that we can take pride in and help break through some of the barriers that exist in technology and the government sectors today. We are hiring a Principal Technical Advisor to be the senior technical voice on a supply chain and logistics program for a federal health customer. You will advise delivery teams and customer stakeholders on the hard calls, resolve the technical disputes that stall work, and carry credibility in rooms where the decision gets made. This is an advisory seat, not a management track. This position is fully remote within the United States. We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses and identifying potential inconsistencies or verification signals in application materials based on available information. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us.
Responsibilities
- Advise delivery teams and customer stakeholders on technical strategy and the trade-offs behind it
- Resolve escalated technical questions that cross team boundaries
- Review designs and plans before they are committed to, and say what will not work
- Translate between what the customer is asking for and what the technology can deliver
- Build the technical judgment of the people around you
Requirements
- Master's degree and 18+ years of technical experience in enterprise or federal IT
- Demonstrated advisory role on programs where your recommendations changed the outcome
- Depth in at least two of: systems architecture, data, security, or delivery engineering
- Experience working directly with government stakeholders at a decision-making level
- Track record of resolving technical disputes across teams you do not manage
- Advising on security accreditation, including Risk Management Framework activities and the documentation and remediation an authorization depends on
- Serving in a technical lead role within SAFe, across disciplines such as architecture, security or test
- Ability to obtain and maintain a federal background investigation (Public Trust)
- Applicants selected will be subject to a Security Investigation and may need to meet requirements for access to protected and/or classified information
- Applicants need to be a US Citizen to be considered for the position and have physically resided in the United States for a minimum of 3 years due to background investigation requirements
Qualifications
- Experience on federal health IT programs
- Supply chain, logistics or asset management domain depth
- Experience advising on Section 508 accessibility and Human Centered Design in product delivery
- Enterprise architecture framework experience (TOGAF, FEAF, DoDAF)
- Experience advising on cloud migration of legacy federal systems
- Experience advising on adoption of AI/ML capabilities under federal AI governance
- Familiarity with federal IT governance and approved-tooling processes
Benefits
- Medical, Vision, Dental
- Paid Vacation & Sick Time
- Paid Federal Holidays
- 401k Retirement Plan with 100% Company Matching
- Employer Paid Life Insurance
- Continued Education Assistance
- Employee Assistance Program (EAP)
- Commuter Benefits Program
- Health Savings Account (HSA)