Senior Prototyping Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: Active security clearance requirement (maybe under Requirements). Responsibilities: description of role (architect, prototype, lead team). Requirements: active clearance, required skills list. Qualifications: education/experience requirements. Skills: required skills and desired skills. Benefits: description of Nyla FLEX program, health care, 401k matching, professional development, student loan repayment, volunteering. Pay: salary range $203k-$240k. Schedule: mention of flexibility (scale down to 30-32 hours) etc. Also mention of leave etc. So we can include sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Possibly also "About the role" but we have responsibilities covering that. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. Also not include Job ID etc. Remove boilerplate like EEO, equal opportunity, scam warning, navigation, cookie, legal. At end there is "Nyla is an equal opportunity employer." Remove that. We need to preserve all substantive information. Must not invent or summarize away detail. Must not create sections with filler like "commensurate with experience". We have actual content. We need to use

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

  for prose. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  Responsibilities

  ... prose describing responsibilities ... maybe bullet list? The responsibilities include: architect, prototype, tune advanced statistical, ML, graph-based algorithms; evaluate performance; partner with software/cloud engineers to scale prototypes; serve as technical leader guiding team, defining analytic roadmaps, incorporating emerging ML techniques; solving complex data puzzles, leading technical teams, bringing authentic self to high-stakes defense tech. Could be prose. We could also bullet list duties. Use

  • for list. Similarly Requirements: active security clearance TS/SCI polygraph required; required skills list (Advanced Algorithm Development, SME Collaboration & Feature Engineering, Prototype-to-Production Transition, Rigorous Validation & Metrics, Data Visualization & Insight Delivery, Technical Leadership & Strategy). Use
    • . Qualifications: education/experience alternatives. Could be prose or list. Use

      maybe. Skills: maybe separate Required Skills and Desired Skills. Could combine under Skills heading with subheadings? But we only have

      for sections; we could have

      Skills

      then

      Required Skills: ...

      Desired Skills: ...

      Or we could bullet each. Benefits: description of Nyla FLEX program, health care, 401k matching, professional development, student loan repayment, volunteering. Use
      • for each benefit. Pay: salary range. Use

        . Schedule: flexibility details: Nyla FLEX program details about pay, leave, schedule. Actually schedule part is within benefits description. But we can still have Schedule section with details about flexible hours: ability to scale down to 30-32 hours while still enjoying benefits, etc. Also mention of cash out annual leave, opt out benefits, arrange additional hours on contract, earn 1.3 times hourly rate after 1880 hours, buy additional annual leave up to 6 weeks, paid anniversary leave, etc. That's a lot. Could be under Benefits though. But we need to follow instruction: include a section ONLY when posting has real specific content for it. The posting does have schedule content (flexibility). So we can include Schedule section. We must not repeat info across sections unnecessarily? It's okay if some overlap but better to keep distinct. Let's extract details: From posting: - Pay: "The annual base salary range for this role is $203,000-$240,000 (USD), which does not include discretionary bonus compensation or our comprehensive benefits package. Actual compensation offered to the successful candidate may vary from posted hiring range based upon geographic location, work experience, education, and/or skill level, among other things." - Benefits: Nyla FLEX program details: PAY - Nyla starts with 4 weeks of Annual Leave plus 11 holidays and an additional day of Annual Leave for each year you’re at the company. You have the flexibility to cash out your annual leave hours, opt out of other Nyla benefits, and/or arrange for additional hours on contract* (over 40 hrs/week). There’s even an option to earn 1.3 times your hourly rate once you work over 1880 hours on contract! LEAVE - Want to spend more time with the family? Want more time to travel the world? You can BUY additional annual leave for a total of 6 weeks of annual leave. That’s up to 240 hours of leave plus 11 holidays! That’s not even including paid anniversary leave! SCHEDULE - Does the traditional 40-hour workweek no longer fit your lifestyle? With Nyla FLEX, you have the freedom to scale down to 30-32 hours while still enjoying the top-notch Nyla benefits you know and love. It's flexibility that works for you without compromising the perks! WHAT ABOUT OTHER BENEFITS? Nyla’s health care (medical, dental, and vision) is 100% covered by the company. We provide 10% 401k matching - with full vesting day 1! Our Professional Development offers $5,000 per year to be used towards fees, tuition, or time off for your continued growth. We even have a student loan repayment program and we provide 8 hours of volunteering annually so you can support your community, making your world a better place. Thus Benefits section can include health care, 401k matching, professional development, student loan repayment, volunteering. The FLEX program details about pay, leave, schedule could be split into Pay, Leave, Schedule sections. But we already have Pay section for salary; but the FLEX PAY part is about leave cash out etc. Might be better to include under Benefits or separate sections. The instruction: Use headings for Benefits, Pay, Schedule. So we should have Pay (salary), Schedule (flex hours), Benefits (other benefits). The FLEX PAY details about leave cash out etc could be considered part of Benefits or maybe Schedule? Actually it's about pay flexibility (cash out leave, opt out benefits, additional hours, earn 1.3x). That's more about compensation flexibility, but we already have Pay for base salary. Could still include under Benefits as "Flexible compensation options". But to follow instruction, we can put those under Benefits as part of Nyla FLEX program. However we also have Schedule section for schedule flexibility (30-32 hours). Leave details could be under Benefits or maybe separate Leave section but not required. We'll include Leave details under Benefits as part of FLEX. Thus:

        Benefits

        • Nyla FLEX program: 4 weeks annual leave + 11 holidays + additional day per year of service; ability to cash out annual leave hours, opt out of other benefits, arrange additional hours on contract (>40 hrs/week); option to earn 1.3× hourly rate after 1880 contract hours.
        • Option to buy additional annual leave for up to 6 weeks total (240 hours) plus 11 holidays; includes paid anniversary leave.
        • Freedom to scale down to 30‑32 hour workweek while retaining full benefits.
        • Health care (medical, dental, vision) 100% company‑paid.
        • 10% 401k matching with full vesting day 1.
        • Professional Development: $5,000 per year for fees, tuition, or time off.
        • Student loan repayment program.
        • 8 hours of volunteering time provided annually.
        But note we also have Schedule section separate; we might duplicate schedule info. To avoid duplication, we could put schedule details only under Schedule section, and leave details under Benefits. However the posting includes schedule details under "SCHEDULE - ...". So we should put that under Schedule section. The leave details under "LEAVE - ..." could be under Benefits or maybe a separate Leave heading but not required. We'll put leave details under Benefits. Pay section: base salary range. Now Responsibilities: we need to capture all responsibilities from description: "architect, prototype, and tune advanced statistical, machine learning, and graph-based algorithms, evaluate performance with rigorous metrics, and partner directly with software and cloud engineers to scale prototypes into resilient production systems. Beyond algorithm design, you will serve as a technical leader—guiding a team of data scientists, defining analytic roadmaps, and incorporating emerging state-of-the-art machine learning techniques to power mission automation. If you thrive on solving complex data puzzles, leading technical teams, and bringing your authentic self to high-stakes defense tech, Team Nyla wants you on board!" We can bullet list. Requirements: active security clearance TS/SCI polygraph required; required skills list (six items). We'll bullet. Qualifications: education/experience alternatives: Bachelor’s Degree in CS, CE, SE, or related technical discipline, PLUS 10+ years professional software engineering experience OR Master's Degree PLUS 8+ years of professional software engineering experience OR High School Diploma / GED, PLUS 14+ years of hands-on technical software development experience in lieu of a degree. We can bullet or prose. Skills: we already listed required skills under Requirements; but we also have Desired Skills list: Data Simulation & Synthetic Generation; Graph & Pattern Recognition Analytics; Scalable Cloud Integration. We could put under Skills heading with subheadings Required Skills and Desired Skills. But we already used Requirements for required skills; maybe better to have Requirements include clearance and maybe some other non-skill requirements; Skills heading for both required and desired skills. However the instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put required skills under Skills, and maybe also include clearance under Requirements. Let's decide: - Requirements: Active security clearance TS/SCI polygraph required. (maybe also mention "U.S. Government" etc but not needed.) - Skills: list required skills and desired skills. - Qualifications: education/experience. Thus we avoid duplication. Let's craft:

        Requirements

        Active security clearance at the TS/SCI polygraph level is required.

        Skills

        • Required Skills
          • Advanced Algorithm Development: Proven track record of designing, implementing, and tuning statistical, machine learning, data mining, heuristic, and graph‑based algorithms using Python, R, SAS, or MATLAB.
          • SME Collaboration & Feature Engineering: Demonstrated ability to partner with Subject Matter Experts (SMEs) to extract critical insights from raw data (e.g., SQL tables, network logs, structured metadata) and formulate high‑impact feature vectors.
          • Prototype‑to‑Production Transition: Hands‑on experience translating qualitative user workflows into quantitative mathematical formulations and partnering with cloud/software engineers to deploy scalable analytics into analyst workflows.
          • Rigorous Validation & Metrics: Expertise in validating model performance using standard evaluation metrics and statistical techniques (e.g., cross‑validation, ROC curves, confusion matrices).
          • Data Visualization & Insight Delivery: Ability to design intuitive visualizations and generate clear reports that summarize