Software Engineer (Desktop/Web)
Areté · Northridge, California, United States · 1 mo ago
Engineering$90k–$120k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraph about company and role. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Intro: "At Areté, we are on the forefront of developing innovative solutions, with great minds from all backgrounds, to help solve the nation’s most complex security challenges. We strive for an inclusive, collaborative team environment that approaches differences as opportunities for innovation and excellence. As an employee-owned company, we foster an atmosphere that propels diverse career opportunities and professional growth. Discover your future with us. We are seeking a Software Engineer with web and/or desktop development experience to help create and maintain intuitive and interactive GUI applications with a focus on mission management, data analysis, and data visualization. The ideal candidate will combine strong design skills with technical expertise and have a multidisciplinary background in physics, mathematics, and software engineering. This role requires a passion for solving challenging technical problems in a collaborative environment. This position offers an exciting opportunity to shape user experiences while simultaneously satisfying a critical mission need."
That could be "About the role". Could also be "Responsibilities". But we have a separate "Experiences And Background We Look For (required Skills)" list. That's requirements/qualifications/skills.
We have "Nice To Have (preferred Skills)" list.
We have benefits list: "We have an impressive range of benefits, programs, and perks that we offer: Generous PTO and Leave Times Flextime Scheduling Bereavement Paid Time Off (PTO) Paid Parental Leave Financial Benefits 401K Retirement Plan Contribution Employee Stock Ownership Plan Continuing Education Funds Health, Medical, And Wellness Benefits Medical Insurance Dental & Vision Insurance Life Insurance and Long-Term Disability (LTD) Vision Reimbursement"
We have salary range: "The salary range for this role depends on the candidate’s level of experience: Engineer 1: $90,000 - $120,000 [required BS degree or higher] Engineer 2: $110,000 - $140,000 [minimum experience of BS+2 years, OR MS+0 years] Staff Engineer: $130,000 - $160,000 [minimum experience of BS+5 years, MS+3 years, or PhD+0 years] However, Arete considers several factors when extending an offer of employment, including but not limited to: the position and associated responsibilities, a candidate’s work experience, education/training, and key skills."
We have "Qualities We Look For Creativity Integrity Passion Responsiveness Collaboration" - could be part of Skills or Qualities.
We have other considerations (EEO etc) which we should remove.
We need sections: About the role (intro), Responsibilities? The posting doesn't explicitly list responsibilities beyond "help create and maintain intuitive and interactive GUI applications with a focus on mission management, data analysis, and data visualization." That could be responsibilities. We could put that under Responsibilities.
Requirements: required skills list.
Qualifications: maybe education? Not explicit. Could combine.
Skills: maybe both required and preferred? But we have separate sections for required and preferred. Could put required under Requirements, preferred under Skills? Or we could have Skills for both required and preferred? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections have content.
We have:
- About the role: intro paragraph.
- Responsibilities: maybe the sentence about creating/maintaining GUI applications, mission management, data analysis, data visualization.
- Requirements: required skills list (the "Experiences And Background We Look For (required Skills)").
- Qualifications: maybe education? Not explicit but could be implied: "BS degree or higher" etc in salary ranges. But we could also put qualifications as education requirements: maybe not needed. Could skip Qualifications if no specific content.
- Skills: maybe the "Nice To Have (preferred Skills)" list.
- Benefits: benefits list.
- Pay: salary range details.
- Schedule: maybe flextime scheduling mentioned under benefits? There's "Flextime Scheduling". Could be schedule. So we could have Schedule section with flextime.
We must not create sections with placeholder text like "not specified". So only include if we have real content.
Thus sections:
. Let's parse:
- Generous PTO and Leave Times
- Flextime Scheduling
- Bereavement Paid Time Off (PTO)
- Paid Parental Leave
- Financial Benefits
- 401K Retirement Plan Contribution
- Employee Stock Ownership Plan
- Continuing Education Funds
- Health, Medical, And Wellness Benefits
- Medical Insurance
- Dental & Vision Insurance
- Life Insurance and Long-Term Disability (LTD)
- Vision Reimbursement
We could flatten: list each distinct benefit.
Thus items:
- Generous PTO and Leave Times
- Flextime Scheduling
- Bereavement Paid Time Off (PTO)
- Paid Parental Leave
- 401K Retirement Plan Contribution
- Employee Stock Ownership Plan
- Continuing Education Funds
- Medical Insurance
- Dental & Vision Insurance
- Life Insurance and Long-Term Disability (LTD)
- Vision Reimbursement
We could also keep "Financial Benefits" as a heading but we only use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Intro: "At Areté, we are on the forefront of developing innovative solutions, with great minds from all backgrounds, to help solve the nation’s most complex security challenges. We strive for an inclusive, collaborative team environment that approaches differences as opportunities for innovation and excellence. As an employee-owned company, we foster an atmosphere that propels diverse career opportunities and professional growth. Discover your future with us. We are seeking a Software Engineer with web and/or desktop development experience to help create and maintain intuitive and interactive GUI applications with a focus on mission management, data analysis, and data visualization. The ideal candidate will combine strong design skills with technical expertise and have a multidisciplinary background in physics, mathematics, and software engineering. This role requires a passion for solving challenging technical problems in a collaborative environment. This position offers an exciting opportunity to shape user experiences while simultaneously satisfying a critical mission need."
That could be "About the role". Could also be "Responsibilities". But we have a separate "Experiences And Background We Look For (required Skills)" list. That's requirements/qualifications/skills.
We have "Nice To Have (preferred Skills)" list.
We have benefits list: "We have an impressive range of benefits, programs, and perks that we offer: Generous PTO and Leave Times Flextime Scheduling Bereavement Paid Time Off (PTO) Paid Parental Leave Financial Benefits 401K Retirement Plan Contribution Employee Stock Ownership Plan Continuing Education Funds Health, Medical, And Wellness Benefits Medical Insurance Dental & Vision Insurance Life Insurance and Long-Term Disability (LTD) Vision Reimbursement"
We have salary range: "The salary range for this role depends on the candidate’s level of experience: Engineer 1: $90,000 - $120,000 [required BS degree or higher] Engineer 2: $110,000 - $140,000 [minimum experience of BS+2 years, OR MS+0 years] Staff Engineer: $130,000 - $160,000 [minimum experience of BS+5 years, MS+3 years, or PhD+0 years] However, Arete considers several factors when extending an offer of employment, including but not limited to: the position and associated responsibilities, a candidate’s work experience, education/training, and key skills."
We have "Qualities We Look For Creativity Integrity Passion Responsiveness Collaboration" - could be part of Skills or Qualities.
We have other considerations (EEO etc) which we should remove.
We need sections: About the role (intro), Responsibilities? The posting doesn't explicitly list responsibilities beyond "help create and maintain intuitive and interactive GUI applications with a focus on mission management, data analysis, and data visualization." That could be responsibilities. We could put that under Responsibilities.
Requirements: required skills list.
Qualifications: maybe education? Not explicit. Could combine.
Skills: maybe both required and preferred? But we have separate sections for required and preferred. Could put required under Requirements, preferred under Skills? Or we could have Skills for both required and preferred? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections have content.
We have:
- About the role: intro paragraph.
- Responsibilities: maybe the sentence about creating/maintaining GUI applications, mission management, data analysis, data visualization.
- Requirements: required skills list (the "Experiences And Background We Look For (required Skills)").
- Qualifications: maybe education? Not explicit but could be implied: "BS degree or higher" etc in salary ranges. But we could also put qualifications as education requirements: maybe not needed. Could skip Qualifications if no specific content.
- Skills: maybe the "Nice To Have (preferred Skills)" list.
- Benefits: benefits list.
- Pay: salary range details.
- Schedule: maybe flextime scheduling mentioned under benefits? There's "Flextime Scheduling". Could be schedule. So we could have Schedule section with flextime.
We must not create sections with placeholder text like "not specified". So only include if we have real content.
Thus sections:
About the role
... intro ...
Responsibilities
Help create and maintain intuitive and interactive GUI applications with a focus on mission management, data analysis, and data visualization.
Requirements
- ... each required skill ...
Skills
- ... each preferred skill ...
Benefits
- ... each benefit ...
Pay
Salary range: Engineer 1: $90,000 - $120,000 [required BS degree or higher]; Engineer 2: $110,000 - $140,000 [minimum experience of BS+2 years, OR MS+0 years]; Staff Engineer: $130,000 - $160,000 [minimum experience of BS+5 years, MS+3 years, or PhD+0 years]. Arete considers several factors when extending an offer of employment, including but not limited to: the position and associated responsibilities, a candidate’s work experience, education/training, and key skills.
Schedule
Flextime scheduling is offered.
We need to ensure we preserve all substantive information. Let's extract required skills list exactly: "Experiences And Background We Look For (required Skills) Demonstrated exposure to college level physics, math, and software engineering Experience with front-end GUI development Strong programming skills in Python and PyQt Proficiency in modern JavaScript (ES6+), HTML, and CSS Experience designing prototypes with Figma or similar tools Knowledge of version control using Git Experience developing in Windows and Linux environments Excellent written and verbal communication skills – with an attention to detail Intellectual curiosity and a desire for continuous learning Ability to work with minimal supervision and collaborate with small teams in an Agile-like environment Willingness to work onsite in the office 100% Must be able to obtain and maintain a TS/SCI security clearance and program access" We need to keep each as list items. Preferred skills list: "Nice To Have (preferred Skills) Experience with issue tracking software Strong programming skills in C++ and Qt Web application configuration and deployment Experience with UI testing frameworks such as Squish and Selenium Experience working with relational databases Experience with API design Data analysis and visualization skills Experience with computer graphics using libraries such as OpenGL or WebGL Active Top-Secret Clearance" We need to keep each. Benefits list: The paragraph: "We have an impressive range of benefits, programs, and perks that we offer: Generous PTO and Leave Times Flextime Scheduling Bereavement Paid Time Off (PTO) Paid Parental Leave Financial Benefits 401K Retirement Plan Contribution Employee Stock Ownership Plan Continuing Education Funds Health, Medical, And Wellness Benefits Medical Insurance Dental & Vision Insurance Life Insurance and Long-Term Disability (LTD) Vision Reimbursement" We need to split into sensible items. Could list each benefit as separate- . So just list.
Schedule: Flextime Scheduling already listed under benefits; but schedule section could mention flextime. However we might duplicate. The instruction: avoid duplication? It says remove duplicated lines. If we put flextime both in Benefits and Schedule, that's duplication. Better to put flextime only under Schedule, and not list it under Benefits. But benefits list includes Flextime Scheduling as a benefit. We could keep it under Benefits and not have Schedule section, or we could keep Schedule and remove flextime from Benefits. Which is better? The instruction: Prefer a few substantive sections over many thin ones. We have Benefits already; we could drop Schedule section and keep flextime under Benefits. But we need to include Schedule only if posting has real specific content for it. The posting mentions Flextime Scheduling as a benefit; that's schedule info. Could be considered schedule. But we already have Benefits section; we could incorporate flextime there. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid overlapping content across sections, but we should avoid duplication. I'd choose to keep Benefits section with flextime included, and not create a separate Schedule section to avoid duplication. However the instruction says we can use Schedule heading if we have schedule info. But we already have flextime under Benefits; we could still have Schedule section with flextime, but that duplicates. Better to not duplicate.
Thus we will not include Schedule section.
Now Pay section: we have salary range details. We'll put that.
Now we need to ensure we don't include boilerplate like EEO etc. We'll omit.
Now produce HTML fragment.
Let's craft:
About the role
At Areté, we are on the forefront of developing innovative solutions, with great minds from all backgrounds, to help solve the nation’s most complex security challenges. We strive for an inclusive, collaborative team environment that approaches differences as opportunities for innovation and excellence. As an employee-owned company, we foster an atmosphere that propels diverse career opportunities and professional growth. Discover your future with us. We are seeking a Software Engineer with web and/or desktop development experience to help create and maintain intuitive and interactive GUI applications with a focus on mission management, data analysis, and data visualization. The ideal candidate will combine strong design skills with technical expertise and have a multidisciplinary background in physics, mathematics, and software engineering. This role requires a passion for solving challenging technical problems in a collaborative environment. This position offers an exciting opportunity to shape user experiences while simultaneously satisfying a critical mission need.
Responsibilities
Help create and maintain intuitive and interactive GUI applications with a focus on mission management, data analysis, and data visualization.
Requirements
- Demonstrated exposure to college level physics, math, and software engineering
- Experience with front-end GUI development
- Strong programming skills in Python and PyQt
- Proficiency in modern JavaScript (ES6+), HTML, and CSS
- Experience designing prototypes with Figma or similar tools