Lead Software Engineer/Developer - Contingent

We need to output HTML fragment with sections: About Aretum? Actually "About Aretum" is a section heading. Use

for section headings. We need to include sections only if posting has real specific content. We have: - About Aretum (description) - Job Summary (maybe treat as section heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists examples but not exhaustive. We can include Job Summary as a heading? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow pattern: maybe we can treat "Job Summary" as a section heading. However they said "Do NOT repeat the job title as a heading (the page already shows it)". Job Summary is not job title, so okay. We need to include sections: About Aretum, Job Summary, Responsibilities, Requirements, Preferred Qualifications? They said "Qualifications" as a possible heading. Could combine Requirements and Preferred Qualifications under Qualifications? But they said prefer a few substantive sections over many thin ones. We could have sections: About Aretum, Job Summary, Responsibilities, Qualifications (covering Requirements and Preferred Qualifications), Benefits, Travel Requirements? Travel is not in list but could be included as a section if content present. They said include a section ONLY when posting has real specific content. Travel Requirements present: "This is a remote position; however, occasional travel may be required..." So we could include Travel as a section heading maybe "Travel". But they didn't list Travel as example but we can still use

. However they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are typical but not exclusive. Safer to include Travel as a section. We also have Public Trust Eligibility Required and contingent position note at top. That's metadata; we should fold minor metadata into a short

or drop it. So we can include a short paragraph at top: "Public Trust eligibility required. This is a contingent position dependent on contract award and background investigation." We must remove boilerplate: EEO statement, etc. Also remove "EEO Statement", "Equal Opportunity Employer/Veterans/Disabled", "U.S. Work Authorization", etc. Also remove "Travel Requirements" heading? We'll keep travel content. We must preserve all substantive information. So we need to include all responsibilities list items, requirements list items, preferred qualifications list items, benefits list items, etc. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We must not repeat job title as heading. Not include Job ID/requisition numbers. We must not include sections with filler like "commensurate with experience". Benefits section we have actual salary range and benefits list, so we can include Benefits heading. Pay: they gave salary range; we could include Pay section with salary range. But they said never create Pay/Schedule/Benefits sections unless posting actually states them. They gave salary range, so we can include Pay. Benefits also present. Schedule? Not given; they didn't mention schedule (like full-time, hours). So we should not create Schedule section. We could combine Pay and Benefits under Benefits? But they said prefer few substantive sections over many thin ones. Could have Benefits section that includes salary range and benefits list. However they gave separate "Benefits" heading in the posting with bullet list. We could keep Benefits heading and include salary range inside that section as a paragraph. Or we could have Pay section for salary range and Benefits section for benefits. But that would be thin. Better to combine into Benefits section that includes salary range and benefits. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." They didn't forbid combining. I'd create a Benefits section that includes salary range and benefits list. We need to ensure we don't include placeholder text like "not specified". All content is specific. Now craft HTML. Structure:

  Public Trust eligibility required. This is a contingent position dependent on contract award and background investigation.

  About Aretum

  ... (the paragraph)

  Job Summary

  ... (the paragraph)

  Responsibilities

  • ...
  ...

  Qualifications

  We need to include Requirements and Preferred Qualifications. Could split into two sub-sections? But we can just list all items under Qualifications, maybe separate with a note? But we need to preserve all info. Could do:

  Requirements

  ...

  Preferred Qualifications

  ...
  That's two sections; still okay. They said prefer few substantive sections over many thin ones, but we have many sections already. Could combine Requirements and Preferred Qualifications under Qualifications with headings inside? But they said use

  for section headings. Could use

  for subheadings? Not allowed? They didn't forbid other heading levels, but they said use

  for section headings (e.g...). Might be okay to use

  for sub-sections. Safer to keep as separate

  sections: Requirements and Preferred Qualifications. Thus sections: About Aretum, Job Summary, Responsibilities, Requirements, Preferred Qualifications, Benefits, Travel. We must not include Schedule or Pay separately. Now ensure we remove boilerplate: EEO statement, Equal Opportunity Employer/Veterans/Disabled, U.S. Work Authorization, etc. Also remove "Public Trust Eligibility Required" line? We kept it in a short paragraph. Also remove "This is a contingent position, meaning employment is dependent upon the successful award of the associated contract to Aretum and completion of any required background investigation or security clearance verification." We incorporated. Now we need to preserve all substantive information from responsibilities, requirements, preferred qualifications, benefits, travel. Let's extract. Responsibilities list (each line starts with a verb). We'll copy each as

  . Responsibilities bullet points from posting: - Serve as the technical lead of a scrum team working on a three-week sprint cadence as part of an integrated team with government developers, testers, and stakeholders, using standard Agile practices including continuous integration and story-point-based planning in JIRA. - Lead the design, development, and unit testing of Python and Django backend services that support system-to-system content acquisition, ingest, quality review, inventory, and reporting functions. - Design and build REST APIs in Python and Django to support content extract, transform, and load (ETL) operations, metadata exchange, reporting, and digital content management functions across integrated enterprise systems. - Design and implement content identification and selection services, including business rules for selection (date ranges, status flags, ownership), inclusion and exclusion criteria, filtering logic, and manual, scheduled, and event-driven selection triggers. - Build metadata management and transformation services, including field mapping, normalization, schema validation, quality and completeness checks, and reconciliation logic for metadata mismatches and validation failures. - Implement API integration and content transfer capabilities, including source and target API connectivity, authentication and authorization, secure transport, retry and error-handling logic, transfer status monitoring, and end-to-end transaction logging and traceability. - Design relational data models and tune database schemas, queries, and indexes in PostgreSQL to support content registries, workflow state, audit history, and reporting. - Implement asynchronous and background processing for long-running content operations, including queueing, task orchestration, checkpointing, throttling, and idempotent retry behavior for large or batched transfers. - Maintain and extend existing Java components where the platform requires it, applying the same standards of testability, readability, and maintainability used across the codebase. - Integrate existing malware scanning, file integrity validation (checksum comparison), and content routing utility services into exchange workflows through their documented APIs, including quarantine handling and remediation paths. - Design and implement workflow administration and governance capabilities, including workflow states, approvals, escalations, exception paths, role-based permissions, operational queues, and audit logging. - Design and tune search and indexing capabilities using Solr and Elasticsearch to support discovery, reporting, and content management features. - Build and operate services across AWS-based development, test, staging, and production environments, contributing to infrastructure-as-code in Terraform and to containerized deployment patterns using Docker. - Maintain continuous integration pipelines using Jenkins and Git, including automated build, test, and code quality stages such as SonarQube. - Author unit test scripts for your own code and processes, and collaborate with government QA and testing staff who perform acceptance, integration, and accessibility testing, including participating in the creation of acceptance and testing criteria during sprint planning. - Support the accessibility of user-facing components against WCAG 2.1 standards and support remediation of accessibility findings. - Participate fully in Agile ceremonies, including user story creation sessions, daily stand-ups, backlog grooming, sprint planning, sprint reviews, and retrospectives, recording all work as scored user stories in JIRA. - Mentor the team's mid-level developer through pairing, design review, and constructive code review, and enforce the client's coding standards across the team's repositories. - Provide technical input into lifecycle documentation maintained by the client, including system requirements and design documents, system diagrams, and security assessment and authorization artifacts. - Handle all project information appropriately as Controlled Unclassified Information (CUI), performing all development within client-owned and client-managed systems and environments. - Support end-of-engagement closeout activities, including finalizing documentation, closing tickets, and completing transition activities. Now Requirements list: - Minimum 5 years of professional software development experience, including experience serving as a technical lead or senior developer on an Agile team. - Bachelor's degree in Computer Science, Software Engineering, Information Systems, or a related field, or equivalent additional experience. - Proven ability to lead technical designs, conduct peer code review, and mentor mid-level developers. - Deep, hands-on experience building production backend services and REST APIs in Python, including substantial experience with the Django framework. - Strong experience with relational databases, particularly PostgreSQL, including data modeling, schema design, query optimization, and migrations. - Working proficiency in Java, sufficient to maintain, extend, and troubleshoot existing Java components on the platform. - Hands-on experience with Solr and Elasticsearch, including index design and query tuning. - Experience designing and building microservices and REST APIs, including authentication, authorization, versioning, input validation, and error handling. - Experience building ETL or data integration pipelines, including transformation, validation, reconciliation, and error recovery. - Hands-on experience developing and deploying applications in AWS environments. - Working experience with Terraform for infrastructure-as-code. - Experience building and maintaining continuous integration pipelines with Jenkins and Git-based source control. - Working knowledge of content-addressable storage concepts and patterns. - Proficiency with HTML5, CSS3, and JavaScript, sufficient to support and integrate with the program's user-facing components. - Experience working in Agile and Scrum environments, including user-story-based development in JIRA with story-point estimation. - Excellent written and verbal communication skills, with the ability to collaborate effectively with government technical staff, product owners, and non-technical stakeholders in a fully remote setting. Preferred Qualifications list: - Experience supporting federal government clients, particularly on software development or systems integration programs. - Experience with digital content, digital collections, or digital asset management systems, including ingest, preservation, derivative creation, or metadata exchange workflows. - Experience with Celery or comparable distributed task queues for asynchronous processing. - Experience with Docker, Red Hat Linux, Apache, and Varnish in enterprise environments. - Experience with automated testing and code quality tools such as Selenium and SonarQube, and with accessibility testing practices under Section 508 and WCAG 2.1. - Experience with reporting and monitoring tools such as Grafana or Tableau