Front End Web Applications Developer (Junior) (5657)
SMX · United States · 4 wk ago
RemoteRemoteEngineering$73k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description: "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." That's about the role.
Then "Essential Duties & Responsibilities:" with a paragraph and bullet list? Actually it's a paragraph then bullet-like sentences separated by periods. We need to convert to
- for any list of duties/requirements/benefits. The duties are multiple sentences; we can treat each sentence as a list item. The paragraph before list? The first sentence after heading: "SAC is an all-in-one cloud product offered as software as a service (SaaS) for business intelligence (BI), planning, and predictive analytics." That's prose; then list of duties: "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."
We need to separate into list items. Probably each bullet is a duty. Let's parse:
- 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.
We also have a preceding sentence about SAC being product; maybe that is prose before list.
Now Required Skills & Experience: list of bullet items. We'll convert to
- .
Desired Skills & Experience: list.
Pay: we have salary range: $73,000 USD - $122,700 USD. So we need a Pay section with that info.
Benefits: mention health insurance, paid leave, retirement. Also mention competitive mix of compensation, learning & development opportunities, benefits. So we can list benefits.
Schedule: not mentioned explicitly; remote role, but no schedule details. So we should not create Schedule section.
We need headings: About the role, Responsibilities, Requirements (maybe combine Required Skills & Experience), Qualifications? Could combine Required Skills & Experience as Requirements. Desired Skills & Experience could be Qualifications or Skills. But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content.
We have About the role (intro). Responsibilities (duties). Requirements (Required Skills & Experience). Qualifications (maybe Desired Skills & Experience). Skills? Could be overlapping; maybe we can put Desired Skills & Experience under Qualifications. Or we could have Skills section for technical skills? But we already have Required Skills & Experience and Desired Skills & Experience. To avoid thin sections, we could combine Desired into Qualifications. Or we could have Skills section for both required and desired? But instructions: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (combining required and desired?), Benefits, Pay. But we need to preserve all info; we can't lose desired skills. We could put desired skills under Requirements as a subsection? But we must use headings only; we can't create subheadings. Could we put desired skills as part of Requirements list? That would mix required and desired but still preserve info. However the posting distinguishes required vs desired; but we can still include both under Requirements heading, maybe with a note? But we shouldn't invent filler. It's okay to combine.
Alternatively we could have Requirements (required) and Qualifications (desired). That's two sections, both substantive. That's okay.
We also have Skills heading maybe not needed.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now we need to output HTML fragment with
for each heading, then content:
for prose,
- for lists.
We must not repeat job title as heading. Not include Job ID etc.
Remove boilerplate: EEO, legal, etc. Also remove lines like "# LI-SA1#CJPOST", "The SMX salary determination process..." maybe part of Pay? Actually that is about salary determination; we can incorporate into Pay section prose. But we should not include fluff like "At SMX, one of our Core Values is to Invest in Our People..." that's benefits description; we can include in Benefits.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the salary determination description? It's substantive about how salary is determined. It's not boilerplate; it's about compensation. So we should include it in Pay section maybe as a paragraph before the range.
Similarly the paragraph about SMX being team of technical experts etc is maybe boilerplate? It's about company description; could be considered substantive? It's not required but it's info about company. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That paragraph about SMX being team of technical experts is not boilerplate; it's company description. Might be okay to keep. But we need to decide where to put it. Could be part of About the role? Already we have intro about role. Could add another paragraph under About the role.
But we must not invent or summarize away detail. So we should keep that paragraph.
Also the line "Selected applicant may be subject to a background investigation and/or education verification." is substantive; maybe we can put under Requirements or a separate section? Could be part of Requirements (clearance). But we already have Public Trust clearance mentioned in intro. This line is about background investigation; we could include in Requirements.
Also "SMX does not sponsor a new applicant for employment authorization..." is substantive about immigration; we could include in Requirements or a note.
We need to decide sections.
Let's outline:
About the role: combine first paragraph and the SMX description paragraph (starting "At SMX®, we are a team...") maybe also the mission statement paragraph.
Responsibilities: list of duties.
Requirements: include required skills & experience, plus Public Trust clearance, US citizenship, background investigation, no sponsorship.
Qualifications: desired skills & experience (SAP Analytics Cloud experience, experience with Federal etc, understanding of SDLC, lean, agile).
Benefits: health insurance, paid leave, retirement, competitive mix of compensation, learning & development opportunities.
Pay: salary determination process paragraph, then salary range.
We must not include Schedule.
Now format.
We need to ensure we don't include any empty headings.
Let's craft HTML.
We'll start with
About the role
then...
maybe multiple paragraphs. We need to preserve all info; we can split into multipleif needed. Let's write. About the role paragraph 1: "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." Paragraph 2: "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." That's all. Now Responsibilities heading. We need a
for the introductory sentence about SAC being product? Actually the first sentence after heading: "SAC is an all-in-one cloud product offered as software as a service (SaaS) for business intelligence (BI), planning, and predictive analytics." That's prose; we can put as
. Then list. Let's do:
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.
maybe intro: "Required Skills & Experience:" then list. But we should not repeat heading as list title; we can just have
- items. We'll include each bullet. Required skills list from posting: - Bachelor’s degree in computer science or related field (Software Engineering, Web Development) or equivalent job experience - 2 years of software engineering experience working across front-end web technologies (JavaScript, HTML5, CSS, etc.) - 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 a federal clearance Additionally: "Selected applicant may be subject to a background investigation and/or education verification." and "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)." We'll add those as list items. Now Qualifications heading (desired skills). Desired skills list: - SAP Analytics Cloud Experience - Experience with Federal, State, Local, or Higher Education organizations
- for lists.
We must not repeat job title as heading. Not include Job ID etc.
Remove boilerplate: EEO, legal, etc. Also remove lines like "# LI-SA1#CJPOST", "The SMX salary determination process..." maybe part of Pay? Actually that is about salary determination; we can incorporate into Pay section prose. But we should not include fluff like "At SMX, one of our Core Values is to Invest in Our People..." that's benefits description; we can include in Benefits.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the salary determination description? It's substantive about how salary is determined. It's not boilerplate; it's about compensation. So we should include it in Pay section maybe as a paragraph before the range.
Similarly the paragraph about SMX being team of technical experts etc is maybe boilerplate? It's about company description; could be considered substantive? It's not required but it's info about company. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That paragraph about SMX being team of technical experts is not boilerplate; it's company description. Might be okay to keep. But we need to decide where to put it. Could be part of About the role? Already we have intro about role. Could add another paragraph under About the role.
But we must not invent or summarize away detail. So we should keep that paragraph.
Also the line "Selected applicant may be subject to a background investigation and/or education verification." is substantive; maybe we can put under Requirements or a separate section? Could be part of Requirements (clearance). But we already have Public Trust clearance mentioned in intro. This line is about background investigation; we could include in Requirements.
Also "SMX does not sponsor a new applicant for employment authorization..." is substantive about immigration; we could include in Requirements or a note.
We need to decide sections.
Let's outline:
About the role: combine first paragraph and the SMX description paragraph (starting "At SMX®, we are a team...") maybe also the mission statement paragraph.
Responsibilities: list of duties.
Requirements: include required skills & experience, plus Public Trust clearance, US citizenship, background investigation, no sponsorship.
Qualifications: desired skills & experience (SAP Analytics Cloud experience, experience with Federal etc, understanding of SDLC, lean, agile).
Benefits: health insurance, paid leave, retirement, competitive mix of compensation, learning & development opportunities.
Pay: salary determination process paragraph, then salary range.
We must not include Schedule.
Now format.
We need to ensure we don't include any empty headings.
Let's craft HTML.
We'll start with
- .
Desired Skills & Experience: list.
Pay: we have salary range: $73,000 USD - $122,700 USD. So we need a Pay section with that info.
Benefits: mention health insurance, paid leave, retirement. Also mention competitive mix of compensation, learning & development opportunities, benefits. So we can list benefits.
Schedule: not mentioned explicitly; remote role, but no schedule details. So we should not create Schedule section.
We need headings: About the role, Responsibilities, Requirements (maybe combine Required Skills & Experience), Qualifications? Could combine Required Skills & Experience as Requirements. Desired Skills & Experience could be Qualifications or Skills. But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content.
We have About the role (intro). Responsibilities (duties). Requirements (Required Skills & Experience). Qualifications (maybe Desired Skills & Experience). Skills? Could be overlapping; maybe we can put Desired Skills & Experience under Qualifications. Or we could have Skills section for technical skills? But we already have Required Skills & Experience and Desired Skills & Experience. To avoid thin sections, we could combine Desired into Qualifications. Or we could have Skills section for both required and desired? But instructions: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (combining required and desired?), Benefits, Pay. But we need to preserve all info; we can't lose desired skills. We could put desired skills under Requirements as a subsection? But we must use headings only; we can't create subheadings. Could we put desired skills as part of Requirements list? That would mix required and desired but still preserve info. However the posting distinguishes required vs desired; but we can still include both under Requirements heading, maybe with a note? But we shouldn't invent filler. It's okay to combine.
Alternatively we could have Requirements (required) and Qualifications (desired). That's two sections, both substantive. That's okay.
We also have Skills heading maybe not needed.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now we need to output HTML fragment with