Senior Application Developer

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. Only include sections that have real specific content. We need to parse the job posting. Job Title: Senior Application Developer (but we must not repeat job title as heading). Clearance Required: Public Trust – Federal Client requires US Citizenship. Work Location: Hybrid, Washington, DC. We need to include sections: About the role (maybe from description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to preserve all substantive info, no filler. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Application Deadline: October 31, 2026" maybe considered application instruction? It's a deadline; but instruction to apply? Might be considered application instruction. The instruction says remove application instructions. So we should remove that line. Also remove "Required Certification(s): N/A." and "Desired Certification(s): ..." maybe we keep if relevant? It's about certifications; but it's not a section heading; we could include under Qualifications or Skills. But we need to preserve substantive info. However "N/A" is filler; we should not include placeholder text. So we should omit that line. Also "Preferred Qualifications" etc. We need to decide sections. Let's extract content: About the role: The description after "Alpha Omega is looking for a Senior Application Developer to join our team supporting one of our government customers." Then there is a confusing sentence: "The Junior Database and Automation Engineer will maintain and enhance a portfolio of Power Platform solutions, including Power Apps, Power Automate flows, and Power BI dashboards." That seems mismatched (Junior vs Senior). But we keep as is. Then: "The developer will independently deliver routine feature requests, bug fixes, and workflow automations that support day-to-day operational efficiency. This role is ideal for an early-career developer with a go-getter attitude looking to grow within an established technical delivery team, working under the direction of a senior technical lead." That's about the role. Responsibilities: List under "Key Responsibilities". Items: - Serve as the primary developer maintaining and enhancing two complex, business-critical Canvas Power Apps, plus additional smaller apps in the portfolio. - Build and modify Canvas app screens, forms, and data connections, delivering routine feature requests, bug fixes, and UI adjustments from the backlog. - Develop and maintain Power BI dashboards, reports, and Workspace Apps tied to the Canvas Apps and other ad-hoc data sources. - Create and maintain automated workflows using Power Automate to support reporting and streamline repetitive tasks. - Perform routine access controls, end-user support, and O&M across the application portfolio. - Clean and integrate data from multiple sources (SQL, Excel, SharePoint, APIs) as needed for applications and reporting. - Support client Systems Engineering Lifecycle (SELC) tasks and maintain technical documentation, including use of deployment pipelines. - Handle ad hoc client requests for existing systems, such as data ingest from flat Excel files. - Collaborate with functional area teams to translate business requirements into effective Power Platform solutions. That's a list. Requirements: There's a section "Required Qualifications Required Experience/Skills:" then a list of items. That seems like requirements. We need to separate Requirements vs Qualifications vs Skills? The instruction says use headings for those categories if content exists. We have "Required Qualifications" which includes experience/skills. Then "Preferred Qualifications". Then "Education". Also "Required Certification(s): N/A." etc. We could treat "Required Qualifications" as Requirements heading. "Preferred Qualifications" as Qualifications heading. "Education" maybe as Qualifications or separate? Could be under Qualifications. Skills maybe from list of knowledge etc. But we need to avoid thin sections. Let's see what we have: - Required Qualifications (list of experience/skills) - Preferred Qualifications (list) - Education (Bachelor’s degree or relevant experience) - Knowledge of SQL Databases etc. - Ability to develop training materials... - Experience with Federal government contracting... - Experience with RPA and AI/ML technologies. - Required Certification(s): N/A (skip) - Desired Certification(s): Certifications that show desire for learning... (maybe keep under Qualifications or Skills) - (Required Or Preferred) Education A Bachelor’s degree in Computer Science, Information Systems, or related field. We also have "Salary And Benefit Information" with salary range. Benefits section: list of benefits. Culture And Values etc maybe not needed as per headings; but we could include under About the role? But we should only include sections with real specific content. The culture and values is substantive but not under given headings; we could maybe put under About the role? But the instruction says use headings for those specific headings; we could add a section like "Culture And Values" but not in allowed list. So we should not create extra headings; we could incorporate that info into About the role paragraph maybe. But we must preserve all substantive info; we could add a paragraph under About the role that includes culture and values. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine culture and values into About the role. Also "Our Company" description could go into About the role. Thus we will have sections: - About the role (paragraph(s) covering description, company info, culture/values) - Responsibilities (ul) - Requirements (ul) from Required Qualifications list - Qualifications (ul) from Preferred Qualifications list plus education, knowledge, abilities, certifications etc. - Benefits (ul) - Pay (maybe a p with salary range) - Schedule? Not specified; there is no schedule info besides Hybrid location. Could treat Work Location as Schedule? Not exactly. The instruction says include Schedule section only if posting actually states them. There's no explicit schedule (e.g., full-time, part-time, shift). So we omit Schedule. Also we need to include clearance and location maybe in About the role or a short p. Could add a short p under About the role for metadata: "Clearance Required: Public Trust – Federal Client requires US Citizenship. Work Location: Hybrid, Washington, DC." We must not repeat job title as heading. Now we need to output HTML fragment: use

for each section heading, then content:

for prose,

• for lists. We must not include any extra tags like unless needed? Not prohibited but better to keep simple. Let's craft. First, About the role: We need to combine: "Alpha Omega is looking for a Senior Application Developer to join our team supporting one of our government customers. The Junior Database and Automation Engineer will maintain and enhance a portfolio of Power Platform solutions, including Power Apps, Power Automate flows, and Power BI dashboards. The developer will independently deliver routine feature requests, bug fixes, and workflow automations that support day-to-day operational efficiency. This role is ideal for an early-career developer with a go-getter attitude looking to grow within an established technical delivery team, working under the direction of a senior technical lead." Then company description: "Our Company Alpha Omega is an award-winning solutions provider dedicated to delivering mission-enabling technology and strategic solutions for our customers. Since our founding in 2016, we have grown to over 700 employees nationwide consisting of former operators, technologists, and strategists who bring decades of government and industry experience. They are united by one purpose: ensuring our nation’s continued global leadership. We have a unified operating model providing technical capabilities and solutions for customers across two main business units: National Security – supporting agencies such as the Department of Homeland Security (DHS), Navy, Air Force, Army, and the Department of State (DOS). National Resilience – supporting agencies such as Federal Deposit Insurance Corporation (FDIC), Treasury, Health & Human Services (HHS), National Institutes of Health (NIH), National Oceanic and Atmospheric Administration (NOAA) and the United States Department of Agriculture (USDA) Through strategic partnerships, intellectual property, and relentless drive for innovation, Alpha Omega is shaping the future of government technology. We are proud to be a Virginia Best Places to Work 8 times, an Inc. 5000 honoree 7 times, and a Washington Post Top Workplaces 4 times. Join us in driving transformation that secures the nation's future." Culture and values: "Guided by our core values—Harmony, Engagement, Accountability, Resourcefulness, and Tenacity (HEART)— we foster a culture of innovation, collaboration, and continuous learning and are committed to delivering high-impact solutions. We recognize and reward hard work. Alpha Omega's culture is driven by our values and mission. We invest in top talent through mentorship, growth, and meaningful work. We value individuality, reward integrity, and foster a diverse, high-performing team united by purpose-at work, in service, and in the community." Add clearance and location: "Clearance Required: Public Trust – Federal Client requires US Citizenship. Work Location: Hybrid, Washington, DC." We can put that as a short p. Now Responsibilities: list as above. Requirements: list from Required Qualifications: - Ten (10) or more years of relevant experience in an Enterprise IT environment leading major systems support and integration efforts across a mixed platform. - Relevant experience working in a Federal Law Enforcement environment. - Demonstrated lifecycle acquisition Program Management experience in a Federal environment. - Demonstrated Project Management experience in an Agile environment. - Experience with requirements tools and tracking. - Experience working and leading an Agile Program with multiple workstreams/components. - Experience defining solutions that cross business and technical boundaries. - Experience monitoring program execution to identify obstacles and deviations from plan and takes corrective action as needed. - Experience conducting continuous risk assessment and management including developing measures to reduce risk in program execution. - Experience with contract management, budgeting, and resource allocation, including management of subcontractor personnel. - Experience with all aspects of configuration management planning including configuration identification, change control, configuration status accounting, configuration audits, configuration documentation. We should keep each as
• . Qualifications: from Preferred Qualifications plus education, knowledge, abilities, certifications. Preferred Qualifications list: - Bachelor’s degree or relevant experience. - Knowledge of SQL Databases and Query creation. - Knowledge of the Federal Acquisition Lifecycle or commercial contracting. - Knowledge of Federal financial systems or commercial accounting. - Ability to develop training materials and conduct end-user training sessions. - Experience with Federal government contracting and/or program office organizations business processes. - Experience with RPA and AI/ML technologies. Also Desired Certification(s): Certifications that show the desire for learning and continued education (e.g., IBM or Tableau certifications). We can include that as a bullet. Also Education: "A Bachelor’s degree in Computer Science, Information Systems, or related field." (but note Preferred Qualifications already includes Bachelor’s degree or relevant experience; we can keep both but avoid duplication. We'll include education bullet. We might combine education bullet: "Bachelor’s degree in Computer Science, Information Systems, or related field." Now Benefits: list from Benefits section: - 15 days PTO including paid parental, military, and bereavement leave - Eleven (11) paid Federal holidays, five of which are floating holidays (as designated by the company’s holiday schedule each year) - Health and Dental Insurance (including 100% employer paid premiums for employee coverage under the HDHP health plan) - Life Insurance, STD/LTD term disability coverage, with employer paid premiums - 401(k) plan with a match that is 100% vested after you complete two years of service - FSA/DFSA/HSA flexible benefit plans - Annual Tuition & Professional Development Reimbursement benefit We should keep as list. Pay: Salary range: "$130,000 - $145,000." plus note that it's not guarantee etc. We should preserve that note. So we can put a p: "The likely