Program Manager II - Software Engineering
for each section heading. Only include sections that have real specific content. The posting includes: About the Company (but we should not repeat job title; we can include About the Company? Not listed as a heading; but we can maybe include as a paragraph? The instructions: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not limited to those? Probably we should only use those headings if content exists. The posting includes "About the Company" and "About the Role". We could treat "About the Role" as a section heading About the Role
. "About the Company" maybe not required but could be included as a paragraph without heading? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can also use other headings if appropriate? Safer to stick to those. We have content for About the role (the paragraph after "About the Role"). We have Responsibilities (list). We have Requirements (list). There's also EDUCATION/EXPERIENCE which could be Qualifications. There's also Skills (maybe separate). The posting includes many skill items under REQUIREMENTS; we could split into Skills and Qualifications? We could treat REQUIREMENTS as Qualifications, and maybe separate Skills? But we need to avoid thin sections. Let's map:
- About the Role: paragraph(s) describing role.
- Responsibilities: bullet list under RESPONSIBILITIES.
- Requirements: bullet list under REQUIREMENTS (maybe split into Qualifications and Skills). But we can just have Requirements section with list.
- Qualifications: maybe EDUCATION/EXPERIENCE bullet list.
- Skills: maybe we can extract specific skills like Atlassian tools, financial management, communication, etc. But that overlaps with Requirements. To avoid duplication, we could have Requirements (includes both). But instruction: prefer few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But they ask to use headings like Qualifications, Skills. We could include Qualifications (education/experience) and Skills (technical skills). Let's parse:
From text:
REQUIREMENTS
- High-level proficiency in Atlassian tools - Jira, Confluence, and BigPicture (or equivalent extension), Tempo, Script Runner and Jira Automation; ability to configure and administer projects from scratch.
- Strong command of project financial management: budgeting, forecasting, variance tracking, and cost reporting.
- Excellent cross-functional communication skills, written and verbal, with demonstrated ability to manage engineering and customer relationships at a technical level.
- Proven ability to manage multiple software development programs simultaneously in a fast-paced, globally distributed environment.
- Strong analytical skills; ability to build and use tools to synthesize project data into actionable reporting.
- Deep understanding of cross-functional interdependencies in embedded software product development, from architecture through release and customer hand-off.
- Exceptional attention to detail and time management discipline.
- Working knowledge of embedded software development processes: Agile/Scrum or Kanban delivery, code review and CI/CD pipelines, and release/version management.
- Familiarity with embedded Linux, RTOS, and wireless connectivity stacks (e.g., Wi-Fi, Bluetooth, Cellular) is strongly preferred.
- Understanding of the technical considerations specific to custom SOM/SBC software co-development programs, including board support packages and driver bring-up.
- Proficiency in Microsoft Excel and data analysis tools for financial and schedule tracking.
EDUCATION/EXPERIENCE
- Bachelor’s degree in Computer Science, Software Engineering, or a related technical field. Equivalent professional experience considered in lieu of degree.
- 5+ years of program or project management experience in an electronics design environment - embedded software or firmware development experience required.
- Direct experience managing customer co-development programs (NRE-based or joint development agreements) is strongly preferred.
- Experience with NXP i.MX, TI, or similar embedded processor platforms, and their associated software/BSP ecosystems, and wireless certifications is a plus.
Thus we can have:
About the Role
About the Role
. "About the Company" maybe not required but could be included as a paragraph without heading? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can also use other headings if appropriate? Safer to stick to those. We have content for About the role (the paragraph after "About the Role"). We have Responsibilities (list). We have Requirements (list). There's also EDUCATION/EXPERIENCE which could be Qualifications. There's also Skills (maybe separate). The posting includes many skill items under REQUIREMENTS; we could split into Skills and Qualifications? We could treat REQUIREMENTS as Qualifications, and maybe separate Skills? But we need to avoid thin sections. Let's map:
- About the Role: paragraph(s) describing role.
- Responsibilities: bullet list under RESPONSIBILITIES.
- Requirements: bullet list under REQUIREMENTS (maybe split into Qualifications and Skills). But we can just have Requirements section with list.
- Qualifications: maybe EDUCATION/EXPERIENCE bullet list.
- Skills: maybe we can extract specific skills like Atlassian tools, financial management, communication, etc. But that overlaps with Requirements. To avoid duplication, we could have Requirements (includes both). But instruction: prefer few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But they ask to use headings like Qualifications, Skills. We could include Qualifications (education/experience) and Skills (technical skills). Let's parse:
From text:
REQUIREMENTS
- High-level proficiency in Atlassian tools - Jira, Confluence, and BigPicture (or equivalent extension), Tempo, Script Runner and Jira Automation; ability to configure and administer projects from scratch.
- Strong command of project financial management: budgeting, forecasting, variance tracking, and cost reporting.
- Excellent cross-functional communication skills, written and verbal, with demonstrated ability to manage engineering and customer relationships at a technical level.
- Proven ability to manage multiple software development programs simultaneously in a fast-paced, globally distributed environment.
- Strong analytical skills; ability to build and use tools to synthesize project data into actionable reporting.
- Deep understanding of cross-functional interdependencies in embedded software product development, from architecture through release and customer hand-off.
- Exceptional attention to detail and time management discipline.
- Working knowledge of embedded software development processes: Agile/Scrum or Kanban delivery, code review and CI/CD pipelines, and release/version management.
- Familiarity with embedded Linux, RTOS, and wireless connectivity stacks (e.g., Wi-Fi, Bluetooth, Cellular) is strongly preferred.
- Understanding of the technical considerations specific to custom SOM/SBC software co-development programs, including board support packages and driver bring-up.
- Proficiency in Microsoft Excel and data analysis tools for financial and schedule tracking.
EDUCATION/EXPERIENCE
- Bachelor’s degree in Computer Science, Software Engineering, or a related technical field. Equivalent professional experience considered in lieu of degree.
- 5+ years of program or project management experience in an electronics design environment - embedded software or firmware development experience required.
- Direct experience managing customer co-development programs (NRE-based or joint development agreements) is strongly preferred.
- Experience with NXP i.MX, TI, or similar embedded processor platforms, and their associated software/BSP ecosystems, and wireless certifications is a plus.
Thus we can have:
About the Role
... (the paragraph after About the Role)
Responsibilities
- ...
Requirements
- ... (the REQUIREMENTS bullet list)
Qualifications
- ... (the EDUCATION/EXPERIENCE bullet list)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow examples. Probably we can include About the Company as a paragraph without heading, or we could treat as About the Company
though not in list but seems okay. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are typical headings; we could still use About the Company as heading but it's not in examples. Safer to include as a paragraph without heading? The page already shows job title; they said do NOT repeat the job title as a heading. About the Company is not job title, so could be heading. But they didn't forbid. I'd include About the Company as a paragraph (maybe
) without heading to keep minimal. Let's extract About the Company paragraph: "We engineer connectivity and embedded compute solutions that power connected devices worldwide. With decades of experience, our solutions are secure by design, globally compliant and supported over long lifecycles." About the Role paragraph: after "About the Role"The Program Manager II - Software Engineering leads the planning and delivery of custom embedded software, firmware, and connectivity stacks that run on Ezurio's Wi-Fi Radios, System-on-Modules (SOMs) and Single Board Computers (SBCs). These multi-discipline software programs — spanning radio firmware, board support packages, drivers, middleware, cloud/edge connectivity, and customer application enablement — require disciplined project management from concept through release and long-term support. Working with Product Management, and Engineering teams you will be an experienced user of Atlassian tools (Jira, Confluence, Jira Product Discovery), and extensions such as BigPicture, Eazy Bi, Tempo, bringing hands-on experience managing embedded software development programs in an electronics design environment. Both internal and customer-facing projects are scoped; strong stakeholder management and customer-facing communication skills are essential. This role is preferably based in hybrid work arrangement in Akron, Ohio. Remote candidates will also be considered. Legal authorization to work in the US is required." We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep that paragraph exactly (maybe minor punctuation). We'll output as
. Now Responsibilities bullet list: need to capture each bullet under RESPONSIBILITIES heading. Let's extract: - Own end-to-end program management for custom software/firmware co-development programs, from project initiation through production release and sustaining support. - Define, plan, and maintain detailed project schedules, release plans, and financial budgets in alignment with customer commitments and internal targets. - Simultaneously manage priorities, direction, and resource allocation across all active software programs. - Identify, track, and proactively mitigate project risks; escalate issues with clear options and recommendations. - Manage cost targets as established by Senior Management, tracking actuals against budget throughout the software development lifecycle. - Atlassian Toolset & Reporting - Stand up, configure, and maintain all projects within the Atlassian toolset (Jira, Confluence, BigPicture, Tempo). - Maintain accurate, up-to-date project plans, project boards, and associated collateral in line with Ezurio engineering process requirements. - Assist in the maintenance, development and improvement of Jira tools and processes using Jira automation, Script Runner, Eazy Bi (MDX) and Power Bi (Power Query & DAX) - Generate and present weekly snapshot reports for both internal stakeholders and external customers. - Produce and present program status reports to the Senior Leadership Team (SLT), including schedule health, budget variance, and key risks. - Cross-Functional & Customer Collaboration - Serve as the primary project management interface for customers throughout the software co-development lifecycle, ensuring clear communication on scope, schedule, and deliverables. - Lead and coordinate globally distributed engineering teams spanning embedded software, firmware, cloud, QA/test, and hardware disciplines. - Partner with department heads to manage shared engineering resources across multiple concurrent software programs. - Coordinate activities between software engineering, hardware engineering, manufacturing, and quality to meet product development requirements and customer commitments. - Process & Quality - Generate and facilitate documentation in accordance with Ezurio engineering procedures and quality standards. - Adhere to and support quality and safety systems and standards, including secure software development and release practices, across all managed programs. - Contribute to the continuous improvement of project management and software delivery practices within the Custom SOM & SBC group. We need to preserve as list items; sub-bullets maybe we can flatten? The instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can keep flat list items with the sub-bullets as separate
- . Might be okay to keep hierarchy using nested
- . Safer to keep flat but preserve meaning. We'll just make each bullet as
- . For headings like "Atlassian Toolset & Reporting" that is a heading within responsibilities; we could treat as a
- with bold? But we should not invent headings inside list. Better to keep as
- with the text including the heading. Eg: "
- Atlassian Toolset & Reporting: Stand up, configure, and maintain all projects within the Atlassian toolset (Jira, Confluence, BigPicture, Tempo). " but we need to keep the sub-bullets separate. Could do:
- Atlassian Toolset & Reporting then nested
- for subitems. That is acceptable as list of duties. We'll do nested.
Similarly for Cross-Functional & Customer Collaboration and Process & Quality.
Now Requirements bullet list: extract each bullet.
- High-level proficiency in Atlassian tools - Jira, Confluence, and BigPicture (or equivalent extension), Tempo, Script Runner and Jira Automation; ability to configure and administer projects from scratch.
- Strong command of project financial management: budgeting, forecasting, variance tracking, and cost reporting.
- Excellent cross-functional communication skills, written and verbal, with demonstrated ability to manage engineering and customer relationships at a technical level.
- Proven ability to manage multiple software development programs simultaneously in a fast-paced, globally distributed environment.
- Strong analytical skills; ability to build and use tools to synthesize project data into actionable reporting.
- Deep understanding of cross-functional interdependencies in embedded software product development, from architecture through release and customer hand-off.
- Exceptional attention to detail and time management discipline.
- Working knowledge of embedded software development processes: Agile/Scrum or Kanban delivery, code review and CI/CD pipelines, and release/version management.
- Familiarity with embedded Linux, RTOS, and wireless connectivity stacks (e.g., Wi-Fi, Bluetooth, Cellular) is strongly preferred.
- Understanding of the technical considerations specific to custom SOM/SBC software