Sr. Cyber Business Analyst

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have About Us description (but heading "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. The posting includes "About Us" which is about company; we could treat as "About the role"? Actually "About the role" is typical heading for role description. The posting has "Description" then "About Us:" then description of company and role. We could put that under

About the role

with paragraphs. Responsibilities: we have a big list under "Responsibilities". Use

• . Requirements: there is "Required Qualifications:" and "Desired Qualifications". Also "Working Environment". We need to decide sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes "Requirements" (Required Qualifications) and "Desired Qualifications". Could combine under Requirements? Or separate: Requirements (maybe required) and Qualifications (desired). Skills could be derived from required qualifications (proficiency in...). But we should not invent sections if no specific content. The posting includes "Benefits" explicitly. Pay: Salary Description given. Schedule: Working Environment includes expected hours 9-5 Eastern, occasional travel less than 5% per year. That's schedule info. So we can include Schedule section. We must not include headings with filler like "commensurate with experience". Not present. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to cut out the EEO statement, Reasonable Accommodation, Equal Employment Opportunity, etc. Also remove "Location: Remote Work with travel to Pentagon DC and Los Angeles AFB CA This position is contingent upon contract award." That's metadata; we can fold into a short

  or drop it. Probably include as a short paragraph under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short paragraph for location and contingency. We must preserve all substantive information. So we need to include details about responsibilities, requirements, desired qualifications, benefits, pay, schedule, working environment. We need to avoid repeating job title as heading. Not needed. We must output only HTML fragment. Let's structure:

  About the role

  eSimplicity is a modern digital services company that partners with government agencies to improve the lives and protect the well-being of all Americans, from veterans and service members to children, families, and seniors. Our engineers, designers, and strategists cut through complexity to create intuitive products and services that equip federal agencies with solutions to courageously transform today for a better tomorrow. We are seeking a dynamic and proactive Senior Cyber Business Analyst to support help desk and customer service operations for a large-scale SaaS data analytics platform (Palantir Foundry). In this role, you will act as a key liaison between users, engineers, and data stakeholders, providing Tier 1 triage and Tier 2 troubleshooting for platform issues, data pipelines, and analytic workflows. You will help ensure reliable platform operations by resolving user issues, supporting data integration efforts, and improving overall user experience. Working closely with the Envision Program Office and Warp Core Program Executive Office, you will operate in a fast-paced support environment, delivering timely issue resolution, communicating risks and blockers, and driving continuous improvements in platform usability and help desk processes. The ideal candidate is highly collaborative, technically adept, and customer-focused, with a strong ability to translate complex technical issues for both technical and non-technical audiences.

  Location: Remote work with travel to Pentagon, DC and Los Angeles AFB, CA. This position is contingent upon contract award.

  Then Responsibilities:

  Responsibilities

  • Attend Project Meetings: Participate in calls to identify new data sources or additional data required to support ongoing platform work.
  • Schedule Meetings: Coordinate meetings with data source owners and requestors to determine the best approach, establish connections, document processes, and integrate data.
  • Provide Tier 1 triage and Tier 2 troubleshooting/support for data analytics workflows, platform functionality, user issues, and operational incidents within Palantir Foundry.
  • Support users working with data pipelines, analytic workflows, data models, and operational datasets by identifying, troubleshooting, and resolving platform and data-related issues.
  • Work within both code-based and low-code/no-code solutions across the platform to support analytic development, operational workflows, and user requirements.
  • Support and troubleshoot data integration capabilities, including REST API connectivity, data ingestion/export processes, and system-to-system integrations.
  • Collaborate with data scientists, data engineers, analysts, and platform administrators to resolve complex technical and data-related issues.
  • Document troubleshooting procedures, recurring issues, operational processes, and user support guidance to improve platform sustainment and support operations.
  • Support continuous improvement efforts related to platform usability, operational efficiency, data reliability, and analytic workflow optimization.
  • Leverage collaboration tools such as Slack, Teams, Outlook, Sharepoint to communicate, document, and share information across the team.
  • Create documentation repositories and standard operating procedures for help desk actions.
  • Create processes for automation of reoccurring issues to more efficiently use resources.
  • Collaborate with ISSM Team: Provide the ISSM team with up-to-date and accurate information on each data source request to facilitate the Approval Official (AO) approval process.
  • Prioritization for CCB Board: Offer prioritization for data connections to the CCB board, which directs the ISSM and engineering teams efforts to finalize connections.
  • Support Engineering Team: Assist in restoring degraded connections through password resets, identifying points of contact (POCs), and scheduling troubleshooting sessions.
  • User Forum Support: Respond to questions on the Teams "User Forum" or seek input from the engineering team for accurate responses.
  • Facilitate Engineering Inquiries: Assist the engineering team with data-related questions by coordinating discussions between engineers and data SMEs for each connected data source.
  • General Account Management: Create and configure user accounts with appropriate access levels; provide user support, including addressing account-related issues; manage user access to ensure compliance with security protocols.
  • Review migration plans of any data sources and update documentation.
  • Ensure that Engineers members follow data connection processes.
  • Define and operate the organization's data management tools.
  Then Requirements (maybe Required Qualifications):

  Requirements

  • Active Top Secret Security Clearance as required by the US government customer.
  • Minimum of 7-10 years of experience.
  • Bachelor's degree in a relevant field (e.g., Computer Science, Software Engineer, Data Science).
  • Experience working in a government headquarters staff, preferably in support of the Department of Defense or Air Force.
  • Understanding data governance, data integration, and data quality management.
  • Knowledge of cybersecurity protocols, particularly related to data protection and compliance (e.g., ATO, PIA, MOA, DSA).
  • Awareness of government procedures and protocols, especially those relevant to data sharing and collaboration.
  • Strong verbal and written communication skills to effectively coordinate with data source owners, requestors, and engineering teams.
  • Ability to work independently and as a part of a team.
  • Ability to manage multiple data connection projects, prioritize tasks, and ensure timely completion.
  • Proficiency in data analytics principles, data modeling concepts, and enterprise data environments.
  • Proficiency in REST API technologies, Swagger/OpenAPI documentation, and data integration methodologies.
  • Proficiency of cloud-based or enterprise-scale analytics platforms and modern data architectures.
  • Practical experience in Python, SQL, PySpark, and TypeScript/JavaScript for troubleshooting and supporting analytic and operational workflows.
  • Proficient in analyzing datasets, identifying data quality issues, troubleshooting pipeline failures, and resolving platform-related incidents.
  • Ability to support users within a complex data analytics ecosystem and communicate technical findings to both technical and non-technical stakeholders.
  • Ability to quickly learn new analytic tools, platform capabilities, and operational support processes within Foundry.
  • Ability to manage multiple support requests, prioritize operational issues, and work effectively in a fast-paced support environment.
  Then Qualifications (Desired Qualifications):

  Qualifications

  • Experience with Palantir Foundry is highly desired.
  • Candidates without prior Foundry experience must demonstrate the ability to rapidly learn and operate within a complex data analytics platform environment.
  • Experience with data engineering concepts including data lineage, data transformations, data cleansing, ELT processes, and pipeline troubleshooting is highly desired.
  Skills: Could be derived but we already have many skill items in Requirements. Could we create a Skills section summarizing technical skills? The instruction: prefer a few substantive sections over many thin ones. We already have Requirements and Qualifications; maybe we can skip Skills to avoid thin section. However the posting includes many skill proficiencies; we could put them under Skills instead of Requirements. But we already used Requirements for qualifications. Might be okay to have Skills section with those proficiencies. But we need to avoid duplication. Let's think: The posting has "Required Qualifications:" list includes many items, some are qualifications (clearance, experience, degree) and some are skills (proficiency in Python, etc.). The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could split: Requirements for mandatory items (clearance, experience, degree, govt experience, data governance, cybersecurity, awareness, communication, teamwork, project management). Qualifications for desired qualifications (Foundry experience, data engineering concepts). Skills for technical proficiencies (data analytics principles, REST API, cloud platforms, Python/SQL/PySpark/TS, data analysis, learning new tools, managing support requests). That seems reasonable. Thus we need to parse the Required Qualifications list into these categories. Let's extract: Required Qualifications bullet points from posting: - Active Top Secret Security Clearance?as required by the US government customer. - Minimum of 7-10 or years of experience. (typo: "7-10 or years") - Bachelor's degree in a relevant field (e.g., Computer Science, Software Engineer, Data Science.) - Experience working in a government headquarters staff, preferably in support of the Department of Defense or Air Force. - Understanding data governance, data integration, and data quality management. - Knowledge of cybersecurity protocols, particularly related to data protection and compliance (e.g., ATO, PIA, MOA, DSA). - Awareness of government procedures and protocols, especially those relevant to data sharing and collaboration. - Strong verbal and written communication skills to effectively coordinate with data source owners, requestors, and engineering teams. - Ability to work independently and as a part of a team. - Ability to manage multiple data connection projects, prioritize tasks, and ensure timely completion. - Proficiency in data analytics principles, data modeling concepts, and enterprise data environments. - Proficiency in REST API technologies, Swagger/OpenAPI documentation, and data integration methodologies. - Proficiency of cloud-based or enterprise-scale analytics platforms and modern data architectures. - Practical experience in Python, SQL, PySpark, and TypeScript/JavaScript for troubleshooting and