Radio Frequency Designer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the description and extract sections.
The posting includes:
- Description (company overview) maybe "About the role" or "Position Overview/Mandate". Could be "About the role" heading.
- Position Overview/Mandate: description of role.
- "Make an Impact with US:" maybe part of responsibilities.
- "What You’ll Be Doing:" list of duties.
- "Who You Are:" qualifications/requirements.
- "Nice to Have:" maybe skills or qualifications.
- "Location and travel:" location and travel info (maybe schedule? travel). Could be schedule? Not exactly schedule. Might be location and travel.
- "Benefits" section.
- "About Fidus & Why Work Here" maybe about company.
We need to decide which sections to include: About the role (position overview), Responsibilities (What You’ll Be Doing), Requirements/Qualifications (Who You Are), Skills (maybe Nice to Have), Benefits, Location and travel (maybe Schedule? but schedule not given; location and travel includes travel requirement). Pay not mentioned, so omit Pay section. Schedule not mentioned (no specific schedule like full-time/part-time). So omit Schedule.
We must not create sections with filler. So include only those with content.
We must use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like bullet points.
We need to extract bullet lists from "What You’ll Be Doing:" and "Who You Are:" and "Nice to Have:" and "Benefits". Also maybe "Location and travel:" includes travel requirement.
We must not include boilerplate like EEO, AI statement, etc. Remove those.
We must not duplicate lines.
We need to ensure we keep all substantive info.
Let's parse.
First, company description: "Fidus is a global high-tech design firm headquartered in Ottawa, with additional design centres in Kitchener-Waterloo and San Jose. We specialize in leading-edge electronic product development, with hardware, RF/wireless, embedded software, FPGA/ASIC, and signal integrity teams working together to design and deliver next-generation products for clients in emerging technology markets."
That's about the company; could be part of "About Fidus & Why Work Here". Might be considered "About the role"? Actually "About Fidus & Why Work Here" is later. The earlier description could be part of "About the role" or maybe we can include a short paragraph under "About the role". We'll include it as part of "About the role" heading.
Then "Position Overview/Mandate:" paragraph: "The RF Designer owns complete RF subsystems on Fidus client programs — from the antenna port through the front-end, frequency conversion and data converters, that present into the DSP and/or FPGA fabric. You will set the RF architecture, build the frequency and sampling plans, design and model the transmit and receive lineups, and prove the performance on the bench, working at microwave frequencies up to 40 GHz.This role suits an RF designer who has carried subsystems from architecture to characterized, manufacturable hardware, is ready to be the RF authority on a cross-functional team, and works directly with customers — taking pride in designs rigorously modeled before build and rigorously measured after."
We can combine with earlier company description maybe under "About the role". Or we could have separate "Position Overview" but heading must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company overview and position overview under "About the role". That seems fine.
Next: "Make an Impact with US:" paragraph: "You'll collaborate across FPGA/DSP, hardware, embedded software, verification, SI/PI, PCB layout and mechanical/thermal design, delivering real products for our clients.In practice, that means SatCom payloads, ground modems and portable terminals; GNSS and precision synchronization; radar and multi-sensor fusion; software defined radios; semiconductor characterization and test fixturing; industrial and private network radios; and medical telemetry."
That could be part of Responsibilities or maybe about role. We'll include under Responsibilities as introductory paragraph.
Then "What You’ll Be Doing:" list of duties (bullet points). We'll put under Responsibilities as a
.
Then "Who You Are:" list of qualifications (bullet points). We'll put under Requirements (or Qualifications). The heading list includes both Requirements and Qualifications; we need to decide which to use. Could combine both under Requirements. But we should not create thin sections; maybe we can have Requirements (includes Who You Are) and Skills (Nice to Have). Or we could have Qualifications for Who You Are and Skills for Nice to Have. Since both are present, we can have two sections: Requirements (maybe for mandatory) and Skills (nice to have). However the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Who You Are and Nice to Have into one Requirements section? But they are distinct: mandatory vs nice-to-have. Could still be one section but we can separate with headings? Might be considered thin if we split. Better to have one section "Requirements" that includes both mandatory and nice-to-have? But then we lose distinction. However we could have "Requirements" for mandatory and "Skills" for nice-to-have. That's two sections, each substantive. That seems okay.
Thus:
- About the role
: includes company description and position overview/mandate and maybe "Make an Impact with US:"? Actually that is more about impact; could be part of responsibilities. We'll keep About the role as company overview and position overview.
- Responsibilities
: includes "Make an Impact with US:" paragraph and the bullet list under "What You’ll Be Doing:".
- Requirements
: includes "Who You Are:" bullet list (mandatory).
- Skills
: includes "Nice to Have:" bullet list.
- Benefits
: includes benefits paragraph.
- Location and travel
: includes location and travel paragraph. However location and travel is not in the allowed headings list (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Location and travel is not listed. Should we omit? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning examples, not exhaustive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not create a heading for Location and travel; we could fold that info into another section, maybe Responsibilities or About the role. Since travel is a requirement, maybe we can include under Requirements (as a bullet). Or we could include under Responsibilities? Travel is not a duty but a condition. Could be placed under Requirements as a bullet: "Location: Fully remote role and requires a minimum of 20% travel, including domestic and international." That seems appropriate.
Thus we will not create a separate Location and travel heading.
Now Benefits: we have paragraph: "Our competitive compensation package also includes a comprehensive benefits package, including medical, dental, and vision plans, matching 401(k) contributions, annual profit-sharing bonus, along with other supplementary benefits." Also there is line: "We also recognize that candidates show interest throughout different career stages and welcome all applications. When there is a great fit, the level of the role may be shifted as applicable." That's more about hiring process; could be considered boilerplate? It's not EEO but still generic. Might be considered filler? It's substantive? It's about flexibility of role level. Might be kept but could be considered not essential. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This line is not exactly boilerplate but it's about applications. Might be considered application instructions? It's about level shifting. Could be considered part of the posting but not essential. Safer to keep? It's not about benefits. Could be placed under About the role? Might be considered filler. I'd lean to omit it as it's not directly about the role responsibilities/requirements/benefits. It's about hiring flexibility. Might be considered boilerplate-ish. I'd omit.
Also later "About Fidus & Why Work Here" paragraph: we already used company overview earlier; but there is more detailed about Fidus history etc. That could be considered About the role or maybe we could include under About the role as additional prose. It's substantive about company. We'll include it under About the role after the position overview.
Thus About the role will contain:
- Company overview paragraph (first paragraph)
- Position Overview/Mandate paragraph
- Maybe "Make an Impact with US:"? Actually we placed that under Responsibilities. So About the role will have first two paragraphs.
Then after that we could also include the "About Fidus & Why Work Here" paragraph (the longer one). That is also about company. So we can append.
Now Responsibilities:
- Intro paragraph: "Make an Impact with US:" paragraph (the collaboration and examples)
- Then bullet list from "What You’ll Be Doing:".
We need to convert each bullet into
- . The bullet list includes many items each starting with a capital letter and ending with a period. We'll keep them as is.
Now Requirements:
- Bullet list from "Who You Are:" (mandatory). Each bullet is a sentence. We'll keep.
Now Skills:
- Bullet list from "Nice to Have:" (nice to have). Each bullet.
Now Benefits:
- Paragraph: "Our competitive compensation package also includes a comprehensive benefits package, including medical, dental, and vision plans, matching 401(k) contributions, annual profit-sharing bonus, along with other supplementary benefits."
We might also include any other benefits like "matching 401(k) contributions" etc. Already there.
Now we must ensure we don't repeat any content. Also ensure we don't include any boilerplate like "Automated tools (including AI) support our initial screening..." etc. Remove.
Now produce HTML fragment.
Let's craft.
First, About the role:
Fidus is a global high-tech design firm headquartered in Ottawa, with additional design centres in Kitchener‑Waterloo and San Jose. We specialize in leading‑edge electronic product development, with hardware, RF/wireless, embedded software, FPGA/ASIC, and signal integrity teams working together to design and deliver next‑generation products for clients in emerging technology markets.
The RF Designer owns complete RF subsystems on Fidus client programs — from the antenna port through the front‑end, frequency conversion and data converters, that present into the DSP and/or FPGA fabric. You will set the RF architecture, build the frequency and sampling plans, design and model the transmit and receive lineups, and prove the performance on the bench, working at microwave frequencies up to 40 GHz. This role suits an RF designer who has carried subsystems from architecture to characterized, manufacturable hardware, is ready to be the RF authority on a cross‑functional team, and works directly with customers — taking pride in designs rigorously modeled before build and rigorously measured after.
Since 2001, Fidus has completed over 4,000 projects for more than 400 customers across industries including Telecom/Datacom, Aerospace & Defence, Consumer, Semiconductors, Industrial/Automotive Controls, and
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like bullet points. We need to extract bullet lists from "What You’ll Be Doing:" and "Who You Are:" and "Nice to Have:" and "Benefits". Also maybe "Location and travel:" includes travel requirement. We must not include boilerplate like EEO, AI statement, etc. Remove those. We must not duplicate lines. We need to ensure we keep all substantive info. Let's parse. First, company description: "Fidus is a global high-tech design firm headquartered in Ottawa, with additional design centres in Kitchener-Waterloo and San Jose. We specialize in leading-edge electronic product development, with hardware, RF/wireless, embedded software, FPGA/ASIC, and signal integrity teams working together to design and deliver next-generation products for clients in emerging technology markets." That's about the company; could be part of "About Fidus & Why Work Here". Might be considered "About the role"? Actually "About Fidus & Why Work Here" is later. The earlier description could be part of "About the role" or maybe we can include a short paragraph under "About the role". We'll include it as part of "About the role" heading. Then "Position Overview/Mandate:" paragraph: "The RF Designer owns complete RF subsystems on Fidus client programs — from the antenna port through the front-end, frequency conversion and data converters, that present into the DSP and/or FPGA fabric. You will set the RF architecture, build the frequency and sampling plans, design and model the transmit and receive lineups, and prove the performance on the bench, working at microwave frequencies up to 40 GHz.This role suits an RF designer who has carried subsystems from architecture to characterized, manufacturable hardware, is ready to be the RF authority on a cross-functional team, and works directly with customers — taking pride in designs rigorously modeled before build and rigorously measured after." We can combine with earlier company description maybe under "About the role". Or we could have separate "Position Overview" but heading must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company overview and position overview under "About the role". That seems fine. Next: "Make an Impact with US:" paragraph: "You'll collaborate across FPGA/DSP, hardware, embedded software, verification, SI/PI, PCB layout and mechanical/thermal design, delivering real products for our clients.In practice, that means SatCom payloads, ground modems and portable terminals; GNSS and precision synchronization; radar and multi-sensor fusion; software defined radios; semiconductor characterization and test fixturing; industrial and private network radios; and medical telemetry." That could be part of Responsibilities or maybe about role. We'll include under Responsibilities as introductory paragraph. Then "What You’ll Be Doing:" list of duties (bullet points). We'll put under Responsibilities as a
- .
Then "Who You Are:" list of qualifications (bullet points). We'll put under Requirements (or Qualifications). The heading list includes both Requirements and Qualifications; we need to decide which to use. Could combine both under Requirements. But we should not create thin sections; maybe we can have Requirements (includes Who You Are) and Skills (Nice to Have). Or we could have Qualifications for Who You Are and Skills for Nice to Have. Since both are present, we can have two sections: Requirements (maybe for mandatory) and Skills (nice to have). However the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Who You Are and Nice to Have into one Requirements section? But they are distinct: mandatory vs nice-to-have. Could still be one section but we can separate with headings? Might be considered thin if we split. Better to have one section "Requirements" that includes both mandatory and nice-to-have? But then we lose distinction. However we could have "Requirements" for mandatory and "Skills" for nice-to-have. That's two sections, each substantive. That seems okay.
Thus:
-
- . The bullet list includes many items each starting with a capital letter and ending with a period. We'll keep them as is.
Now Requirements:
- Bullet list from "Who You Are:" (mandatory). Each bullet is a sentence. We'll keep.
Now Skills:
- Bullet list from "Nice to Have:" (nice to have). Each bullet.
Now Benefits:
- Paragraph: "Our competitive compensation package also includes a comprehensive benefits package, including medical, dental, and vision plans, matching 401(k) contributions, annual profit-sharing bonus, along with other supplementary benefits."
We might also include any other benefits like "matching 401(k) contributions" etc. Already there.
Now we must ensure we don't repeat any content. Also ensure we don't include any boilerplate like "Automated tools (including AI) support our initial screening..." etc. Remove.
Now produce HTML fragment.
Let's craft.
First, About the role:
Fidus is a global high-tech design firm headquartered in Ottawa, with additional design centres in Kitchener‑Waterloo and San Jose. We specialize in leading‑edge electronic product development, with hardware, RF/wireless, embedded software, FPGA/ASIC, and signal integrity teams working together to design and deliver next‑generation products for clients in emerging technology markets.
The RF Designer owns complete RF subsystems on Fidus client programs — from the antenna port through the front‑end, frequency conversion and data converters, that present into the DSP and/or FPGA fabric. You will set the RF architecture, build the frequency and sampling plans, design and model the transmit and receive lineups, and prove the performance on the bench, working at microwave frequencies up to 40 GHz. This role suits an RF designer who has carried subsystems from architecture to characterized, manufacturable hardware, is ready to be the RF authority on a cross‑functional team, and works directly with customers — taking pride in designs rigorously modeled before build and rigorously measured after.
Since 2001, Fidus has completed over 4,000 projects for more than 400 customers across industries including Telecom/Datacom, Aerospace & Defence, Consumer, Semiconductors, Industrial/Automotive Controls, and
About the role
: includes company description and position overview/mandate and maybe "Make an Impact with US:"? Actually that is more about impact; could be part of responsibilities. We'll keep About the role as company overview and position overview. -Responsibilities
: includes "Make an Impact with US:" paragraph and the bullet list under "What You’ll Be Doing:". -Requirements
: includes "Who You Are:" bullet list (mandatory). -Skills
: includes "Nice to Have:" bullet list. -Benefits
: includes benefits paragraph. -Location and travel
: includes location and travel paragraph. However location and travel is not in the allowed headings list (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Location and travel is not listed. Should we omit? The instruction: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning examples, not exhaustive? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not create a heading for Location and travel; we could fold that info into another section, maybe Responsibilities or About the role. Since travel is a requirement, maybe we can include under Requirements (as a bullet). Or we could include under Responsibilities? Travel is not a duty but a condition. Could be placed under Requirements as a bullet: "Location: Fully remote role and requires a minimum of 20% travel, including domestic and international." That seems appropriate. Thus we will not create a separate Location and travel heading. Now Benefits: we have paragraph: "Our competitive compensation package also includes a comprehensive benefits package, including medical, dental, and vision plans, matching 401(k) contributions, annual profit-sharing bonus, along with other supplementary benefits." Also there is line: "We also recognize that candidates show interest throughout different career stages and welcome all applications. When there is a great fit, the level of the role may be shifted as applicable." That's more about hiring process; could be considered boilerplate? It's not EEO but still generic. Might be considered filler? It's substantive? It's about flexibility of role level. Might be kept but could be considered not essential. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This line is not exactly boilerplate but it's about applications. Might be considered application instructions? It's about level shifting. Could be considered part of the posting but not essential. Safer to keep? It's not about benefits. Could be placed under About the role? Might be considered filler. I'd lean to omit it as it's not directly about the role responsibilities/requirements/benefits. It's about hiring flexibility. Might be considered boilerplate-ish. I'd omit. Also later "About Fidus & Why Work Here" paragraph: we already used company overview earlier; but there is more detailed about Fidus history etc. That could be considered About the role or maybe we could include under About the role as additional prose. It's substantive about company. We'll include it under About the role after the position overview. Thus About the role will contain: - Company overview paragraph (first paragraph) - Position Overview/Mandate paragraph - Maybe "Make an Impact with US:"? Actually we placed that under Responsibilities. So About the role will have first two paragraphs. Then after that we could also include the "About Fidus & Why Work Here" paragraph (the longer one). That is also about company. So we can append. Now Responsibilities: - Intro paragraph: "Make an Impact with US:" paragraph (the collaboration and examples) - Then bullet list from "What You’ll Be Doing:". We need to convert each bullet into
- . The bullet list includes many items each starting with a capital letter and ending with a period. We'll keep them as is.
Now Requirements:
- Bullet list from "Who You Are:" (mandatory). Each bullet is a sentence. We'll keep.
Now Skills:
- Bullet list from "Nice to Have:" (nice to have). Each bullet.
Now Benefits:
- Paragraph: "Our competitive compensation package also includes a comprehensive benefits package, including medical, dental, and vision plans, matching 401(k) contributions, annual profit-sharing bonus, along with other supplementary benefits."
We might also include any other benefits like "matching 401(k) contributions" etc. Already there.
Now we must ensure we don't repeat any content. Also ensure we don't include any boilerplate like "Automated tools (including AI) support our initial screening..." etc. Remove.
Now produce HTML fragment.
Let's craft.
First, About the role: