Staff Software Engineer 1
ARA · Baton Rouge, LA · 1 mo ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate. We need to preserve all substantive info.
Let's parse the posting:
- Because of our work with the defense community, applicants must be U.S. citizens.*** (citizenship requirement)
- ARA is seeking a Staff Software Engineer to be part of our team in Baton Rouge, Louisiana.
- We are a 100% employee-owned scientific research and engineering company dedicated to solving critical national problems to improve our safety, security, and way of life.
- You will work with other developers and engineers to design and develop products for a diverse range of clients.
- As a member of our development team, you will work in an agile environment focused on delivering high-quality software to our clients.
- What You Will Do: You will be a key member of ARA supporting multiple teams developing enterprise technologies to aid real-world operations for the Navy and military communities. As a valued member of our team your responsibilities will include:
- Designing, developing, and debugging applications in C#, Java, or JavaScript
- Frontend frameworks such as React, Angular, or Vue
- Performing code analysis and review
- Designing and implementing graphical user interfaces
- Unit testing
- Documenting software functionality
- Software support after release
- Staff Software Developer Required Technologies And Skills
- BA/BS in Computer Science or a related field
- 2+ years of professional software development experience
- Strong troubleshooting and debugging skills
- Experience with agile development methods
- Experience with C# or Java
- Experience developing Microsoft .NET applications
- Experience with JavaScript
- Strong oral and written communication skills
- Ability to work effectively in small team settings
- Licenses & Certifications: US citizen with the ability to obtain DoD Secret clearance
- Preferred Qualifications:
- Familiarity with relational databases and SQL
- Experience with a frontend framework (React, Angular, or Vue)
- Solid understanding of responsive web design
- Experience with AWS services
- High level of self-initiative and self-motivation with the ability to work under minimal supervision
- Benefits Include:
- 401K Matching
- Employee Stock Ownership Plan (ESOP)
- Health, Dental, and Vision Insurance
- Paid holidays and Paid Time Off
- About Us: description of ARA (company overview). This could be "About the role"? Actually "About Us" is company description. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- About the role: maybe the introductory paragraph describing role, location, company mission, agile environment, etc. Could be "About the role". We'll include that.
- Responsibilities: list of duties (designing, developing, debugging, etc.)
- Requirements: maybe the required technologies and skills (BA/BS, 2+ years, etc.) plus citizenship and clearance? Could be separate "Requirements" and "Qualifications". Usually "Requirements" are mandatory, "Qualifications" are preferred. We'll separate.
- Skills: maybe list of technical skills (C#, Java, JavaScript, .NET, agile, etc.) but we already have them in requirements. Could combine. But we need to avoid thin sections. Perhaps we can have "Requirements" covering education, experience, citizenship, clearance, technical skills. Then "Preferred Qualifications" covering preferred items. Then "Benefits". Pay and Schedule not mentioned, so omit.
We also have "About Us" company description; could be placed under "About the role" or maybe a separate "About the company" but not in allowed headings. Since only allowed headings are those list, we could put company description under "About the role" as part of role description. Or we could omit if not fitting. But we must preserve ALL substantive information; we cannot drop company description. So we need to include it somewhere. The allowed headings include "About the role". We can include company description there as part of role context.
Thus:
About the role
ARA is seeking a Staff Software Engineer to be part of our team in Baton Rouge, Louisiana. We are a 100% employee-owned scientific research and engineering company dedicated to solving critical national problems to improve our safety, security, and way of life. You will work with other developers and engineers to design and develop products for a diverse range of clients. As a member of our development team, you will work in an agile environment focused on delivering high-quality software to our clients. You will be a key member of ARA supporting multiple teams developing enterprise technologies to aid real-world operations for the Navy and military communities.
Then responsibilities list. Then Requirements (mandatory): BA/BS in Computer Science or related field, 2+ years professional software development experience, strong troubleshooting and debugging skills, experience with agile development methods, experience with C# or Java, experience developing Microsoft .NET applications, experience with JavaScript, strong oral and written communication skills, ability to work effectively in small team settings, US citizen with ability to obtain DoD Secret clearance. Then Preferred Qualifications: familiarity with relational databases and SQL, experience with a frontend framework (React, Angular, or Vue), solid understanding of responsive web design, experience with AWS services, high level of self-initiative and self-motivation with ability to work under minimal supervision. Then Benefits: 401K Matching, Employee Stock Ownership Plan (ESOP), Health, Dental, and Vision Insurance, Paid holidays and Paid Time Off. We might also include "Skills" section but we already covered technical skills in Requirements. Could create a Skills section listing languages/frameworks: C#, Java, JavaScript, .NET, React/Angular/Vue, etc. But that would be duplicate. Better to keep Requirements and Preferred Qualifications. We must not include Pay or Schedule sections as not specified. We must not include filler like "commensurate with experience". Not present. We need to output only HTML fragment. Let's craft. Be careful to not include any extra text outside HTML. We'll produce:About the role
...
Responsibilities
- Designing, developing, and debugging applications in C#, Java, or JavaScript
- Working with frontend frameworks such as React, Angular, or Vue
- Performing code analysis and review
- Designing and implementing graphical user interfaces
- Unit testing
- Documenting software functionality
- Providing software support after release
Requirements
- BA/BS in Computer Science or a related field
- 2+ years of professional software development experience
- Strong troubleshooting and debugging skills
- Experience with agile development methods
- Experience with C# or Java
- Experience developing Microsoft .NET applications
- Experience with JavaScript
- Strong oral and written communication skills
- Ability to work effectively in small team settings
- U.S. citizenship with the ability to obtain a DoD Secret clearance
Preferred Qualifications
- Familiarity with relational databases and SQL
- Experience with a frontend framework (React, Angular, or Vue)
- Solid understanding of responsive web design
- Experience with AWS services
- High level of self-initiative and self-motivation with the ability to work under minimal supervision
Benefits
- 401K Matching
- Employee Stock Ownership Plan (ESOP)
- Health, Dental, and Vision Insurance
- Paid holidays and Paid Time Off