Software Engineer (FORECASTED)

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Must preserve all substantive information; do not invent or summarize away detail. Must not include sections with filler like "commensurate with experience", etc. Must not create Pay/Schedule/Benefits sections unless posting actually states them. We need to parse the posting. Key parts: - Title: "This Position is Contingent on Contract Award** Description Columbia Technology Partners is seeking a Software Engineer to develop, maintain, and enhance complex software systems supporting mission-critical operations." - About the role? There's a description paragraph: "Columbia Technology Partners is seeking a Software Engineer to develop, maintain, and enhance complex software systems supporting mission-critical operations. The ideal candidate will contribute to all phases of the software development lifecycle, including requirements analysis, design, development, testing, integration, deployment, and sustainment. Opportunities are available for entry-level developers through senior technical leaders supporting advanced analytics, large-scale data processing, real-time systems, and enterprise software solutions." That could be "About the role" section. - Key Responsibilities: a list of bullet points (though they are sentences separated by periods). We need to put them in

• . - Qualifications: includes education, substitution, levels (Level 0-3). That's qualifications. - Preferred Qualifications: list. - Requirements: includes U.S. Citizenship required, security clearance, polygraph, drug testing, background investigation, etc. Also "Certification Requirements:N/A". Also "This position requires an active Security Clearance with appropriate Polygraph." - About Us: description of company. - Salary Range Transparency: description of how salary ranges determined. No actual numbers given. It says "Salary Range Transparency" but does not give actual numbers. According to rule: do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It does not give actual salary numbers or range. It only explains how they determine salary ranges. That is not a specific pay figure. Should we include a Pay section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Salary Range Transparency" and describes factors but not actual numbers. I'd interpret that as not stating actual pay, so we should NOT include a Pay section. Similarly, Benefits: there is a "Really Good Benefits, For Really GREAT People" section describing benefits: medical, vision+dental, retirement, PTO, etc. That is specific benefits. So we should include a Benefits section with those details. - Schedule: not mentioned. No schedule info. So no Schedule section. - Skills: maybe we could include a Skills section derived from Preferred Qualifications? But we have Qualifications and Preferred Qualifications; we could combine them into Qualifications and maybe Skills? The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only when posting has real specific content. We have content for About the role, Responsibilities, Qualifications (including education, levels), Preferred Qualifications (could be Skills), Requirements, Benefits. We could treat Preferred Qualifications as Skills. Or we could keep Qualifications and Preferred Qualifications separate but we only have allowed headings; we could put Preferred Qualifications under Skills heading. Or we could have both Qualifications and Skills sections: Qualifications for mandatory qualifications, Skills for preferred. That seems reasonable. Thus sections: -

  About the role

  with paragraph(s) from description. -

  Responsibilities

  with
  • each responsibility. -

    Qualifications

    with paragraph(s) for education, substitution, levels. -

    Skills

    with preferred qualifications list. -

    Requirements

    with paragraph(s) for citizenship, security clearance, polygraph, drug testing, background investigation. -

    Benefits

    with list of benefits. We must not include EEO boilerplate etc. Remove duplicated lines. Also remove "This Position is Contingent on Contract Award**" maybe keep as part of description? It's a note; we could include it in About the role paragraph? It's a statement about contingency; it's substantive. We'll keep it. We must not include "About Us" as a heading unless we have a heading for it; but we don't have a heading for About Us in allowed list. Could we put About Us under About the role? Probably not; but we could include it as part of About the role? The instruction says use headings for those specific section names; we can add other headings? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples but likely we should stick to those. The About Us content is not required to be a separate section; we could incorporate it into About the role or maybe omit? But we must preserve ALL substantive information. So we need to include that info somewhere. We could put it under About the role as a paragraph describing the company. That seems okay. Similarly, Salary Range Transparency: we decided not to include Pay section because no specific numbers. But we could include that info under About the role or maybe under Benefits? It's about compensation philosophy; maybe we could include it under About the role as a paragraph. However, the rule says do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Salary Range Transparency" but not actual numbers. It's still about pay. Safer to not create a Pay section; we could include that info under About the role as a paragraph describing compensation philosophy. That preserves info. Thus About the role will contain: the initial description about seeking Software Engineer, plus the Opportunities sentence, plus About Us paragraph, plus Salary Range Transparency paragraph. Now we need to ensure we don't include boilerplate like EEO, equal opportunity employer, etc. We must remove those lines. Also remove "Columbia Technology Partners is an Equal Opportunity Employer." etc. Also remove "CTP was voted one of the top 25 best places to work in Baltimore by Baltimore Magazine!" That's maybe not boilerplate but could be considered fluff; but it's substantive? It's about accolades; maybe we keep it? It's not required to be removed; it's not EEO/legal. It's okay to keep. We also need to remove duplicated lines: there may be duplicate statements like "Columbia Technology Partners is an Equal Opportunity Employer." appears twice? We'll remove. Now craft HTML. We'll need to escape any special characters? Not needed. Let's draft:

    About the role

    This Position is Contingent on Contract Award. Columbia Technology Partners is seeking a Software Engineer to develop, maintain, and enhance complex software systems supporting mission-critical operations. The ideal candidate will contribute to all phases of the software development lifecycle, including requirements analysis, design, development, testing, integration, deployment, and sustainment. Opportunities are available for entry-level developers through senior technical leaders supporting advanced analytics, large-scale data processing, real-time systems, and enterprise software solutions. Founded in 2007, Columbia Technology Partners is a Service-Disabled Veteran Owned Small Business with a specialization in technology and management consulting committed to solving intricate and sensitive technology issues facing corporations and federal agencies. Since its inception, CTP has been instrumental in the technical design, engineering development, operational deployment, and support of key systems. With a proven track record in information security, project management, systems/network engineering, security risk management, vulnerability assessments, and mobile security implementation; our employees have the experience, expertise, and innovative thinking our customers need for results that exceed expectations. CTP staff have worked closely with both government engineers and management to gather mission requirements, develop the architecture to deliver the needed functionality and assess tools available to meet or exceed the needs of the mission. At Columbia Technology Partners (CTP), we are united in being the best that we can be as individuals, but our core belief is that we can be better together. Together we will take on each mission with an execution process that authentically represents who we are. Our success relies on our team values, the foundation we built around them, and the Partners we become along the way. That's why our pay is competitive, our missions are critical, and our benefits represent what matters most to CTP: Our People. Our salary ranges are based on the following key factors: Job Role and Responsibilities: The specific duties and responsibilities associated with each role form the foundation of our compensation structure.Market Research and Industry Benchmarks: We conduct regular analysis of market trends and salaries across our industry, using reliable compensation data to ensure we stay competitive.Experience and Qualifications: An individual's experience, education, certifications, and specialized skills all contribute to determining their position within a salary range.Location: Salary ranges may be adjusted based on geographic cost of living, in accordance with local and national standards.Company Performance: Our compensation practices also take into account overall company performance and financial health, ensuring that we maintain sustainability while rewarding our team.

    Now Responsibilities: We need to extract each responsibility sentence from "Key Responsibilities". The text: "Key Responsibilities Analyze user requirements to derive software design and performance requirements.Design, develop, test, document, and maintain software applications and system components.Debug existing software and resolve defects to improve functionality and performance.Integrate software into new or existing systems and operating environments.Develop and maintain database interfaces, queries, and data repository solutions.Implement algorithms to satisfy system performance, scalability, and functional requirements.Collaborate with system engineers, hardware engineers, and stakeholders to derive software requirements and resolve technical challenges.Participate in software testing, quality assurance, and verification activities.Recommend and implement improvements to software development processes and documentation standards.Design and implement complex algorithms, interfaces, and software architectures.Lead software development efforts, oversee team activities, and ensure compliance with established development processes.Coordinate software installation, deployment, and operational support activities.Recommend new technologies, methodologies, and engineering practices to improve software solutions.Provide technical leadership, mentorship, and quality oversight across software development teams.Support customer engagement activities and contribute to strategic software engineering decisions." We need to split into separate items. Each starts with a verb. We'll create
  • for each. Now Qualifications: Text: "Qualifications Bachelor's degree in Computer Science or a related discipline from an accredited college or university.Four (4) years of additional Software Engineer experience may be substituted in lieu of a bachelor's degree.For Level 0: No demonstrated Software Engineer experience required.For Level 1: Seven (7) years of Software Engineer experience supporting programs and contracts of similar scope, type, and complexity.For Level 2: Fourteen (14) years of Software Engineer experience supporting programs and contracts of similar scope, type, and complexity.For Level 3: Twenty (20) years of Software Engineer experience supporting programs and contracts of similar scope, type, and complexity." We'll put as paragraph(s). Could be one paragraph. Now Skills (Preferred Qualifications): Text: "Preferred Qualifications Experience developing software in Linux and cloud-based environments.Experience with modern programming languages, frameworks, and software development methodologies.Experience supporting large-scale data processing, analytics, real-time applications, or distributed systems.Experience with database design, data repositories, and complex query development.Experience serving as a technical lead, mentoring developers, or managing software development efforts.Experience supporting Agile, DevSecOps, CI/CD, automated testing, and secure software development practices." We'll list each as
  • . Now Requirements: Text: "Requirements U.S. Citizenship is required for all applicants. CTP is an equal opportunity employer and abides by applicable employment laws and regulations. All applicants and employees are subject to random drug testing in accordance with Executive Order 1