Jobs · Engineering · Maryland

Web Developer 2 (FORECASTED)

Columbia Technology Partners · Annapolis Junction, MD · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: - Description: includes overview, maybe "About the role". Could put under "About the role" heading. - Key Responsibilities: list of duties. - Minimum Qualifications: maybe under "Qualifications" or "Requirements". There's also "Preferred Qualifications". Also "Requirements" includes US Citizenship, security clearance, etc. - Skills: maybe not explicit but could infer from responsibilities. - Benefits: there is a section "Really Good Benefits, For Really GREAT People" with details. - Pay: there is "Salary Range Transparency" but no actual numbers; they explain how they determine salary ranges but no specific range. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. They gave a description of how they determine salary ranges but not actual numbers. Is that considered stating them? It says "Salary Range Transparency" but no actual range. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Since they didn't give a specific range, we should not include Pay section. - Schedule: not mentioned. - Skills: maybe we can include under "Skills" if there is explicit list. There's mention of technologies: HTML, object-oriented programming languages, modern web development technologies and frameworks, graphics software, etc. Could be considered skills. But we need to decide if we should create a Skills section. The instruction: Prefer a few substantive sections over many thin ones. Could combine qualifications and responsibilities. But we have separate headings allowed. We need to include all substantive information. Let's extract: About the role: description paragraph. Responsibilities: list bullet points from "Key Responsibilities". Requirements: includes US Citizenship, security clearance, polygraph, drug testing, background investigation. Also maybe "Minimum Qualifications" and "Preferred Qualifications". Could treat "Requirements" as mandatory (US Citizenship, clearance). Could also put qualifications under "Qualifications". But we have both Requirements and Qualifications headings allowed. We need to decide. We could have:

About the role

...

Responsibilities

    ...

Requirements

    ...
(US Citizenship, security clearance, polygraph, background investigation, drug testing)

Qualifications

    ...
(Minimum and Preferred qualifications)

Benefits

    ...
(Medical, Vision+Dental, Retirement, PTO, Career Growth, Life insurance, Profit Sharing, Referral Bonus) We should not include Pay or Schedule. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, equal opportunity, scam warning, navigation, cookie, legal, duplicated lines. Also remove "This Position is Contingent on Contract Award**" maybe not needed but it's substantive? It's a contingency note. Could include in About the role? Might be considered metadata; but we can keep as part of About the role paragraph. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like "Founded in 2007, Columbia Technology Partners is a Service-Disabled Veteran Owned Small Business..." That's about company; maybe could be part of About the role? But it's about company, not role. Could be omitted? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. Where? Could be in About the role section? Might be okay as it's about the company but still relevant. Could add a separate section "About the company" but not in allowed headings. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we must fit it into one of those. Probably "About the role" can include company overview as context. That seems acceptable. We also need to keep the "Salary Range Transparency" explanation? Since we cannot create Pay section, but we could include that explanation in About the role or Qualifications? It's about compensation methodology, not a specific range. Might be considered substantive but not a pay range. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It doesn't forbid mentioning salary details elsewhere. So we could include a paragraph about how they determine salary ranges within About the role or maybe a separate paragraph not under a heading? But we must output only HTML fragment; we can include

anywhere not under heading? The instruction: Use

for section headings,
  • for any list,

    for prose. It doesn't forbid stray

    outside headings, but likely they expect sections. Safer to include that explanation as a

    under About the role. Now let's extract details. About the role paragraph: combine the initial description and company overview and salary transparency explanation. Initial description: "This Position is Contingent on Contract Award** Description Columbia Technology Partners is seeking a Web Developer to design, develop, maintain, and enhance innovative web-based applications and websites supporting mission-critical operations. The ideal candidate will collaborate with technical teams and stakeholders to gather requirements, evaluate and implement effective web technologies, and create intuitive, content-rich web solutions that enhance communication and information sharing. This role combines front-end and back-end development, application integration, testing, troubleshooting, deployment, configuration management, and ongoing website maintenance to deliver secure, high-performance solutions that meet customer requirements while leveraging modern web technologies, development frameworks, and best practices." Company overview: "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." Salary transparency: "At Columbia Technology Partners we are committed to transparency and fairness in our compensation practices. We believe in creating a work environment where employees feel valued, empowered, and rewarded for their contributions. How We Determine Salary Ranges 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." We can combine these into a few paragraphs. Now Responsibilities list: from "Key Responsibilities" bullet list: - Design, develop, test, maintain, and support web-based applications and websites. - Gather and analyze customer requirements to determine effective web technology solutions. - Develop user-friendly, visually appealing interfaces with intuitive navigation and functionality. - Create and maintain website technical documentation to support ongoing maintenance and upgrades. - Code and maintain websites using HTML and other web development technologies and frameworks. - Integrate new web products and capabilities into existing applications and environments. - Develop website components including user interfaces, databases, animation, special effects, and business applications. - Troubleshoot and resolve software issues using modern web development tools and technologies. - Collaborate with software development leads, management, and technical teams to ensure successful project execution. - Support website planning, deployment, configuration management, and lifecycle maintenance activities. - Analyze and resolve complex web application issues while working independently on advanced development projects. - Utilize graphics software, object-oriented programming languages, and internet technologies to deliver comprehensive web solutions. We need to keep each as

  • . Now Requirements: from "Requirements" section: "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 12564. Employment is contingent upon successful completion of a security background investigation and polygraph.Certification Requirements:N/A This position requires an active Security Clearance with appropriate Polygraph." We need to keep substantive: US Citizenship required, random drug testing, security background investigation and polygraph, active Security Clearance with appropriate Polygraph. Also mention that certification requirements N/A (maybe not needed). We'll include those as list items. Now Qualifications: Minimum Qualifications and Preferred Qualifications. Minimum: - Bachelor's degree in a technical discipline from an accredited college or university. - Eight (8) years of Web Developer experience supporting programs and contracts of similar scope, type, and complexity. - Four (4) additional years of Web Developer experience may be substituted in lieu of a bachelor's degree. - Experience developing and supporting web applications utilizing modern web development technologies and frameworks. - Experience creating and maintaining technical documentation, implementing website enhancements, and troubleshooting application issues. Preferred: - Experience developing user interfaces, web services, and database-driven web applications. - Experience with object-oriented programming languages and modern web technologies. - Experience integrating new web solutions into existing enterprise environments. - Experience supporting high-performance, scalable web applications. - Familiarity with configuration management and software development lifecycle best practices. - Experience working collaboratively with software engineers, system administrators, and technical stakeholders. We can combine both under Qualifications heading, maybe separate subheadings? Not allowed; only

    for section headings. Could just list all qualifications as list items, maybe differentiate with text? Could include a note "Minimum Qualifications:" then list, then "Preferred Qualifications:" then list. That's okay within
      but we need to keep the labels. Could use
    • Minimum Qualifications: ...
    • but that might be okay. Simpler: create two separate
        under same heading? The instruction: Use
        • for any list of duties/requirements/benefits. It doesn't forbid multiple lists under same heading. We'll do:

          Qualifications

          Minimum Qualifications:

            ...

          Preferred Qualifications:

            ...
          That's acceptable. Now Benefits: from "Really Good Benefits, For Really GREAT People" section: - Medical: CTP offers 3 superior plans, bringing our employees both in-network and out-of-network options. - Vision + Dental: Both free to you + paid in full by CTP. - Retirement: 401k - 6% company contribution - PTO + Leave: A work life balance is extremely important to our team here at CTP, which is why our paid

Similar jobs

Web Developer 2

SundayyUnited States· 1 mo ago
RemoteInformation Technologyapply on sundayy.com

Web Developer II

Chenega MIOS SBUWashington, United States· 2 wk ago
Engineeringapply on chenega.jibeapply.com

Web Developer II

Catalyst Mobility™United States· 1 mo ago
RemoteEngineering$72k–$86k/yrapply on jobs.lever.co

Web Developer II

University of HoustonHouston, TX· 1 mo ago
Engineeringapply on careers.uh.edu