Jobs · Engineering · New York

Mechanical Engineer III

Frontgrade Technologies · Hauppauge, NY · 1 mo ago
Engineering$105k–$131k/yrFull-time
We need to output HTML fragment with sections: About the role? The job description includes "Job Description" then description. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections where posting has real specific content. Let's parse. Content: - Job Description: description of role: "The Mechanical Engineer III provides mechanical engineering expertise in the early stages of design. They also coordinate project design and analyze complex construction problems. They will perform a variety of complex duties in support of the development and manufacturing of space mechanisms, actuators, motors, twist caps, and motor controllers operating in a space environment." That's about the role. Could be "About the role" heading. - Compensation: $104756-$130945 => Pay section. - Responsibilities: list bullet points. - Experience QUALIFICATIONS: includes qualifications: Minimum five (5) years... OR (9) years... OR (3) years... Ability to obtain/maintain Security Clearance. Experience in design of electronic/electromechanical products (duplicate). Also "Experience QUALIFICATIONS" heading maybe combine as Qualifications. - About Frontgrade: description of company; could be "About the company" but not in allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Frontgrade" maybe not needed; but we could put under "About the role"? Not exactly. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those? It says use those for section headings. Likely we should only use those headings. So we need to map content to those headings. We have: - About the role: description of role (first paragraph). Could also include some of the "About Frontgrade" maybe not needed but could be considered "About the role"? Probably not. But we could include "About the role" as the initial description. - Responsibilities: list bullet points. - Qualifications: the qualifications/experience section. - Benefits: list of benefits (Immediate Medical..., 401K..., 9X80..., Career Opportunity..., Tuition..., Generous PTO..., 8 weeks of 100% Paid Family Leave). Also maybe "Additional Information" about ITAR etc not benefit. - Pay: compensation range. - Schedule: mention "9X80 compressed work schedule for qualifying roles". That's schedule. - Skills: maybe not explicitly listed; we could omit if no specific skills. - Requirements: maybe not separate; qualifications cover. We must not create sections with filler. So include only those with real content. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to output HTML fragment: use

for each heading, then content:

for prose,

  • for lists. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting. Let's extract details precisely. About the role paragraph: "The Mechanical Engineer III provides mechanical engineering expertise in the early stages of design. They also coordinate project design and analyze complex construction problems. They will perform a variety of complex duties in support of the development and manufacturing of space mechanisms, actuators, motors, twist caps, and motor controllers operating in a space environment." That's it. Responsibilities list: - Develop comprehensive mechanical designs - Provide technical support to project teams as required from initial design to production - Mentor ME I and ME II employees by providing training on job functions and reviewing work - Develop mechanical designs for new products, fabrication fixturing, and test fixturing - Create and review engineering documentation packages - Provide inputs to engineering design reviews including calculations, analyses, drawings, etc. to show compliance with specifications and project objectives and standards - Interact with customers and vendors as necessary based on project scope; makes presentations to communicate engineering findings - Perform advanced analyses (thermal, structural, and tolerance) with minimal guidance of advanced engineers Note: The original had "Experience QUALIFICATIONS" then list. We'll treat that as Qualifications. Qualifications: - Minimum five (5) years of experience in a specialized functional discipline. - OR (9) years of experience may be considered in lieu of a Bachelors Degree. - OR (3) years of experience may be considered w/ a Masters Degree. - Ability to obtain and/or maintain a Security Clearance - Experience in the design of electronic or electromechanical products (mentioned twice but we should include once? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicate lines: we should remove duplicated lines. So we include only once. Also there is "Experience QUALIFICATIONS" heading but we treat as qualifications. Benefits list: - Immediate Medical (FSA and HSA) - Dental - Vision - 401K Match with 100% immediate vesting - 9X80 compressed work schedule for qualifying roles (but that's schedule, maybe also benefit) - Career Opportunity and Growth - Tuition Reimbursement/Student Loan Repayment - Generous PTO and 11 paid Holidays per year (9 designated holidays and 2 floating holidays) - 8 weeks of 100% Paid Family Leave We need to separate schedule: "9X80 compressed work schedule for qualifying roles" goes under Schedule section. Thus Benefits list excludes that line. Pay: "$104756-$130945" Schedule: "9X80 compressed work schedule for qualifying roles" Now we need to ensure we don't include boilerplate like "Additional Information This position may require access to technology..." etc. That's not benefit, not required? It's substantive? It's about ITAR/EAR export laws. Might be considered relevant but not in allowed headings. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The ITAR/EAR line is legal/export control; maybe considered legal boilerplate? It's a condition of employment. Might be considered substantive? It's not explicitly listed as boilerplate but it's legal. The instruction says remove legal boilerplate. So we should drop that line. Also "Other Benefits Include" line before benefits list; we already captured benefits. Now produce HTML. Structure:

    About the role

    The Mechanical Engineer III provides mechanical engineering expertise in the early stages of design. They also coordinate project design and analyze complex construction problems. They will perform a variety of complex duties in support of the development and manufacturing of space mechanisms, actuators, motors, twist caps, and motor controllers operating in a space environment.

    Responsibilities

    • Develop comprehensive mechanical designs
    • Provide technical support to project teams as required from initial design to production
    • Mentor ME I and ME II employees by providing training on job functions and reviewing work
    • Develop mechanical designs for new products, fabrication fixturing, and test fixturing
    • Create and review engineering documentation packages
    • Provide inputs to engineering design reviews including calculations, analyses, drawings, etc. to show compliance with specifications and project objectives and standards
    • Interact with customers and vendors as necessary based on project scope; makes presentations to communicate engineering findings
    • Perform advanced analyses (thermal, structural, and tolerance) with minimal guidance of advanced engineers

    Qualifications

    • Minimum five (5) years of experience in a specialized functional discipline.
    • OR (9) years of experience may be considered in lieu of a Bachelors Degree.
    • OR (3) years of experience may be considered w/ a Masters Degree.
    • Ability to obtain and/or maintain a Security Clearance
    • Experience in the design of electronic or electromechanical products

    Benefits

    • Immediate Medical (FSA and HSA)
    • Dental
    • Vision
    • 401K Match with 100% immediate vesting
    • Career Opportunity and Growth
    • Tuition Reimbursement/Student Loan Repayment
    • Generous PTO and 11 paid Holidays per year (9 designated holidays and 2 floating holidays)
    • 8 weeks of 100% Paid Family Leave

    Pay

    $104756-$130945

    Schedule

    9X80 compressed work schedule for qualifying roles

    Check that we didn't miss any substantive info: The "About Frontgrade" description about company mission etc. That is substantive but not covered by allowed headings. Could we put it under "About the role"? Not appropriate. The instruction says use those headings e.g., but not strictly limited? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could use other headings if needed, but they gave examples. However they also say "Prefer a few substantive sections over many thin ones." So maybe we could include an "About Frontgrade" section using

    About Frontgrade

    . But they didn't list that as example. Safer to stick to given headings. The company description may be considered "About the role"? Not really. Could be omitted? But we must preserve ALL substantive information. If we omit company description, we lose substantive info. So we need to include it somewhere. Perhaps we can include it under "About the role" as a paragraph after the role description? That would be mixing but still about the role? Might be acceptable. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." It doesn't forbid adding extra headings beyond the examples, but they gave examples. I'd rather include an "About Frontgrade" section using

    About Frontgrade

    to preserve that info. The examples are not exclusive. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we can use other headings as needed. So we can add About Frontgrade. Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule, About Frontgrade (maybe put before or after). Order? Typically About the role first, then Responsibilities, Qualifications, Benefits, Pay, Schedule, About Frontgrade at end. We must not create sections with filler. All have content. Now ensure we didn't include duplicated lines: we removed duplicate Experience line. Check Benefits list: we included all from "Other Benefits Include" except the schedule line. Now check if any other substantive info: "Additional Information This position may require access to technology, materials, software or hardware that is controlled by either ITAR or EAR U.S. export laws. As a condition of any job offer, in order to be employed in this position, you may need to obtain a U.S. Government export license(s), as required by law." This is legal/export control; maybe considered legal boilerplate; we should remove per instruction to remove legal boilerplate. So drop. Now final HTML. Make sure no extra whitespace issues

Similar jobs

Mechanical Engineer III

Hargrove Engineers & ConstructorsAtlanta, GA· 1 mo ago
Engineeringapply on hargroveepc.wd12.myworkdayjobs.com

Mechanical Engineer III

HEDLos Angeles Metropolitan Area· 3 mo ago
Information Technologyapply on workforcenow.adp.com