Software Engineer II - Front End

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented summary. Remove boilerplate (cookie/navigation/legal/EEO etc). Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes compensation range: "Compensation Range: The pay range for this position at commencement of employment is expected to be between $115,000 and $140,000 per year." Also mentions total compensation package may include bonus, equity, benefits, 401(k), PTO. So we have Pay and Benefits content. Schedule: mentions hybrid position requiring onsite presence at HQ at least 3 days per week. So we have schedule info. Also location: Hybrid in Long Island City (Queens) NY, must reside in NY, NJ or CT. That's location info but not a section heading; we could include in About the role or maybe a short p. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - About the role: The posting includes "About The Role" paragraph describing role. So we can have

About the role

with

content. - Responsibilities: The "What You Would Do" bullet list. So we can have

Responsibilities

with

• items. - Requirements: The posting includes Education, Experience, etc. Could be under Requirements or Qualifications. The instruction says we can have Requirements and Qualifications separate. We need to decide based on content. The posting has Education, Experience, Knowledge, Skills & Abilities. Could split: Requirements (Education, Experience) and Qualifications (maybe Knowledge, Skills & Abilities). Or we could combine. But we must not create thin sections. Let's see: Education and Experience are concrete. Knowledge, Skills & Abilities also concrete. So we could have Requirements (Education + Experience) and Skills (Knowledge, Skills & Abilities). The instruction list includes Skills as a possible heading. So we can have Skills section for that. Qualifications maybe not needed if we already have Requirements and Skills. But we could also have Qualifications for things like "Proven track record..." etc. However to avoid thin sections, we can combine Education+Experience into Requirements, and Knowledge, Skills & Abilities into Skills. That seems reasonable. - Benefits: The posting mentions total compensation package may include bonus, equity, full range of medical, financial, and/or other benefits (including 401(k) eligibility and various paid time off benefits). So we have Benefits content. - Pay: Compensation range. - Schedule: Hybrid position requiring onsite presence at least 3 days per week. We must not include filler like "commensurate with experience". Not present. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information. So we need to include location info (Hybrid in Long Island City (Queens) NY, must reside in NY, NJ or CT). Where to put? Could be in About the role paragraph or maybe a short p after About the role. Since we have About the role section, we can incorporate location there. Also "Reports to: Engineering Team Lead" and "Direct Reports: No" etc. That's metadata; we could fold into a short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short p for Reports to, Direct Reports, Location maybe. But we already have location in About the role. Could also include Reports to and Direct Reports in a short p. We must not include boilerplate like EEO etc. Remove that. We must not include application instructions. Now produce HTML fragment. Structure:

  About the role

  ... (including description, location, reports to, direct reports maybe)

  Responsibilities

  • ...
  ...

  Requirements

  • Bachelor’s degree in Computer Science, Software Engineering, or a related technical field, or equivalent practical experience
  • 2+ years of professional software engineering experience building, shipping, and maintaining customer-facing web applications (preferably in mission-critical or regulated environments)

  Skills

  • Strong team player with excellent communication skills and a proactive approach to unblocking teammates and triaging technical issues
  • Working knowledge of or desire to expand skills into backend technologies (Python, Node.js)
  • Solid software engineering fundamentals: testing, debugging, code reviews, git workflows, and architectural planning
  • High proficiency in modern front-end web technologies, including TypeScript, HTML5, CSS, and React
  • Familiarity with desktop application frameworks (Electron) and state management architecture (Redux) preferred
  • Strong interest in life sciences; prior software experience in biotech, pharmaceuticals, or medical technology preferred
  • Demonstrated experience writing performant, well-tested, and resilient front-end code in a production environment
  • Proven track record of collaborating across multi-disciplinary teams to translate UI/UX designs into production features
  • Experience maintaining or interacting with CI/CD pipelines and cloud-based deployment workflows preferred
  • Active contributions to or maintenance of open-source software preferred
  But note some of these items overlap with responsibilities? Actually the "Knowledge, Skills & Abilities" list includes many items. We should ensure we don't duplicate content from responsibilities. The responsibilities list is separate. Now Benefits:

  Benefits

  • Bonus
  • Equity
  • Full range of medical, financial, and/or other benefits
  • 401(k) eligibility
  • Paid time off benefits (vacation, sick time, parental leave)
  But we need to preserve the exact phrasing: "The total compensation package for this position may also include other elements, including bonus, equity and full range of medical, financial, and/or other benefits (including 401(k) eligibility and various paid time off benefits, such as vacation, sick time, and parental leave), dependent on the position offered." So we could make a

  with that sentence, or break into list. The instruction: Use

  • for any list of duties/requirements/benefits. So we should list benefits as list items. We can break down: bonus, equity, full range of medical, financial, and/or other benefits, 401(k) eligibility, various paid time off benefits (vacation, sick time, parental leave). That seems fine. Pay:

    Pay

    The pay range for this position at commencement of employment is expected to be between $115,000 and $140,000 per year. Base pay offered may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and years of experience. We typically target mid-range for well-qualified candidates. Following employment, growth beyond the hiring range is possible based on performance.

    Schedule:

    Schedule

    This is a hybrid position, requiring onsite presence at our Long Island City HQ at least 3 days per week.

    We also need to include location residency requirement: "Must reside in: NY, NJ or CT". Could be included in About the role paragraph or Schedule. Probably About the role. Now About the role paragraph: Should include description from "About The Role" plus location and reporting lines. Original About The Role paragraph: "Our robotic platform, API, and the apps built on top of them empower scientists to discover, build, and run their own automated experiments. The engineering team is constantly building, iterating on, and shipping these powerful and user friendly products. We are looking for a skilled Front End Software Engineer (SWE II) who can grow with the organization as a core member of the software team, and write applications in a way that is focused on customer needs and strikes a healthy balance of flexibility without unnecessary complexity. This is a hybrid position, requiring onsite presence at our Long Island City HQ at least 3 days per week. The Front-End Software Engineer reports directly to the Engineering Team Lead." We also have location residency requirement separate: "Must reside in: NY, NJ or CT". Also "Reports to: Engineering Team Lead" already in paragraph. Direct Reports: No. We can incorporate location and direct reports in a short p after the About the role paragraph, or include in same paragraph. Let's craft About the role

    combining the description and location/residency and direct reports. Paragraph: "Our robotic platform, API, and the apps built on top of them empower scientists to discover, build, and run their own automated experiments. The engineering team is constantly building, iterating on, and shipping these powerful and user friendly products. We are looking for a skilled Front End Software Engineer (SWE II) who can grow with the organization as a core member of the software team, and write applications in a way that is focused on customer needs and strikes a healthy balance of flexibility without unnecessary complexity. This is a hybrid position, requiring onsite presence at our Long Island City HQ at least 3 days per week. The Front-End Software Engineer reports directly to the Engineering Team Lead. The role has no direct reports. Candidates must reside in NY, NJ, or CT." That preserves all. Now ensure we didn't include any boilerplate like EEO etc. We removed. Now check for any repeated content: Responsibilities list from "What You Would Do". Let's extract each bullet: - Develop performant and reliable software that will enable our users to efficiently execute scientific workflows. - Implement new features for customer-facing web applications built with Typescript, HTML, and CSS. - Assist in developing and maintaining software systems. - Collaborate on design improvements and translate UI/UX concepts into high-quality front-end code. - Review code contributions from members of the team and establish an effective development / deployment workflow. - Proactively help unblock teammates. - Help triage and solve tricky bugs when teammates need assistance. - Collaboratively plan for and build toward long-term goals, including architectural and other design decisions that will have wide-reaching impact. - Other duties as assigned. We'll list those. Now Requirements: Education and Experience. Education: "Bachelor’s degree in Computer Science, Software Engineering, or a related technical field, or equivalent practical experience" Experience: "2+ years of professional software engineering experience building, shipping, and maintaining customer-facing web applications (preferably in mission-critical or regulated environments)" Also there is "Demonstrated experience writing performant, well-tested, and resilient front-end code in a production environment" - that could be under Skills or Requirements. It's under Knowledge, Skills & Abilities originally. We'll put under Skills. "Proven track record of collaborating across multi-disciplinary teams to translate UI/UX designs into production features" also Skills. "Experience maintaining or interacting with CI/CD pipelines and cloud-based deployment workflows preferred" Skills. "Active contributions to or maintenance of open-source software preferred." Skills. Now Skills list: we need to include all from Knowledge, Skills & Abilities plus those items we just mentioned. Let's compile Skills items: - Strong team player with excellent communication skills and a proactive approach to unblocking teammates and triaging technical issues - Working knowledge of or desire to expand skills into backend technologies (Python, Node.js) - Solid software engineering fundamentals: testing, debugging, code reviews, git workflows, and architectural planning - High proficiency in modern front-end web technologies, including TypeScript, HTML5, CSS,