Juniper Network Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose among those. We should not create other headings like Overview, Location, Travel, etc unless they fit into those categories. Could embed location and travel in a short
maybe under About the role? The instruction: "Prefer a few substantive sections over many thin ones." So we could have sections: Responsibilities, Qualifications (maybe combine Required Skills, Desired Skills, Certifications), Benefits, Pay, Schedule. Also maybe About the role (overview). We need to decide. We must not repeat job title as heading. The page already shows it, so we don't add a heading for job title. We need to include all substantive info. So we need to include location, travel, work environment, physical demands, work authorization/security clearance, etc. Where to put them? Could be under "About the role" or maybe under "Qualifications"? But they are not qualifications. Perhaps we can create a section "About the role" that includes overview, location, travel, work environment, security clearance, etc. That seems appropriate. Thus sections: - About the role: overview paragraph, location, travel, work environment (maybe short), security clearance (U.S Citizen, active Secret clearance). Could also include physical demands? Might be too much but we can include as part of About the role. - Responsibilities: as given. - Qualifications: maybe combine Required Skills, Desired Skills, Certifications into a list? But we need to use
- for any list of duties/requirements/benefits. So we can have sub-sections? The instruction only says use
for section headings, and
- for any list of duties/requirements/benefits, and
for prose. So we can have headings like Responsibilities, Qualifications, Benefits, Pay, Schedule. Under Qualifications we can have subheadings? Not allowed because only those headings are listed; but we could still use
for subheadings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. So we can have Qualifications section containing paragraphs and lists for required skills, desired skills, certifications. We need to preserve all substantive info. So we need to include required skills list, desired skills list, certifications list. We can do:
Qualifications
Required:
- 5 years of experience ... etc
Desired:
- ...
Certifications:
- ...
About the role
then acontaining overview sentences. Then maybe a
- for location, travel, work environment, physical demands, security clearance? But those are not lists of duties/requirements/benefits; they are metadata. Could be
- for lists. For location/travel etc we can just put in
sentences. Let's draft:
About the role
We are seeking a Juniper Network Engineer to join our team supporting US Air Force Air Mobility Command Base Infrastructure modification. TekSynap is a fast-growing high-tech company that understands both the pace of technology today and the need to have a comprehensive well planned information management environment. “Technology moving at the speed of thought” embodies these principles – the need to nimbly utilize the best that information technology offers to meet the business needs of our Federal Government customers.
<
lines. Simplify: Use
for prose, and
- for any list of duties/requirements/benefits, and