Full Stack Developer
EngRadar · Chantilly, VA · 1 mo ago
$130k–$265k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need to include headings for sections that have real content: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, EEO, etc. Must not create sections with filler.
We need to parse the posting: It includes description: "As a Full Stack Developer, you will be responsible for designing, developing, troubleshooting, and analyzing complex software solutions. Your role will involve reviewing system architecture and making critical decisions on the selection and integration of development and support tools to ensure optimal product performance. You will also engage in system modeling, simulation, and analysis to anticipate and resolve potential issues before they impact the end user. This position is hybrid, requiring your presence onsite three days each week to collaborate closely with team members and stakeholders. You will mentor junior developers, and use your judgement and expertise to make technical decisions for the team. You will often be client-facing and speak on behalf of the team to the client on technical matters."
That's responsibilities.
Then "To excel in this role, you should have hands-on experience with DevOps practices and be proficient in the AWS Suite, Java, Groovy, DynamoDB, and Lambda. Familiarity with system performance tuning, cloud-native architectures, and automation tools will further enhance your ability to lead technical initiatives and drive innovation within the team."
That's skills/requirements.
Then "Here's What You'll Need" with bullet list: Master's degree in a tech field plus 10 years of relevant experience; or Bachelor's degree in a tech field plus 13 years of relevant experience; or 18 years of relevant experience without a degree. 8+ years of experience in Full Stack Development or a related field. Experience in at least one of the following areas: DevOps, AWS Suite and AWS Lambda, Software engineering, Agile leadership, Groovy, and/or DynamoDB, Node.js, Typescript, Go, Python, and/or React, Leading software developers, but have hands-on keyboard experience as well, Experienced with client-interaction, presenting information, and understanding the requirements.
Then "Bonus Points If You Have" list: Master's degree, Exposure to video application development, CrafterCMS is highly desirable, Experience with video applications.
Then "Security Clearance Active TS/SCI with Poly security clearance is required."
Then compensation: "As required by local law, Accenture Federal Services provides reasonable ranges of compensation for hired roles based on labor costs in the states of California, Colorado, Hawaii, Illinois, Maine, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont, Virginia, Washington, and the District of Columbia, and the city of Cleveland. The base pay range for this position in these locations is shown below. Compensation for roles at Accenture Federal Services varies depending on a wide array of factors, including but not limited to office location, role, skill set, and level of experience. Accenture Federal Services offers a wide variety of benefits. You can find more information on benefits here. We accept applications on an on-going basis and there is no fixed deadline to apply. The Pay Range For The States Of California, Colorado, Hawaii, Illinois, Maine, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont, Virginia, Washington, And The District Of Columbia, And The City Of Cleveland Is $130,200—$265,300 USD"
Thus we have Pay section with range.
Benefits: mention "offers a wide variety of benefits" but no specifics. According to rule: do NOT create Benefits section unless posting actually states them. It says "offers a wide variety of benefits" but no specifics. That's vague; maybe we should not create Benefits section because no specific benefits listed. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states they offer benefits but not specifics. Likely we should not create Benefits section because no concrete benefits. However we could include a short paragraph about benefits? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state they offer benefits, but not list them. Might be considered stating them generically. Safer to omit Benefits section.
Schedule: "This position is hybrid, requiring your presence onsite three days each week to collaborate closely with team members and stakeholders." That's schedule info. So we can create Schedule section.
About the role: maybe we can have an introductory paragraph about the role (the first paragraph about mission). The posting includes: "At Accenture Federal Services, nothing matters more than helping the US federal government make the nation stronger and safer and life better for people. Our 13,000+ people are united in a shared purpose to pursue the limitless potential of technology and ingenuity for clients across defense, national security, public safety, civilian, and military health organizations. Join Accenture Federal Services, a technology company within global Accenture. Recognized as a Glassdoor Top 100 Best Place to Work, we offer a collaborative and caring community where you feel like you belong and are empowered to grow, learn and thrive through hands-on experience, certifications, industry training and more. Join us to drive positive, lasting change that moves missions and the government forward!" That's about the company and role. Could be About the role section.
We need to avoid duplication. We'll produce sections: About the role (p), Responsibilities (ul), Requirements (maybe combine qualifications and skills?), but we have separate headings: Requirements, Qualifications, Skills. We need to decide which to use based on content. The posting has "Here's What You'll Need" (requirements/qualifications). Also "To excel in this role, you should have..." (skills). Also "Bonus Points If You Have" (preferred qualifications). Could map: Requirements = mandatory qualifications (education/experience). Qualifications = maybe same? But we can combine. However we must not create thin sections. Better to have a few substantive sections: About the role, Responsibilities, Requirements (including education/experience and mandatory skills), Preferred Qualifications (bonus points), Schedule, Pay.
But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require using all; we can choose those that have real content. So we can use About the role, Responsibilities, Requirements, Skills, Schedule, Pay. Possibly also Qualifications if we separate education vs skills. But we can combine.
Let's decide:
- About the role: company mission paragraph.
- Responsibilities: bullet list of duties.
- Requirements: education/experience mandatory (Master's/Bachelor's/years, 8+ years Full Stack, experience in at least one of the listed areas). Could be a ul.
- Skills: technical skills list (DevOps, AWS Suite, Java, Groovy, DynamoDB, Lambda, system performance tuning, cloud-native, automation tools). Could be ul.
- Schedule: hybrid, onsite three days.
- Pay: range.
We should also include Security Clearance requirement. Where to put? Could be under Requirements or Skills? It's a requirement. Could add a bullet under Requirements: Active TS/SCI with Poly security clearance required.
Also Bonus Points: could be under Preferred Qualifications (maybe a separate section). But we have no heading for Preferred Qualifications; we could use Qualifications for bonus points? Or we could add a section "Preferred Qualifications". The instruction list includes Qualifications as a possible heading. So we can use Qualifications for bonus points. That seems appropriate.
Thus sections:
About the role (p)
Responsibilities (ul)
Requirements (ul) (mandatory)
Qualifications (ul) (bonus points)
Skills (ul) (technical skills)
Schedule (p)
Pay (p)
We must not include Benefits.
Now we need to ensure we preserve all substantive information. Let's extract details.
About the role paragraph: combine the mission statements: "At Accenture Federal Services, nothing matters more than helping the US federal government make the nation stronger and safer and life better for people. Our 13,000+ people are united in a shared purpose to pursue the limitless potential of technology and ingenuity for clients across defense, national security, public safety, civilian, and military health organizations. Join Accenture Federal Services, a technology company within global Accenture. Recognized as a Glassdoor Top 100 Best Place to Work, we offer a collaborative and caring community where you feel like you belong and are empowered to grow, learn and thrive through hands-on experience, certifications, industry training and more. Join us to drive positive, lasting change that moves missions and the government forward!"
That's fine.
Responsibilities bullet list:
- Designing, developing, troubleshooting, and analyzing complex software solutions.
- Reviewing system architecture and making critical decisions on the selection and integration of development and support tools to ensure optimal product performance.
- Engaging in system modeling, simulation, and analysis to anticipate and resolve potential issues before they impact the end user.
- Mentoring junior developers and using judgement and expertise to make technical decisions for the team.
- Being client-facing and speaking on behalf of the team to the client on technical matters.
- (Hybrid schedule mention? Actually schedule is separate; but the hybrid requirement is part of responsibilities? It's about presence onsite three days each week. Could be under Schedule.)
We'll keep schedule separate.
Requirements (mandatory):
- Master's degree in a tech field plus 10 years of relevant experience; OR Bachelor's degree in a tech field plus 13 years of relevant experience; OR 18 years of relevant experience without a degree.
- 8+ years of experience in Full Stack Development or a related field.
- Experience in at least one of the following areas: DevOps, AWS Suite and AWS Lambda, Software engineering, Agile leadership, Groovy and/or DynamoDB, Node.js, Typescript, Go, Python, and/or React, Leading software developers (with hands-on keyboard experience), Experienced with client-interaction, presenting information, and understanding requirements.
- Active TS/SCI with Poly security clearance required.
We could break into bullets.
Skills (technical):
- DevOps practices
- AWS Suite (including AWS Lambda)
- Java
- Groovy
- DynamoDB
- Lambda (already covered)
- System performance tuning
- Cloud-native architectures
- Automation tools
We could also include maybe other mentioned: but that's fine.
Schedule:
- This position is hybrid, requiring onsite presence three days each week to collaborate closely with team members and stakeholders.
Pay:
- Base pay range for this position in the listed locations (CA, CO, HI, IL, ME, MD, MA, MN, NJ, NY, VT, VA, WA, DC, Cleveland): $130,200—$265,300 USD.
We might also note that compensation varies based on location, role, skill set, experience.
Now produce HTML fragment.
We must not include markdown fences. Just raw HTML.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- Master's degree
- Exposure to video application development
- CrafterCMS is highly desirable
- Experience with video applications
Skills
- DevOps practices
- AWS Suite and AWS Lambda
- Java
- Gro