MuleSoft Developer
Peraton · Herndon, VA · 2 wk ago
Hybrid$80k–$128k/yrFull-time
We need to output HTML fragment with sections: About the role (maybe heading "About the role")? The instruction: use . The text:
"Use your technical proficiency with MuleSoft to design and develop business functionalities using inbuilt CRM/CX technologies and functionalities.
Understand Business Requirements, perform impact analysis and assess technical challenges/feasibility in achieving required business outcome.
Work with stakeholders to design, develop, document, and implement solutions on the MuleSoft platform and API development standards.
Identify ongoing risks and pain points throughout the project, develop and implement mitigation measures.
Work with system architects and support team members to address security and compliance (e.g. section 508, FISMA) requirements related to the setup of MuleSoft and Salesforce platform sandbox and development environments.
This is a hybrid role working in office 3 days a week in Herndon, VA."
The last sentence about hybrid role could be schedule; but also could be part of responsibilities. However we have a Schedule section maybe separate. The instruction: include a section ONLY when posting has real specific content. We have schedule info: hybrid role working in office 3 days a week in Herndon, VA. So we can put that under Schedule section. But also it's mentioned in responsibilities; we could keep it there but better to move to Schedule to avoid duplication. However we must preserve ALL substantive information; we can keep it in both places? Duplication is discouraged: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". Duplicated lines should be removed. So we should not duplicate the hybrid role sentence. We'll place it under Schedule section only, not under Responsibilities.
Thus Responsibilities list will be first five bullet points.
- Qualifications: we have Basic Qualifications and Preferred Qualifications. We'll make a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have content: About Peraton (company description) maybe not needed? The instruction says we reformat a job posting into clean HTML. Likely we include "About the role" section (the paragraph after "About The Role"). Then "Roles and Responsibilities" as Responsibilities. Then "Qualifications" (Basic Qualifications and Preferred Qualifications). Then maybe "Benefits" (Benefits Statement). Then "Pay" (Target Salary Range). Then maybe "Schedule" (Hybrid role working in office 3 days a week). Also location: Herndon, VA maybe part of About the role? Could be included in About the role paragraph. We must not include boilerplate like EEO, application statements, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we strip out: "About Peraton" maybe considered boilerplate? It's company overview; might be considered not essential? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Peraton" is substantive about company but maybe not needed? The job posting includes it; we could keep as a paragraph before sections? There's no heading for it; we could just include as a
at start. The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings like etc. But we should output only HTML fragment; we can include a
for company overview. We need to include sections only when posting has real specific content. We have: - About the role: paragraph after "About The Role": "Peraton is seeking an experienced MuleSoft Developer to join our team of qualified, diverse individuals. This position is in Herndon, VA. The qualified applicant will become part of Peraton's Department of State (DOS) Consular Systems Modernization (CSM) Program, for the Bureau of Diplomatic Technology (DT). This initiative is intended to modernize and consolidate the operational environment under a common technology framework to better support the services provided to CA's customers." We can put that in
About the role
then...
. - Responsibilities: list from "Roles and Responsibilities:" bullet points. We'll convert each sentence intoQualifications
then maybe subheadings? Not required; we can just list items. Could separate Basic and Preferred as- with maybe note? But we can just list all qualifications as items. However we need to preserve distinction? Not required but we can keep as separate
- ...
- with headings? The instruction only says use
for section headings; we could add for Basic and Preferred but not required. Safer to just list all qualifications in one list; but we might lose nuance. However we can include two lists with headings using
maybe. Let's do:
Qualifications
thenBasic Qualifications:
then- ... then
Preferred Qualifications:
then- ... This preserves info.
- Benefits: Benefits Statement paragraph. We'll make
Benefits
then...
. - Pay: Target Salary Range paragraph. We'll makePay
then...
. - Schedule: hybrid role working in office 3 days a week in Herndon, VA. We'll makeSchedule
then...
. We should also include location maybe in About the role? Already we have Herndon, VA in schedule; we could also mention location in About the role but that would duplicate. Better to keep location only in schedule. However About the role currently mentions "This position is in Herndon, VA." If we remove that, we lose location info. But we have schedule covering hybrid role working in office 3 days a week in Herndon, VA. That includes location. So we can drop the location sentence from About the role to avoid duplication. However we must preserve ALL substantive information; removing that sentence is okay if we keep the info elsewhere (schedule). The sentence "This position is in Herndon, VA." is duplicated by schedule sentence. So we can remove it from About the role. Thus About the role paragraph becomes: "Peraton is seeking an experienced MuleSoft Developer to join our team of qualified, diverse individuals. The qualified applicant will become part of Peraton's Department of State (DOS) Consular Systems Modernization (CSM) Program, for the Bureau of Diplomatic Technology (DT). This initiative is intended to modernize and consolidate the operational environment under a common technology framework to better support the services provided to CA's customers." Check if we lost any other info: The original also had "This position is in Herndon, VA." and "#DOSCSM". The hashtag maybe metadata; we can drop. Also "The qualified applicant will become part of Peraton's Department of State (DOS) Consular Systems Modernization (CSM) Program, for the Bureau of Diplomatic Technology (DT)." Good. Now Responsibilities list: we need to ensure we keep all five bullet points. Let's extract them exactly: 1. Use your technical proficiency with MuleSoft to design and develop business functionalities using inbuilt CRM/CX technologies and functionalities. 2. Understand Business Requirements, perform impact analysis and assess technical challenges/feasibility in achieving required business outcome. 3. Work with stakeholders to design, develop, document, and implement solutions on the MuleSoft platform and API development standards. 4. Identify ongoing risks and pain points throughout the project, develop and implement mitigation measures. 5. Work with system architects and support team members to address security and compliance (e.g. section 508, FISMA) requirements related to the setup of MuleSoft and Salesforce platform sandbox and development environments. We'll output asfor company overview? Actually we omitted About Peraton company overview. Should we include it? It's substantive but not required per instruction? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About Peraton paragraph is substantive about the company. If we omit it, we lose info. However we could include it as a
before sections, not as a heading. That's allowed. The instruction only mandates using
for section headings; we can have other elements like
. So we should include the About Peraton paragraph as a
at top. Thus final HTML:
About Peraton Peraton is a next-generation national security company that drives missions of consequence spanning the globe and extending to the farthest reaches of the galaxy. As the world's leading mission capability integrator and transformative enterprise IT provider, we deliver trusted, highly differentiated solutions and technologies to protect our nation and allies. Peraton operates at the critical nexus between traditional and nontraditional threats across all domains: land, sea, space, air, and cyberspace. The company serves as a valued partner to essential government agencies and supports every branch of the U.S. armed forces. Each day, our employees solve the most daunting challenges that our customers face. Visit peraton.com to learn how we're keeping people around the world safe and secure.
ThenAbout the role
...
ThenResponsibilities
- ...
Qualifications
Basic Qualifications:
<