Lead Software Engineer — United States — LinkedIn — 4492188909
Зарплата не указана
ОткликнутьсяКомпания: ••••••••
Локация: United States
Формат: не указан
Занятость: Полная занятость
Грейд: не определён
YvVwNSx FMjumBu seeks a senior engineer to serve as the single named key person on our Library of Congress task order. The engineer plans, builds, tests, and maintains enhancements to the Library’s Web Archiving systems, including pywb, OutbackCDX, Heritrix, and Browsertrix, along with the Varnish, Cloudflare, and loc.gov integrations around them. The Library’s program preserves and serves more than 6PB of archived web content, so the work touches a production archive that researchers use daily. The engineer also acts as RJmfkNz'H technical contact to the Contracting Officer’s Representative, which makes communication skill as important as coding skill.
Duties and Responsibilities
Playback Services
• Develop and maintain the Web Archives Playback Services tools and support the migration of replay from OpenWayback and flat indexes to pywb and OutbackCDX.
• Improve pywb logging to containers so failures, outages, and usage can be tracked.
• Build loc.gov pywb customizations, including color-coded response-code indicators on the calendar page, Library-branded help text, and Ask a Librarian integration.
• Review performance problems and classify each as an infrastructure issue, an application bug, or a feature configuration issue.
• Test and debug the cdx-ingest process, including the retry feature and skipped malformed CDX lines.
• Develop an internal system status page that checks and reports status automatically, with a possible public status page.
• Assist the Web Archiving Team and OCIO with a software roadmap and a Playback Services knowledge base.
Open-Source and IIPC Participation
• Contribute code and documentation to Webrecorder (pywb and wombat.js), OutbackCDX, and Heritrix, including dependency maintenance.
• Join International Internet Preservation Consortium technical discussions at the Library’s request and support the Library’s Technical Committee representative.
• Contribute to conversations on the WARC standard.
In-House Crawl Engineering
• Write requirements for OCIO to support an expanded in-house crawling program and a crawl monitoring dashboard.
• Configure Heritrix, including deduplication, browser-processor, link extraction, regex decide-rules, crawler beans, and Groovy configurations.
• Help build a multi-crawler workflow supporting Browsertrix.
• Train Web Archiving Section staff and produce documentation on tools and on the WARC standard.
Agile Delivery and Reporting
• Work in Kanban with one-week increments of planning, grooming, and review, with every requirement and task recorded as a JIRA ticket.
• Deliver approximately four to six tickets per week at an average velocity of thirteen story points.
• Complete weekly code check-ins, unit tests, user stories, acceptance criteria, and operations and maintenance items.
• Write the monthly report covering completed work, status of milestones, and issues or blockers.
Quality, Lifecycle, and Security
• Perform to the Quality Assurance Surveillance Plan in Attachment J1.
• Follow the Library’s Systems Development Life Cycle and remediate vulnerabilities under LCD 5-410.1.
Education
A bachelor’s degree in computer science, software engineering, information systems, or a closely related field. A master’s degree in one of those fields or in library and information science is preferred. Additional years of directly relevant experience may substitute for the degree, to the extent the IDIQ labor category definition permits.
Experience
• Eight or more years of professional software development experience.
• Five or more years building and maintaining Python web applications, including Django.
• Three or more years working directly with web archiving tools, specifically pywb, OutbackCDX, and Heritrix, along with the WARC format.
• Three or more years of archival web crawling, with hands-on Heritrix configuration and an understanding of crawl quality for preservation.
• Three or more years on AWS-hosted development, test, and production environments.
• Two or more years in a Kanban or Agile team that tracks work in JIRA.
• Working experience with REST APIs and Solr.
Skills
Agile methodology, web archives tools (OpenWayback, pywb, OutbackCDX, Heritrix), preservation-quality archival web crawling, APIs, Solr, Django, and AWS. The candidate must meet or exceed every one of these.
Supporting technologies
Python, JavaScript, HTML/CSS, Bootstrap, JSON, MySQL, RocksDB, Elasticsearch, AWS Glue, Jenkins, Git, Docker, Terraform, Red Hat Linux, Apache, Varnish, Cloudflare, Grafana, and Tableau.
Preferred Qualifications
• Public commits or accepted pull requests in the Webrecorder, OutbackCDX, or Heritrix repositories. Area 2 asks for exactly this work, so a visible contribution history carries weight with evaluators.
• Participation in IIPC working sessions or technical calls.
• Prior work for a library, archive, museum, or other cultural heritage organization.
• Experience with Browsertrix and multi-crawler workflows.
• Experience writing training material for non-developer staff.
Desirable Certifications
• AWS Certified Developer Associate or AWS Certified Solutions Architect Associate
• HashiCorp Certified Terraform Associate
• Professional Scrum Master, Certified ScrumMaster, or a Kanban University credential
• Python Institute PCAP
• Red Hat Certified System Administrator
Security Clearance and Background
The position requires no security clearance. The work is Controlled Unclassified Information protected at Security Category: Moderate. Candidates must hold U.S. work authorization and pass the suitability screening and access forms the Library issues at onboarding. 3yCsMeP also expects a clean criminal and employment history check before the candidate is named in the proposal.
Candidates must also accept these obligations:
• Complete the Library’s information systems security training before any system access and annually afterward.
• Sign a nondisclosure agreement.
• Work from a workstation with continuous antivirus and antispyware, automatic patching, a firewall, and FIPS 140-3 validated encryption for Security Category: Moderate data.
• Report any security incident involving Library CUI within 24 hours.
• Notify the Contracting Officer before using any AI System on deliverables, and never use Library Data to train a model.
• Build to Section 508 and WCAG 2.1 for Library web content.