Principal Embedded Software Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions.
We need to parse the posting.
Let's extract content:
First paragraph: "At MITRE, your passion fuels work that impacts our nation and improves lives. This is where your skills strengthen national security, cybersecurity, health, transportation, and citizen services. We’re a nonprofit engineering, applied research, and advanced technology organization working in the public interest. With objectivity and integrity at our core, we lead federally funded research and development centers for U.S. government agencies – collaborating with industry and academia to deliver integrated, high-impact solutions that advance our nation’s health, security, and prosperity. Our people tackle the toughest technical challenges, supported by competitive benefits, meaningful career development, and a culture of innovation, collaboration, and technical excellence. Choose MITRE for a career with purpose — and help shape the future."
That's about MITRE, could be "About the role" or "About MITRE". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put "About the role" heading and include that paragraph.
Next: "MITRE’s Electronic Systems Development department is seeking a Principal Embedded Software Engineer (Level 5) to support advanced research and development projects of national significance. The successful candidate will join a multidisciplinary team designing and prototyping proof-of-concept systems on embedded hardware platforms, with emphasis on software supporting Position, Navigation, and Timing (PNT) applications. Our diverse sponsors and research objectives provide opportunities such as: Real-time communication, navigation, and sensor systems leveraging modern System-on-a-Chip/Field Programmable Gate Array (SoC/FPGA) technology and Software-Defined Radio (SDR) platformsAdvanced architectures for high-throughput signal processing algorithmsTightly integrated platforms targeting low size, weight, power, and cost (SWaP-C) applicationsCross-disciplinary teams delivering mission-relevant prototypes and demonstrations"
We could include this under "About the role" as well, or maybe separate "Responsibilities"? Actually responsibilities are later.
Next: "Roles & Responsibilities: This position provides an opportunity to lead the design and prototyping of state-of-the-art embedded systems using commercial and custom platforms. Key responsibilities include: Architect, implement, test, document, and debug embedded software systems (primarily C/C++)Collaborate across multidisciplinary teams to define requirements and set technical direction for software development effortsEstablish and reinforce best practices for software design, implementation, integration, and verificationIntegrate and troubleshoot hardware/software interfaces across embedded platforms and RF/SDR-connected systemsMentor and develop junior engineers through technical guidance and reviews"
We can put under Responsibilities
with a - list.
Next: "Basic Qualifications: Typically requires a minimum of 10 years of related experience with a Bachelor’s degree; or 8 years and a Master’s degree; or a PhD with 5 years’ experience; or equivalent combination of related education and work experienceDegree in Computer Engineering, Systems Architecture, or related fieldExpert-level proficiency in high-performance programming languages (C, C++, Python)Demonstrated technical/task leadership experienceDemonstrated ability to architect complex embedded systemsExperience defining and encouraging best practices and design methodsDemonstrated engagement across multidisciplinary teams to define requirements and set technical direction of software development effortsWillingness/passion for mentoring and developing junior engineersStrong understanding of embedded systems, hardware interfacing, and signal processing conceptsIn-depth experience with software systems, systems architecture, and system-of-systems architectureComplete software development skillset including design, implementation, testing, documentation, and debuggingUnderstanding and experience with low-level processor architectures, operating system design, and hardware interfacingExperience with real-time operating systemsExperience with POSIX interfacesExperience with Linux/BSD user and kernel environmentsExperience with Position, Navigation, and Timing (PNT), RF communications, or radar/sensor systemsMust have an active Top Secret/SCI U.S Government issued Security Clearance. Per the U.S. Government’s eligibility requirements, you must be a U.S Citizen to be considered for a security clearance.This position requires a minimum of 3 days a week on-site."
We can put under
Requirements
(or Qualifications). The instruction includes both Requirements and Qualifications headings. We need to decide which to use. Usually "Basic Qualifications" could be under Requirements or Qualifications. We'll put under Qualifications
maybe. But we also have "Preferred Qualifications". Could combine both under Qualifications with sub-sections? But we must not create thin sections. We could have one Qualifications section containing both basic and preferred qualifications as lists.
We need to preserve all substantive info: include the basic qualifications list and preferred qualifications list.
Preferred Qualifications: "Existing program accessesAdvanced degree in Computer Engineering, Systems Architecture, or related fieldExcellent interpersonal skills, judgment, discretion, and tactHistory of building trusted relationships with demanding customers or leadersDemonstrated technical leadership shaping large projects and aligning operational needs, engineering reality, and programmatic execution"
Also note: "This requisition requires the candidate to have a minimum of the following clearance(s): Top Secret/SCI This requisition requires the hired candidate to have or obtain, within one year from the date of hire, the following clearance(s): Top Secret/SCI"
That's basically same as clearance requirement; we can include in Qualifications.
Also: "Salary compensation range and midpoint: $173,200 - $216,500 - $259,800 Annual Work Location Type: Onsite"
We need Pay and Schedule sections if posting actually states them. Pay: yes, salary range given. Schedule: "This position requires a minimum of 3 days a week on-site." Also "Annual Work Location Type: Onsite". So we have schedule info: onsite, minimum 3 days a week. So we can create Pay and Schedule sections.
Benefits: The posting mentions "competitive benefits" but no specific benefits list. It says "Benefits information may be found here." That's not specific. So we should NOT create a Benefits section because no specific content. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits not stated specifically, so omit.
Now we need to output HTML fragment with headings and appropriate content.
We must not repeat job title as heading. So no heading for Principal Embedded Software Engineer.
We must not put Job ID etc.
We must preserve all substantive info: ensure we include all details from the posting, except boilerplate.
Let's list sections:
- About the role (or About MITRE). We'll use "About the role". Include the introductory paragraphs about MITRE and the opportunity.
- Responsibilities: list.
- Qualifications: include basic and preferred qualifications, plus clearance, citizenship, onsite requirement? Actually onsite requirement is schedule; we will put in Schedule section. But we could also mention in Qualifications? Better to keep schedule separate.
- Pay: salary range.
- Schedule: onsite, minimum 3 days a week.
We must not create sections with filler. Ensure each heading has substantive content.
Now format.
We need to use - for any list of duties/requirements/benefits. For paragraphs, use
.
We need to ensure we don't duplicate lines.
Let's craft.
About the role: combine the initial MITRE description and the opportunity description.
Paragraph 1: At MITRE, your passion fuels work... (the first big paragraph). Paragraph 2: MITRE’s Electronic Systems Development department is seeking a Principal Embedded Software Engineer (Level 5) ... opportunities such as: Real-time communication... etc. That includes a colon and list but not bullet list; we can keep as prose or we could turn into
. The instruction: use - for any list of duties/requirements/benefits. This is a list of opportunities; could be considered a list. We'll make a
.
But we need to preserve all info; we can convert to list items.
Opportunities list:
- Real-time communication, navigation, and sensor systems leveraging modern System-on-a-Chip/Field Programmable Gate Array (SoC/FPGA) technology and Software-Defined Radio (SDR) platforms
- Advanced architectures for high-throughput signal processing algorithms
- Tightly integrated platforms targeting low size, weight, power, and cost (SWaP-C) applications
- Cross-disciplinary teams delivering mission-relevant prototypes and demonstrations
We'll include as .
Now Responsibilities list:
- Architect, implement, test, document, and debug embedded software systems (primarily C/C++)
- Collaborate across multidisciplinary teams to define requirements and set technical direction for software development efforts
- Establish and reinforce best practices for software design, implementation, integration, and verification
- Integrate and troubleshoot hardware/software interfaces across embedded platforms and RF/SDR-connected systems
- Mentor and develop junior engineers through technical guidance and reviews
Now Qualifications: we need to include basic qualifications and preferred qualifications.
We could split into two lists under same heading, maybe with a introducing.
Basic qualifications list items (need to split the long sentence). Let's parse:
- Typically requires a minimum of 10 years of related experience with a Bachelor’s degree; or 8 years and a Master’s degree; or a PhD with 5 years’ experience; or equivalent combination of related education and work experience
- Degree in Computer Engineering, Systems Architecture, or related field
- Expert-level proficiency in high-performance programming languages (C, C++, Python)
- Demonstrated technical/task leadership experience
- Demonstrated ability to architect complex embedded systems
- Experience defining and encouraging best practices and design methods
- Demonstrated engagement across multidisciplinary teams to define requirements and set technical direction of software development efforts
- Willingness/passion for mentoring and developing junior engineers
- Strong understanding of embedded systems, hardware interfacing, and signal processing concepts
- In-depth experience with software systems, systems architecture, and system-of-systems architecture
- Complete software development skillset including design, implementation, testing, documentation, and debugging
- Understanding and experience with low-level processor architectures, operating system design, and hardware interfacing
- Experience with real-time operating systems
- Experience with POSIX interfaces
- Experience with Linux/BSD user and kernel environments
- Experience with Position, Navigation, and Timing (PNT), RF communications, or radar/sensor systems
- Must have an active Top Secret/SCI U.S Government issued Security Clearance.
- Per the U.S. Government’s eligibility requirements, you must be a U.S Citizen to be considered for a security clearance.
- This position requires a minimum of 3 days a week on-site. (But we will move onsite to Schedule; but it's also a qualification? We'll keep in Schedule.)
We could keep onsite in Schedule only, not duplicate.
Now Preferred qualifications list:
- Existing program accesses
- Advanced degree in Computer Engineering, Systems Architecture, or related field
- Excellent interpersonal skills, judgment, discretion, and tact
- History of building trusted relationships with demanding customers or leaders
- Demonstrated technical leadership shaping large projects and aligning operational needs, engineering reality, and programmatic execution
Now Pay: Salary compensation range and midpoint: $173,200 - $216,500 - $259,800
We can present as
Salary range: $173,200 – $216,500 – $259,800 (midpoint).
Schedule: This position requires a minimum of 3 days a week on-site. Annual Work Location Type: Onsite.
We can combine: Onsite work required – minimum 3 days per
Requirements
(or Qualifications). The instruction includes both Requirements and Qualifications headings. We need to decide which to use. Usually "Basic Qualifications" could be under Requirements or Qualifications. We'll put underQualifications
maybe. But we also have "Preferred Qualifications". Could combine both under Qualifications with sub-sections? But we must not create thin sections. We could have one Qualifications section containing both basic and preferred qualifications as lists. We need to preserve all substantive info: include the basic qualifications list and preferred qualifications list. Preferred Qualifications: "Existing program accessesAdvanced degree in Computer Engineering, Systems Architecture, or related fieldExcellent interpersonal skills, judgment, discretion, and tactHistory of building trusted relationships with demanding customers or leadersDemonstrated technical leadership shaping large projects and aligning operational needs, engineering reality, and programmatic execution" Also note: "This requisition requires the candidate to have a minimum of the following clearance(s): Top Secret/SCI This requisition requires the hired candidate to have or obtain, within one year from the date of hire, the following clearance(s): Top Secret/SCI" That's basically same as clearance requirement; we can include in Qualifications. Also: "Salary compensation range and midpoint: $173,200 - $216,500 - $259,800 Annual Work Location Type: Onsite" We need Pay and Schedule sections if posting actually states them. Pay: yes, salary range given. Schedule: "This position requires a minimum of 3 days a week on-site." Also "Annual Work Location Type: Onsite". So we have schedule info: onsite, minimum 3 days a week. So we can create Pay and Schedule sections. Benefits: The posting mentions "competitive benefits" but no specific benefits list. It says "Benefits information may be found here." That's not specific. So we should NOT create a Benefits section because no specific content. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits not stated specifically, so omit. Now we need to output HTML fragment with headings and appropriate content.
We must not repeat job title as heading. So no heading for Principal Embedded Software Engineer.
We must not put Job ID etc.
We must preserve all substantive info: ensure we include all details from the posting, except boilerplate.
Let's list sections:
- About the role (or About MITRE). We'll use "About the role". Include the introductory paragraphs about MITRE and the opportunity.
- Responsibilities: list.
- Qualifications: include basic and preferred qualifications, plus clearance, citizenship, onsite requirement? Actually onsite requirement is schedule; we will put in Schedule section. But we could also mention in Qualifications? Better to keep schedule separate.
- Pay: salary range.
- Schedule: onsite, minimum 3 days a week.
We must not create sections with filler. Ensure each heading has substantive content.
Now format.
We need to use - for any list of duties/requirements/benefits. For paragraphs, use
.
We need to ensure we don't duplicate lines.
Let's craft.
About the role: combine the initial MITRE description and the opportunity description.
Paragraph 1: At MITRE, your passion fuels work... (the first big paragraph). Paragraph 2: MITRE’s Electronic Systems Development department is seeking a Principal Embedded Software Engineer (Level 5) ... opportunities such as: Real-time communication... etc. That includes a colon and list but not bullet list; we can keep as prose or we could turn into
. The instruction: use - for any list of duties/requirements/benefits. This is a list of opportunities; could be considered a list. We'll make a
.
But we need to preserve all info; we can convert to list items.
Opportunities list:
- Real-time communication, navigation, and sensor systems leveraging modern System-on-a-Chip/Field Programmable Gate Array (SoC/FPGA) technology and Software-Defined Radio (SDR) platforms
- Advanced architectures for high-throughput signal processing algorithms
- Tightly integrated platforms targeting low size, weight, power, and cost (SWaP-C) applications
- Cross-disciplinary teams delivering mission-relevant prototypes and demonstrations
We'll include as .
Now Responsibilities list:
- Architect, implement, test, document, and debug embedded software systems (primarily C/C++)
- Collaborate across multidisciplinary teams to define requirements and set technical direction for software development efforts
- Establish and reinforce best practices for software design, implementation, integration, and verification
- Integrate and troubleshoot hardware/software interfaces across embedded platforms and RF/SDR-connected systems
- Mentor and develop junior engineers through technical guidance and reviews
Now Qualifications: we need to include basic qualifications and preferred qualifications.
We could split into two lists under same heading, maybe with a introducing.
Basic qualifications list items (need to split the long sentence). Let's parse:
- Typically requires a minimum of 10 years of related experience with a Bachelor’s degree; or 8 years and a Master’s degree; or a PhD with 5 years’ experience; or equivalent combination of related education and work experience
- Degree in Computer Engineering, Systems Architecture, or related field
- Expert-level proficiency in high-performance programming languages (C, C++, Python)
- Demonstrated technical/task leadership experience
- Demonstrated ability to architect complex embedded systems
- Experience defining and encouraging best practices and design methods
- Demonstrated engagement across multidisciplinary teams to define requirements and set technical direction of software development efforts
- Willingness/passion for mentoring and developing junior engineers
- Strong understanding of embedded systems, hardware interfacing, and signal processing concepts
- In-depth experience with software systems, systems architecture, and system-of-systems architecture
- Complete software development skillset including design, implementation, testing, documentation, and debugging
- Understanding and experience with low-level processor architectures, operating system design, and hardware interfacing
- Experience with real-time operating systems
- Experience with POSIX interfaces
- Experience with Linux/BSD user and kernel environments
- Experience with Position, Navigation, and Timing (PNT), RF communications, or radar/sensor systems
- Must have an active Top Secret/SCI U.S Government issued Security Clearance.
- Per the U.S. Government’s eligibility requirements, you must be a U.S Citizen to be considered for a security clearance.
- This position requires a minimum of 3 days a week on-site. (But we will move onsite to Schedule; but it's also a qualification? We'll keep in Schedule.)
We could keep onsite in Schedule only, not duplicate.
Now Preferred qualifications list:
- Existing program accesses
- Advanced degree in Computer Engineering, Systems Architecture, or related field
- Excellent interpersonal skills, judgment, discretion, and tact
- History of building trusted relationships with demanding customers or leaders
- Demonstrated technical leadership shaping large projects and aligning operational needs, engineering reality, and programmatic execution
Now Pay: Salary compensation range and midpoint: $173,200 - $216,500 - $259,800
We can present as
Salary range: $173,200 – $216,500 – $259,800 (midpoint).
Schedule: This position requires a minimum of 3 days a week on-site. Annual Work Location Type: Onsite.
We can combine: Onsite work required – minimum 3 days per
. We need to ensure we don't duplicate lines. Let's craft. About the role: combine the initial MITRE description and the opportunity description. Paragraph 1: At MITRE, your passion fuels work... (the first big paragraph). Paragraph 2: MITRE’s Electronic Systems Development department is seeking a Principal Embedded Software Engineer (Level 5) ... opportunities such as: Real-time communication... etc. That includes a colon and list but not bullet list; we can keep as prose or we could turn into
- . The instruction: use
- for any list of duties/requirements/benefits. This is a list of opportunities; could be considered a list. We'll make a
- .
But we need to preserve all info; we can convert to list items.
Opportunities list:
- Real-time communication, navigation, and sensor systems leveraging modern System-on-a-Chip/Field Programmable Gate Array (SoC/FPGA) technology and Software-Defined Radio (SDR) platforms
- Advanced architectures for high-throughput signal processing algorithms
- Tightly integrated platforms targeting low size, weight, power, and cost (SWaP-C) applications
- Cross-disciplinary teams delivering mission-relevant prototypes and demonstrations
We'll include as
- .
Now Responsibilities list:
- Architect, implement, test, document, and debug embedded software systems (primarily C/C++)
- Collaborate across multidisciplinary teams to define requirements and set technical direction for software development efforts
- Establish and reinforce best practices for software design, implementation, integration, and verification
- Integrate and troubleshoot hardware/software interfaces across embedded platforms and RF/SDR-connected systems
- Mentor and develop junior engineers through technical guidance and reviews
Now Qualifications: we need to include basic qualifications and preferred qualifications.
We could split into two
- lists under same heading, maybe with a
introducing. Basic qualifications list items (need to split the long sentence). Let's parse: - Typically requires a minimum of 10 years of related experience with a Bachelor’s degree; or 8 years and a Master’s degree; or a PhD with 5 years’ experience; or equivalent combination of related education and work experience - Degree in Computer Engineering, Systems Architecture, or related field - Expert-level proficiency in high-performance programming languages (C, C++, Python) - Demonstrated technical/task leadership experience - Demonstrated ability to architect complex embedded systems - Experience defining and encouraging best practices and design methods - Demonstrated engagement across multidisciplinary teams to define requirements and set technical direction of software development efforts - Willingness/passion for mentoring and developing junior engineers - Strong understanding of embedded systems, hardware interfacing, and signal processing concepts - In-depth experience with software systems, systems architecture, and system-of-systems architecture - Complete software development skillset including design, implementation, testing, documentation, and debugging - Understanding and experience with low-level processor architectures, operating system design, and hardware interfacing - Experience with real-time operating systems - Experience with POSIX interfaces - Experience with Linux/BSD user and kernel environments - Experience with Position, Navigation, and Timing (PNT), RF communications, or radar/sensor systems - Must have an active Top Secret/SCI U.S Government issued Security Clearance. - Per the U.S. Government’s eligibility requirements, you must be a U.S Citizen to be considered for a security clearance. - This position requires a minimum of 3 days a week on-site. (But we will move onsite to Schedule; but it's also a qualification? We'll keep in Schedule.) We could keep onsite in Schedule only, not duplicate. Now Preferred qualifications list: - Existing program accesses - Advanced degree in Computer Engineering, Systems Architecture, or related field - Excellent interpersonal skills, judgment, discretion, and tact - History of building trusted relationships with demanding customers or leaders - Demonstrated technical leadership shaping large projects and aligning operational needs, engineering reality, and programmatic execution Now Pay: Salary compensation range and midpoint: $173,200 - $216,500 - $259,800 We can present as
Salary range: $173,200 – $216,500 – $259,800 (midpoint).
Schedule: This position requires a minimum of 3 days a week on-site. Annual Work Location Type: Onsite. We can combine:Onsite work required – minimum 3 days per