Jobs · Engineering · New York

Manager Software Engineering

Optimum · Bethpage, NY · 1 mo ago
Engineering$134k–$220k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Job Summary (maybe About the role). Responsibilities list. Qualifications list. Also mentions Pay range. Benefits? Not explicit benefits listed. Schedule? Not mentioned. Skills? Could be part of qualifications but we could separate Skills if present. The posting includes many qualifications; we could treat them as Requirements or Qualifications. We need to decide sections: About the role (Job Summary). Responsibilities. Requirements (maybe combine Qualifications and Skills). Pay (since they gave range). Benefits? Not given, so omit. Schedule? Not given, omit. Skills? Could be separate but we have qualifications covering skills; but we could still include Skills if we extract skill list. However instruction: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one section called Requirements or Qualifications. Use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not repeat job title as heading. Do not put Job ID etc. Remove boilerplate: EEO, fraud, visa, etc. Also remove "All job descriptions..." etc. Also remove "At Optimum, every action..." maybe keep as part of About the role? It's somewhat fluff but could be considered part of About the role. But we should preserve substantive information; that paragraph about guiding principles maybe not essential but it's substantive? It's about company culture; could be included in About the role. However we might keep it as part of About the role prose. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all details from responsibilities, qualifications, pay range, etc. We can condense into lists but must preserve all items. Not allowed to omit any duty/requirement. So we need to extract each responsibility bullet and each qualification bullet. Let's parse responsibilities: - Lead effective brainstorming sessions to generate innovative ideas and solutions. - Drive multi-scrum technology feasibility, delivery, and quality in partnership with product and design teams. - Establish and gain acceptance for technology roadmaps aligned with product roadmaps. - Establish and gain acceptance for technical solutions, serving as a go-to expert for specific capabilities. - Articulate technology vision, principles, and roadmaps to diverse audiences, tailoring communication appropriately. - Achieve objectively good negotiation results efficiently while maintaining relationships and driving decision-making. - Effectively and respectfully drive technical team interactions, persuasively influencing architecture, software design, implementation, and incident recovery. - Thoroughly vet and refine requirements to clearly articulate their intent. - Establish clear cost and time commitments to stakeholders, ensuring they are met with assistance. - Consistently communicate with stakeholders about expectations. - Build, lead, and improve a successful team of software engineers. - Feedback and Development: Provide candid and empathetic feedback across all levels, fostering a culture of growth and development. - Proactively build strong relationships with product, design, and business/operations counterparts within and across teams. - Articulate the financial benefits and costs of capabilities, incorporating this information into decision-making. - Adhere to regulatory and corporate policy obligations, ensuring compliance without relying on other technologists. That's a list. Qualifications list: - Bachelor's Degree in Computer Science or a related field - Minimum of eight years of professional software development experience, including 3+ years in a leadership role - Proven, hands-on experience designing and implementing customer-facing or Agent facing solutions in the Telecom industry - Strong architectural understanding of Address lookup, Products, Offers, Catalog, Cart, Fulfillment, and Payments, Order flows - Knowledgeable in integrations, A/B testing, Analytics, and integration with CMS and CRM systems - Experience in UI development programming languages (ReactJs, Node.js, TypeScript, JS) and a strong grasp of how to decompose UI designs into reusable components and integrate apis, scripts and sdks in the UI - Experience owning the operational health of a critical, 24/7 service, including defining monitoring and service-level objectives (SLOs), managing incident response, and serving as an escalation point in partnership with SRE or Operations teams - Strong technical background in relevant technologies (e.g., Okta, Go, Java, cloud platforms, CI/CD) - Proven ability to lead and inspire engineering teams, foster collaboration, and drive results - Excellent verbal and written communication skills, with the ability to tailor communication to different audiences - Strong analytical and problem-solving skills, with a focus on finding creative solutions to complex challenges - Experience managing software development projects, including scoping, planning, and execution - Experience working in an Agile development environment - Experience leading the deployment of regularly planned releases Also there is mention of Guiding Principles etc. Could be part of About the role. Pay: "The starting pay rate/range at time of hire for this position in the posted location is $133,661.00 - $219,586.00 / year." We need to include Pay section with that info. Benefits: none specific; we should not create Benefits section. Schedule: none. Thus sections: About the role (Job Summary + maybe guiding principles). Responsibilities. Requirements (or Qualifications). Pay. We need to use

    for each section heading. We need to use
    • for any list of duties/requirements/benefits. So Responsibilities list as ul. Requirements list as ul. For About the role, we can use

      prose. Pay: maybe a

      with the range. We must not include any filler like "commensurate with experience". Not present. We must not repeat job title as heading. Not include. We must not include metadata like Job ID. We must remove boilerplate: EEO, fraud, visa, etc. Also remove "All job descriptions and required skills..." etc. Also remove "We are an Equal Opportunity Employer..." etc. Also remove "The Company collects personal information..." etc. Also remove "Applicants for employment..." etc. Also remove "Please review our Fraud FAQ..." etc. Also remove "We appreciate your interest..." etc. Also remove "Applicants must be authorized..." etc. Also remove "Please note that at this time, we do not provide visa sponsorship..." etc. Also remove "At Optimum, every action and interaction we take part in, is driven by our three Guiding Principles..." maybe keep as part of About the role? It's substantive about culture; but it's not a requirement. Could be included in About the role prose. We'll keep it. Now craft HTML. Structure:

      About the role

      ...

      Responsibilities

      • ...
      • ...

      Requirements

      • ...
      • ...

      Pay

      The starting pay rate/range at time of hire for this position in the posted location is $133,661.00 - $219,586.00 per year.

      Make sure to preserve all details exactly as in text. Need to check punctuation. Let's copy responsibilities exactly as bullet points. Responsibilities list: - Lead effective brainstorming sessions to generate innovative ideas and solutions. - Drive multi-scrum technology feasibility, delivery, and quality in partnership with product and design teams. - Establish and gain acceptance for technology roadmaps aligned with product roadmaps. - Establish and gain acceptance for technical solutions, serving as a go-to expert for specific capabilities. - Articulate technology vision, principles, and roadmaps to diverse audiences, tailoring communication appropriately. - Achieve objectively good negotiation results efficiently while maintaining relationships and driving decision-making. - Effectively and respectfully drive technical team interactions, persuasively influencing architecture, software design, implementation, and incident recovery. - Thoroughly vet and refine requirements to clearly articulate their intent. - Establish clear cost and time commitments to stakeholders, ensuring they are met with assistance. - Consistently communicate with stakeholders about expectations. - Build, lead, and improve a successful team of software engineers. - Feedback and Development: Provide candid and empathetic feedback across all levels, fostering a culture of growth and development. - Proactively build strong relationships with product, design, and business/operations counterparts within and across teams. - Articulate the financial benefits and costs of capabilities, incorporating this information into decision-making. - Adhere to regulatory and corporate policy obligations, ensuring compliance without relying on other technologists. Note: "Feedback and Development:" includes colon; we keep as part of bullet. Now qualifications list: - Bachelor's Degree in Computer Science or a related field - Minimum of eight years of professional software development experience, including 3+ years in a leadership role - Proven, hands-on experience designing and implementing customer-facing or Agent facing solutions in the Telecom industry - Strong architectural understanding of Address lookup, Products, Offers, Catalog, Cart, Fulfillment, and Payments, Order flows - Knowledgeable in integrations, A/B testing, Analytics, and integration with CMS and CRM systems - Experience in UI development programming languages (ReactJs, Node.js, TypeScript, JS) and a strong grasp of how to decompose UI designs into reusable components and integrate apis, scripts and sdks in the UI - Experience owning the operational health of a critical, 24/7 service, including defining monitoring and service-level objectives (SLOs), managing incident response, and serving as an escalation point in partnership with SRE or Operations teams - Strong technical background in relevant technologies (e.g., Okta, Go, Java, cloud platforms, CI/CD) - Proven ability to lead and inspire engineering teams, foster collaboration, and drive results - Excellent verbal and written communication skills, with the ability to tailor communication to different audiences - Strong analytical and problem-solving skills, with a focus on finding creative solutions to complex challenges - Experience managing software development projects, including scoping, planning, and execution - Experience working in an Agile development environment - Experience leading the deployment of regularly planned releases Now About the role prose: combine Job Summary and Guiding Principles paragraph. Job Summary: "We are seeking a highly experienced Manager of Software Engineering to lead our talented One Agent team. In this role, you will own and drive the evolution of our Agent Facing One Agent platform built using Svelte and Go . The ideal candidate possesses a strong technical background in customer facing architecture and UI/BE development technologies, along with outstanding leadership skills and a passion for delivering secure and seamless software. You will be responsible for the One Agent roadmap, collaborating with cross-functional teams to ensure the delivery of high-quality software that meet the needs of our customers and business objectives." Guiding Principles paragraph: "At Optimum, every action and interaction we take part in, is driven by our three Guiding Principles: Do What’s Right, Drive One Optimum, and Make It Happen. These aren’t just words, they help us build trust, create real community, and embrace new ways of thinking. Our employees are empowered to do the right thing for our customers and co-workers and to recognize and reward these behaviors when we see them. It’s all part of the bigger picture of “Be The Difference” where each employee knows they have the power to enact real change, share new ideas, and understand that learning never stop." We need to preserve exactly; note there is a typo "learn never stop" but we keep as is. Combine into one paragraph maybe two sentences; but we can keep as two paragraphs? The instruction: use

      for prose. Could have multiple

      elements. We'll put both in separate

      under About the role. Now ensure we didn't include any boilerplate. Check for any leftover lines like "We are Optimum, a leader..." that is part of the intro before Job Summary. That is also substantive? It's marketing fluff but maybe considered part of About the role. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we

Similar jobs