Front End Web Applications Developer (Mid-Level) (5662)
- for any list of duties/requirements/benefits. The duties are not explicitly bullet list but we can treat each sentence as a list item? The instruction: "Use
- for any list of duties/requirements/benefits". The posting has a paragraph describing duties; not a list. Could we still make a list? Might be considered a list of duties. Safer to keep as
for prose. But we could split into
- each duty. However the instruction says "any list of duties/requirements/benefits". If it's not already a list, we could still make a list? Might be okay. But to be safe, we can keep as
for the duties paragraph. Then "Required Skills & Experience:" with bullet-like sentences. Could treat as list. Then "Desired Skills & Experience:" with bullet-like sentences. Then benefits: "Some key components of our robust benefits include health insurance, paid leave, and retirement." That's a benefits statement. Could make a
- list.
Pay: "The proposed salary for this position is:: $96,400 USD - $160,600 USD". So we need a Pay section with that info.
Schedule: Not mentioned. So we should not include Schedule.
We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We have About the role (intro). Responsibilities (Essential Duties & Responsibilities). Requirements? Could be Required Skills & Experience. Qualifications? Could be Desired Skills & Experience? Actually Qualifications often includes required and desired. But we have both Required and Desired. Could combine into Skills? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use.
We have content: About the role (intro). Responsibilities (duties). Required Skills & Experience (requirements). Desired Skills & Experience (desired qualifications). Benefits (benefits). Pay (salary). No schedule.
We could map: About the role -> intro. Responsibilities -> duties. Requirements -> Required Skills & Experience. Qualifications -> Desired Skills & Experience (or maybe combine). Skills -> maybe not needed if we used Requirements and Qualifications. But we could also have Skills section for technical skills? Might be redundant.
Better to follow typical structure: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Avoid Skills if not needed.
We must not repeat job title as heading. Good.
We must not include Job ID etc.
We must remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, cookie/navigation/legal. At end there is EEO statement, background investigation, etc. Remove those.
We must preserve all substantive information.
Let's extract substantive paragraphs:
Intro: "SMX is currently looking for a highly motivated Software Engineer - Front End Web Applications to contribute to the design, build, support, and implementation of the Budget and Spend (BAS) solution. This is an exciting role where you will work with some of the most interesting and powerful agencies in the world. This role is remote supporting a Washington, DC based customer and requires a Public Trust clearance."
Duties paragraph: "SAC is an all-in-one cloud product offered as software as a service (SaaS) for business intelligence (BI), planning, and predictive analytics. Using SAC Analytics Designer as a platform the team at SMX develops interactive web applications ranging from widgets & dashboards to sophisticated planning and analytic applications. This position will work with the team to develop new features as well as enhance existing features of the BAS web application built using SAC Analytics Designer. Build enterprise planning and reporting applications using SAP Analytics Cloud (SAC) or other web technologies such as JavaScript Review application requirements and interface designs Develop and implement highly interactive UI/UX components Monitor and improve front-end performance. Document application changes and developing updates Provide feedback on the technical feasibility of UI/UX designs Optimize web applications for scalability and speed Participate in code reviews and communicate effectively with team members."
Note there are some missing punctuation; but we keep as is.
Required Skills & Experience: list items:
- Bachelor’s degree in computer science or related field (Software Engineering, Web Development) or equivalent job experience
- 5+ years of software engineering experience working across front-end web technologies (JavaScript, HTML5, CSS, etc.)
- Advanced understanding of JavaScript and all its intricacies
- Knowledge of REST APIs, experience creating and consuming APIs, as well as ability to work with different data formats such as XML and JSON.
- Experience in Object Oriented Programming/Design, Web Development and debugging
- Proven ability to work independently as well as collaboratively
- Strong programming skills
- Excellent verbal and written communication skills
- Public Trust U.S. citizenship required to maintain federal clearance
Desired Skills & Experience:
- SAP Analytics Cloud Experience
- Experience with Federal, State, Local, or Higher Education organizations
- Firm understanding of standard SDLC, lean, and agile practices
- Familiarity with Business Objects (BOBJ)
Benefits: "Some key components of our robust benefits include health insurance, paid leave, and retirement."
Pay: "The proposed salary for this position is:: $96,400 USD - $160,600 USD"
We also have some other sentences about SMX values etc. Those are boilerplate? "At SMX®, we are a team of technical and domain experts dedicated to enabling your mission..." That's marketing fluff but maybe substantive? It's not required to include? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. That paragraph is about SMX's mission etc. Could be considered substantive but maybe it's boilerplate? It's not EEO/legal. It's describing company. Might be considered part of About the role? Could include as part of About the role? But we already have intro. Could add another paragraph under About the role describing SMX's mission. However the instruction says "Prefer a few substantive sections over many thin ones." Might be okay to include as part of About the role.
But we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The paragraph about SMX's mission is not boilerplate; it's descriptive. Keep it.
Also there is line: "Selected applicant may be subject to a background investigation and/or education verification." That's somewhat boilerplate but maybe considered part of hiring process; could be considered application instructions? It's not exactly instruction to apply. Might be considered boilerplate? It's about selection process. Might be okay to keep? The instruction says remove application instructions. This is not an instruction to apply but a condition. Might be considered part of requirements? Could be included under Requirements? But it's not a skill. Might be considered a condition. Safer to drop it as it's not substantive about the job.
Also line: "SMX does not sponsor a new applicant for employment authorization or immigration related support for this position (i.e. H1B, F-1 OPT, ...)." That's also a condition; could be considered part of Requirements (citizenship). Already have Public Trust U.S. citizenship required. This line is about not sponsoring visa. Could be considered part of Requirements. Might keep as a note under Requirements.
But we already have Public Trust U.S. citizenship required. The visa sponsorship line is extra. Could include as a separate bullet under Requirements.
We need to decide.
Given the instruction to preserve ALL substantive information, we should keep that line as it's substantive about eligibility. So include under Requirements.
Now we need to format.
We'll produce:
About the role
SMX is currently looking for a highly motivated Software Engineer - Front End Web Applications to contribute to the design, build, support, and implementation of the Budget and Spend (BAS) solution. This is an exciting role where you will work with some of the most interesting and powerful agencies in the world. This role is remote supporting a Washington, DC based customer and requires a Public Trust clearance.
At SMX®, we are a team of technical and domain experts dedicated to enabling your mission. From priority national security initiatives for the DoD to highly assured and compliant solutions for healthcare, we understand that digital transformation is key to your future success. We share your vision for the future and strive to accelerate your impact on the world. We bring both cutting edge technology and an expansive view of what’s possible to every engagement. Our delivery model and unique approaches harness our deep technical and domain knowledge, providing forward-looking insights and practical solutions to power secure mission acceleration.
Then Responsibilities:Responsibilities
SAC is an all-in-one cloud product offered as software as a service (SaaS) for business intelligence (BI), planning, and predictive analytics. Using SAC Analytics Designer as a platform the team at SMX develops interactive web applications ranging from widgets & dashboards to sophisticated planning and analytic applications. This position will work with the team to develop new features as well as enhance existing features of the BAS web application built using SAC Analytics Designer. Build enterprise planning and reporting applications using SAP Analytics Cloud (SAC) or other web technologies such as JavaScript Review application requirements and interface designs Develop and implement highly interactive UI/UX components Monitor and improve front-end performance. Document application changes and developing updates Provide feedback on the technical feasibility of UI/UX designs Optimize web applications for scalability and speed Participate in code reviews and communicate effectively with team members.
But we could split into list for readability. However the instruction says use- for any list of duties/requirements/benefits. The duties are not a list but we could still make a list; but maybe better to keep as
. However the duties paragraph is long and missing punctuation; but we keep as is. Now Requirements:
Requirements
- Bachelor’s degree in computer science or related field (Software Engineering, Web Development) or equivalent job experience
- 5+ years of software engineering experience working across front-end web technologies (JavaScript, HTML5, CSS, etc.)
- Advanced understanding of JavaScript and all its intricacies
- Knowledge of REST APIs, experience creating and consuming APIs, as well as ability to work with different data formats such as XML and JSON.
- Experience in Object Oriented Programming/Design, Web Development and debugging
- Proven ability to work independently as well as collaboratively
- Strong programming skills
- Excellent verbal and written communication skills
- Public Trust U.S. citizenship required to maintain federal clearance
- SMX does not sponsor a new applicant for employment authorization or immigration related support for this position (i.e. H1B, F-1 OPT, F-1 STEM OPT, F-1 CPT, J-1, TN, E-2, E-3, L-1 and O-1, or any EADs or other forms of work authorization that require immigration support from an employer)
Qualifications
- SAP Analytics Cloud Experience
- Experience with Federal, State, Local, or Higher Education
- for any list of duties/requirements/benefits. The duties are not a list but we could still make a list; but maybe better to keep as
- list.
Pay: "The proposed salary for this position is:: $96,400 USD - $160,600 USD". So we need a Pay section with that info.
Schedule: Not mentioned. So we should not include Schedule.
We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We have About the role (intro). Responsibilities (Essential Duties & Responsibilities). Requirements? Could be Required Skills & Experience. Qualifications? Could be Desired Skills & Experience? Actually Qualifications often includes required and desired. But we have both Required and Desired. Could combine into Skills? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use.
We have content: About the role (intro). Responsibilities (duties). Required Skills & Experience (requirements). Desired Skills & Experience (desired qualifications). Benefits (benefits). Pay (salary). No schedule.
We could map: About the role -> intro. Responsibilities -> duties. Requirements -> Required Skills & Experience. Qualifications -> Desired Skills & Experience (or maybe combine). Skills -> maybe not needed if we used Requirements and Qualifications. But we could also have Skills section for technical skills? Might be redundant.
Better to follow typical structure: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Avoid Skills if not needed.
We must not repeat job title as heading. Good.
We must not include Job ID etc.
We must remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, cookie/navigation/legal. At end there is EEO statement, background investigation, etc. Remove those.
We must preserve all substantive information.
Let's extract substantive paragraphs:
Intro: "SMX is currently looking for a highly motivated Software Engineer - Front End Web Applications to contribute to the design, build, support, and implementation of the Budget and Spend (BAS) solution. This is an exciting role where you will work with some of the most interesting and powerful agencies in the world. This role is remote supporting a Washington, DC based customer and requires a Public Trust clearance."
Duties paragraph: "SAC is an all-in-one cloud product offered as software as a service (SaaS) for business intelligence (BI), planning, and predictive analytics. Using SAC Analytics Designer as a platform the team at SMX develops interactive web applications ranging from widgets & dashboards to sophisticated planning and analytic applications. This position will work with the team to develop new features as well as enhance existing features of the BAS web application built using SAC Analytics Designer. Build enterprise planning and reporting applications using SAP Analytics Cloud (SAC) or other web technologies such as JavaScript Review application requirements and interface designs Develop and implement highly interactive UI/UX components Monitor and improve front-end performance. Document application changes and developing updates Provide feedback on the technical feasibility of UI/UX designs Optimize web applications for scalability and speed Participate in code reviews and communicate effectively with team members."
Note there are some missing punctuation; but we keep as is.
Required Skills & Experience: list items:
- Bachelor’s degree in computer science or related field (Software Engineering, Web Development) or equivalent job experience
- 5+ years of software engineering experience working across front-end web technologies (JavaScript, HTML5, CSS, etc.)
- Advanced understanding of JavaScript and all its intricacies
- Knowledge of REST APIs, experience creating and consuming APIs, as well as ability to work with different data formats such as XML and JSON.
- Experience in Object Oriented Programming/Design, Web Development and debugging
- Proven ability to work independently as well as collaboratively
- Strong programming skills
- Excellent verbal and written communication skills
- Public Trust U.S. citizenship required to maintain federal clearance
Desired Skills & Experience:
- SAP Analytics Cloud Experience
- Experience with Federal, State, Local, or Higher Education organizations
- Firm understanding of standard SDLC, lean, and agile practices
- Familiarity with Business Objects (BOBJ)
Benefits: "Some key components of our robust benefits include health insurance, paid leave, and retirement."
Pay: "The proposed salary for this position is:: $96,400 USD - $160,600 USD"
We also have some other sentences about SMX values etc. Those are boilerplate? "At SMX®, we are a team of technical and domain experts dedicated to enabling your mission..." That's marketing fluff but maybe substantive? It's not required to include? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. That paragraph is about SMX's mission etc. Could be considered substantive but maybe it's boilerplate? It's not EEO/legal. It's describing company. Might be considered part of About the role? Could include as part of About the role? But we already have intro. Could add another paragraph under About the role describing SMX's mission. However the instruction says "Prefer a few substantive sections over many thin ones." Might be okay to include as part of About the role.
But we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The paragraph about SMX's mission is not boilerplate; it's descriptive. Keep it.
Also there is line: "Selected applicant may be subject to a background investigation and/or education verification." That's somewhat boilerplate but maybe considered part of hiring process; could be considered application instructions? It's not exactly instruction to apply. Might be considered boilerplate? It's about selection process. Might be okay to keep? The instruction says remove application instructions. This is not an instruction to apply but a condition. Might be considered part of requirements? Could be included under Requirements? But it's not a skill. Might be considered a condition. Safer to drop it as it's not substantive about the job.
Also line: "SMX does not sponsor a new applicant for employment authorization or immigration related support for this position (i.e. H1B, F-1 OPT, ...)." That's also a condition; could be considered part of Requirements (citizenship). Already have Public Trust U.S. citizenship required. This line is about not sponsoring visa. Could be considered part of Requirements. Might keep as a note under Requirements.
But we already have Public Trust U.S. citizenship required. The visa sponsorship line is extra. Could include as a separate bullet under Requirements.
We need to decide.
Given the instruction to preserve ALL substantive information, we should keep that line as it's substantive about eligibility. So include under Requirements.
Now we need to format.
We'll produce:
- each duty. However the instruction says "any list of duties/requirements/benefits". If it's not already a list, we could still make a list? Might be okay. But to be safe, we can keep as
- for any list of duties/requirements/benefits". The posting has a paragraph describing duties; not a list. Could we still make a list? Might be considered a list of duties. Safer to keep as