Sr. Full Stack Engineer
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions
- Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, let's map the content.
Job Summary: This is prose. Could be "About the role" or "Job Summary". The rule says use
for section headings like "About the role". I'll use "About the role" as heading.
Responsibilities: There's a list of bullet points. That's a list.
Qualifications: There's a list of bullet points. That's a list.
Skills: There's a long comma-separated list of skills. That's a list.
Metadata: location, job type, salary, work hours, education. These are specific details. The rule says fold minor metadata into a short
or drop. But salary, work hours, location are substantive. The posting states salary: $81-82 per hour, work hours: 8am to 5pm, location: Durham, NC, job type: Contract, education: Bachelors. These are specific. Should I create a "Pay" section? The rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary and work hours. So I could include a "Pay" section with salary, and "Schedule" with work hours. But the rule also says prefer few substantive sections over many thin ones. Could combine into a "Details" or "Job Details" section? However, the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Requirements" might be for education/experience. The posting has education: Bachelors, and in responsibilities it says "A Bachelor's degree or equivalent experience... with at least 8 years of development experience". That's a requirement. Could have a "Requirements" section. But the posting has a "Qualifications" section separate from "Responsibilities". The "Responsibilities" section includes a list that starts with "A Bachelor's degree...". That seems like requirements. Actually, the posting has "Responsibilities" heading then a list that includes both responsibilities and requirements. Then "Qualifications" heading with another list. Then "Skills" list.
I need to structure logically.
Let me parse the original text:
"Job Summary Provide technical help to the squads across the product area who are responsible for building, deploying, and maintaining applications in AWS. Effective execution of multiple development work streams while ensuring design and architecture is scalable, resilient, and extensible. Support by developing solutions that help improve developer efficiency and share knowledge about new techniques and technologies. Ensure technology decisions and implementation align with Client architecture standards and strategies. Evaluate and recommend technology and frameworks for flexibility, long-term viability, and time to market. Analyzes and recommends changes in project development policies, procedures, standards, and strategies to development experts and management Provides ongoing assessment for improvement to application design Determines boundary and relationship between technical architecture and application layer Creates new design concepts and processes that improve the quality of technical design development location: Durham, North Carolina job type: Contract salary: $81 - 82 per hour work hours: 8am to 5pm education: Bachelors"
Then "Responsibilities" heading, then a list of bullet points (but in the text it's not bulleted, but each line is a requirement). Actually the text after "Responsibilities" is a list of items separated by line breaks. They are:
- A Bachelor's degree or equivalent experience in computer science, computer engineering, information systems preferred, with at least 8 years of development experience
- Expertise in building scalable web and middle-tier applications using Java, Spring, spring Boot and event-based architecture
- Solid understanding and hands-on experience with API authentication, RBAC Authorization and SAML/OIDC
- Strong foundation of software design, data structures and algorithms.
- Strong experience with web services (JSON, XML, REST, SOAP, etc.)
- Experience building cloud enabled applications leveraging 12 factor design
- Experience with Docker containerization and AWS cloud deployment/application management
- Experience with unit testing and test automation libraries/strategies.
- Experience with CI/CD pipelines, Kubernetes, Terraform and Jenkins
- Experience in delivering software in the Agile environment
- Experience in coaching and mentoring junior engineers and performing code reviews
- Strong verbal and written communication skills, with the ability to understand and parse business logic into technical requirements, experienced in an agile scrum environment.
- Experience with brokerage and financial services application development is a plus
- Working knowledge of design system is a plus
- Knowledge of web security attack methods and measures to defend against them is a plus
Then "Qualifications" heading, then list:
- Champions innovative technology solutions to resolve sophisticated business problems
- Works across groups to find opportunities for organization-wide technology initiatives
- Brings external information, ideas, and expertise back to the team
- Good understanding of the software development process including analysis, design, coding, system and user testing, problem resolution and planning
- Identify creative ways to drive desired outcomes and promote culture of innovation by setting examples.
- Collaborate with peers through code reviews, pair programming or interactive discussions daily.
- You are comfortable working across multiple squads and adaptable to change.
- Embrace customer-first mentality and enjoy developing user-friendly internet facing web applications that solve real life problems.
- Have a passion for following outstanding software engineering practices and always looking to improve your engineering skills and industry knowledge.
- Bring a data-driven & collaborative approach to decision making, both in day-to-day work and in making strategic trade-offs.
Then "Skills" heading, then a comma-separated list of skills.
Then boilerplate: EEO, benefits, posting duration.
Now, I need to output HTML fragment with sections.
I'll create sections:
1. About the role (Job Summary prose)
2. Responsibilities (list from Responsibilities section)
3. Qualifications (list from Qualifications section)
4. Skills (list from Skills section)
5. Maybe a "Details" section for metadata? But the allowed headings include Pay, Schedule. Since salary and work hours are explicitly stated, I should include Pay and Schedule sections. Also location and job type could be in a "Details" but not a standard heading. The rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I can use Pay and Schedule. Also education could be under Requirements. But there is no "Requirements" heading in the example, but it's listed as an example. I could create a "Requirements" section for education and experience. However, the Responsibilities list already includes the degree and experience requirement. The Qualifications list includes more qualitative items. The posting has "Responsibilities" and "Qualifications" as headings. I'll keep those.
But the metadata: location, job type, salary, work hours, education. The education is also in responsibilities. I'll include a short paragraph for location and job type, maybe in About the role or separate. The rule says fold minor metadata into a short
or drop. But salary and work hours are specific and important. I'll create Pay and Schedule sections.
Benefits: The posting mentions benefits package: medical, prescription, dental, vision, AD&D, life insurance, short-term disability, 401K plan. That's specific. So I should include a Benefits section.
But the rule says never create Benefits section unless posting actually states them. It does state them. So include.
However, the boilerplate includes "Equal Opportunity Employer..." and "Pay offered to a successful candidate will be based on several factors..." and "In addition, Randstad Digital offers a comprehensive benefits package...". That is part of the posting. But the rule says remove EEO/equal-opportunity boilerplate. The EEO statement is boilerplate. The benefits description is specific to the company. The posting says "Randstad Digital offers a comprehensive benefits package, including: medical, prescription, dental, vision, AD&D, and life insurance offerings, short-term disability, and a 401K plan (all benefits are based on eligibility)." That's specific. I'll include Benefits section.
But also the posting says "This posting is open for thirty (30) days." That's application instruction/boilerplate, remove.
Now, the Skills list is a long comma-separated string. I'll split into list items.
Now, I need to ensure no filler. All sections have real content.
Let's structure:
About the role
Provide technical help to the squads across the product area who are responsible for building, deploying, and maintaining applications in AWS. Effective execution of multiple development work streams while ensuring design and architecture is scalable, resilient, and extensible. Support by developing solutions that help improve developer efficiency and share knowledge about new techniques and technologies. Ensure technology decisions and implementation align with Client architecture standards and strategies. Evaluate and recommend technology and frameworks for flexibility, long-term viability, and time to market. Analyzes and recommends changes in project development policies, procedures, standards, and strategies to development experts and management. Provides ongoing assessment for improvement to application design. Determines boundary and relationship between technical architecture and application layer. Creates new design concepts and processes that improve the quality of technical design development.
Maybe include location and job type in a paragraph: Location: Durham, North Carolina. Job type: Contract.
But the rule says fold minor metadata into a short . I'll add a paragraph after the summary.
Responsibilities
- ...
Qualifications
- ...
Skills
- ...
Pay
$81 - $82 per hour
Schedule
8am to 5pm
Benefits
- Medical, prescription, dental, vision, AD&D, and life insurance offerings
- Short-term disability
- 401K plan (based on eligibility)
But the benefits are listed in a sentence. I'll parse.
Also education: Bachelors. Could be in Requirements. But the Responsibilities list already includes "A Bachelor's degree or equivalent experience...". So maybe not needed separately.
The posting also says "education: Bachelors" in metadata. I'll include in a "Requirements" section? But the rule says use headings like Requirements. I could add a "Requirements" section with education and experience. However, the Responsibilities list already includes that. To avoid duplication, I'll keep as is.
Now, the Skills
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content. Job Summary: This is prose. Could be "About the role" or "Job Summary". The rule says use
for section headings like "About the role". I'll use "About the role" as heading. Responsibilities: There's a list of bullet points. That's a list. Qualifications: There's a list of bullet points. That's a list. Skills: There's a long comma-separated list of skills. That's a list. Metadata: location, job type, salary, work hours, education. These are specific details. The rule says fold minor metadata into a short
or drop. But salary, work hours, location are substantive. The posting states salary: $81-82 per hour, work hours: 8am to 5pm, location: Durham, NC, job type: Contract, education: Bachelors. These are specific. Should I create a "Pay" section? The rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary and work hours. So I could include a "Pay" section with salary, and "Schedule" with work hours. But the rule also says prefer few substantive sections over many thin ones. Could combine into a "Details" or "Job Details" section? However, the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Requirements" might be for education/experience. The posting has education: Bachelors, and in responsibilities it says "A Bachelor's degree or equivalent experience... with at least 8 years of development experience". That's a requirement. Could have a "Requirements" section. But the posting has a "Qualifications" section separate from "Responsibilities". The "Responsibilities" section includes a list that starts with "A Bachelor's degree...". That seems like requirements. Actually, the posting has "Responsibilities" heading then a list that includes both responsibilities and requirements. Then "Qualifications" heading with another list. Then "Skills" list. I need to structure logically. Let me parse the original text: "Job Summary Provide technical help to the squads across the product area who are responsible for building, deploying, and maintaining applications in AWS. Effective execution of multiple development work streams while ensuring design and architecture is scalable, resilient, and extensible. Support by developing solutions that help improve developer efficiency and share knowledge about new techniques and technologies. Ensure technology decisions and implementation align with Client architecture standards and strategies. Evaluate and recommend technology and frameworks for flexibility, long-term viability, and time to market. Analyzes and recommends changes in project development policies, procedures, standards, and strategies to development experts and management Provides ongoing assessment for improvement to application design Determines boundary and relationship between technical architecture and application layer Creates new design concepts and processes that improve the quality of technical design development location: Durham, North Carolina job type: Contract salary: $81 - 82 per hour work hours: 8am to 5pm education: Bachelors" Then "Responsibilities" heading, then a list of bullet points (but in the text it's not bulleted, but each line is a requirement). Actually the text after "Responsibilities" is a list of items separated by line breaks. They are: - A Bachelor's degree or equivalent experience in computer science, computer engineering, information systems preferred, with at least 8 years of development experience - Expertise in building scalable web and middle-tier applications using Java, Spring, spring Boot and event-based architecture - Solid understanding and hands-on experience with API authentication, RBAC Authorization and SAML/OIDC - Strong foundation of software design, data structures and algorithms. - Strong experience with web services (JSON, XML, REST, SOAP, etc.) - Experience building cloud enabled applications leveraging 12 factor design - Experience with Docker containerization and AWS cloud deployment/application management - Experience with unit testing and test automation libraries/strategies. - Experience with CI/CD pipelines, Kubernetes, Terraform and Jenkins - Experience in delivering software in the Agile environment - Experience in coaching and mentoring junior engineers and performing code reviews - Strong verbal and written communication skills, with the ability to understand and parse business logic into technical requirements, experienced in an agile scrum environment. - Experience with brokerage and financial services application development is a plus - Working knowledge of design system is a plus - Knowledge of web security attack methods and measures to defend against them is a plus Then "Qualifications" heading, then list: - Champions innovative technology solutions to resolve sophisticated business problems - Works across groups to find opportunities for organization-wide technology initiatives - Brings external information, ideas, and expertise back to the team - Good understanding of the software development process including analysis, design, coding, system and user testing, problem resolution and planning - Identify creative ways to drive desired outcomes and promote culture of innovation by setting examples. - Collaborate with peers through code reviews, pair programming or interactive discussions daily. - You are comfortable working across multiple squads and adaptable to change. - Embrace customer-first mentality and enjoy developing user-friendly internet facing web applications that solve real life problems. - Have a passion for following outstanding software engineering practices and always looking to improve your engineering skills and industry knowledge. - Bring a data-driven & collaborative approach to decision making, both in day-to-day work and in making strategic trade-offs. Then "Skills" heading, then a comma-separated list of skills. Then boilerplate: EEO, benefits, posting duration. Now, I need to output HTML fragment with sections. I'll create sections: 1. About the role (Job Summary prose) 2. Responsibilities (list from Responsibilities section) 3. Qualifications (list from Qualifications section) 4. Skills (list from Skills section) 5. Maybe a "Details" section for metadata? But the allowed headings include Pay, Schedule. Since salary and work hours are explicitly stated, I should include Pay and Schedule sections. Also location and job type could be in a "Details" but not a standard heading. The rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I can use Pay and Schedule. Also education could be under Requirements. But there is no "Requirements" heading in the example, but it's listed as an example. I could create a "Requirements" section for education and experience. However, the Responsibilities list already includes the degree and experience requirement. The Qualifications list includes more qualitative items. The posting has "Responsibilities" and "Qualifications" as headings. I'll keep those. But the metadata: location, job type, salary, work hours, education. The education is also in responsibilities. I'll include a short paragraph for location and job type, maybe in About the role or separate. The rule says fold minor metadata into a short
or drop. But salary and work hours are specific and important. I'll create Pay and Schedule sections. Benefits: The posting mentions benefits package: medical, prescription, dental, vision, AD&D, life insurance, short-term disability, 401K plan. That's specific. So I should include a Benefits section. But the rule says never create Benefits section unless posting actually states them. It does state them. So include. However, the boilerplate includes "Equal Opportunity Employer..." and "Pay offered to a successful candidate will be based on several factors..." and "In addition, Randstad Digital offers a comprehensive benefits package...". That is part of the posting. But the rule says remove EEO/equal-opportunity boilerplate. The EEO statement is boilerplate. The benefits description is specific to the company. The posting says "Randstad Digital offers a comprehensive benefits package, including: medical, prescription, dental, vision, AD&D, and life insurance offerings, short-term disability, and a 401K plan (all benefits are based on eligibility)." That's specific. I'll include Benefits section. But also the posting says "This posting is open for thirty (30) days." That's application instruction/boilerplate, remove. Now, the Skills list is a long comma-separated string. I'll split into list items. Now, I need to ensure no filler. All sections have real content. Let's structure:
About the role
Provide technical help to the squads across the product area who are responsible for building, deploying, and maintaining applications in AWS. Effective execution of multiple development work streams while ensuring design and architecture is scalable, resilient, and extensible. Support by developing solutions that help improve developer efficiency and share knowledge about new techniques and technologies. Ensure technology decisions and implementation align with Client architecture standards and strategies. Evaluate and recommend technology and frameworks for flexibility, long-term viability, and time to market. Analyzes and recommends changes in project development policies, procedures, standards, and strategies to development experts and management. Provides ongoing assessment for improvement to application design. Determines boundary and relationship between technical architecture and application layer. Creates new design concepts and processes that improve the quality of technical design development.
Maybe include location and job type in a paragraph:Location: Durham, North Carolina. Job type: Contract.
But the rule says fold minor metadata into a short. I'll add a paragraph after the summary.
Responsibilities
- ...
Qualifications
- ...
Skills
- ...
Pay
$81 - $82 per hour
Schedule
8am to 5pm
Benefits
- Medical, prescription, dental, vision, AD&D, and life insurance offerings
- Short-term disability
- 401K plan (based on eligibility)