Senior Systems Engineer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We have content for About the role (maybe "About The Job" is similar). Responsibilities present. Requirements present. Qualifications? Not explicitly but "Required ABOUT YOU" could be qualifications. Skills? Could be part of required. Benefits present. Pay present. Schedule not present. So we should include sections: About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Qualifications? The "Required ABOUT YOU" includes qualifications like B.S., 5+ years, etc. Could map to Qualifications. But we need to decide. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Qualifications if there is content. There is "Required ABOUT YOU" which lists qualifications. So we can include Qualifications. Skills maybe not separate; could be part of Requirements. We'll not create Skills if no explicit list.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO etc. There's a paragraph about research on women & underrepresented minorities; that's boilerplate? It's about encouraging applications; could be considered EEO/equal-opportunity boilerplate. Should remove. Also remove "At RADAR, your base pay is one part..." but we need to keep pay info. Actually that paragraph includes pay range and benefits. We'll keep pay and benefits but remove the encouraging statement.
We need to preserve all substantive information. So we need to include the description about the company, mission, values? The "About Us" section is substantive; but we are not told to include a section for About Us. The allowed headings list does not include About Us. However we could incorporate that content into About the role? Possibly we could treat "About The Job" as About the role. The "About Us" could be omitted? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't forbid other headings not in list, but says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections. It doesn't say we cannot have other headings, but better to stick to those. The "About Us" could be considered part of About the role? Might be okay to include as a
under About the role heading. Thus structure:
About the role
... combine About Us and About The Job paragraphs.
Responsibilities
- ... each responsibility bullet.
Requirements
- ... required items (B.S., 5+ years, ability to assess, problem solving, entrepreneurial spirit, leadership skills, diving into details, experience writing system requirements, etc.)
Qualifications
Maybe we could combine with Requirements? But we have separate. Could put qualifications like B.S., 5+ years, etc. But those are already in Requirements. Might be redundant. Better to treat Requirements as the list of required qualifications/experience. Qualifications could be empty; we should not create empty section. So we skip Qualifications.Benefits
- equity, comprehensive medical and dental coverage, life and disability benefits, 401k plan, flexible time off, paid parental leave
Pay
The expected base salary range for this position is $165,000 - $200,000. Individual pay is determined by work location and additional factors, including job-related skills, experience and relevant education or training.
We should also include maybe "What You'll Do" as part of About the role or Responsibilities? It's about first 30/60/90 days; could be included under About the role as additional description. We'll incorporate into About the role paragraph. We must not include the encouraging statement about women & underrepresented minorities. Remove that. Also remove any duplicated lines. Now craft HTML. We need to ensure we preserve all substantive information: include details about RADAR's mission, technology, deployment, funding, values, etc. Let's extract. About Us paragraph: "E-commerce got real-time data infrastructure decades ago. Physical stores still have not. RADAR is changing that. RADAR is building the data infrastructure layer for the physical world, starting with retail. Our hardware-enabled SaaS platform uses proprietary overhead sensors, software, and AI-powered analytics to locate every product in a store, continuously, down to the fixture. We are deployed across 1,500+ stores with retailers including American Eagle Outfitters and Old Navy, processing tens of billions of real-world events every day, delivering 99%+ accuracy in complex, noisy environments - at fleet scale. RADAR is one of the best-funded companies in retail technology, backed by a recent Series B financing at a $1 billion valuation. Inventory accuracy is only the beginning. We believe RADAR can become foundational infrastructure for the physical economy, powering new AI-driven commerce experiences across retail and beyond. Join us if you want to work on a large, unsolved, technically challenging problem with an ambitious team building category-defining technology." Values list: Mission-Driven, Collaborative Team, High Impact, Clear Communication, Balanced Lives, Diverse Perspectives, Empathy-Driven Design. About The Job: "Radar is hiring a Senior Systems Engineer with end-to-end ownership of system-level inventory features. You will lead the problem solving process, analyze test data, write requirements and coordinate releases to ensure high quality for all customer deliveries. You will form relationships with the whole cross-functional team and bring clarity and efficiency to drive the group forward. You will own end-to-end testing for your feature and oversee your feature through design, implementation, testing, debug and customer release." Responsibilities list: End-to-end Ownership, System Analysis, Requirements, Validation, Triage and Debug, Leadership, Release Planning. Each with description. Required ABOUT YOU: list of bullet points: B.S. in Engineering or any equivalent technical discipline; 5+ years of experience working on integrated hardware, firmware and software sensors or products; unique ability to assess complex technical and organizational situations and bring clarity to the team; strong problem solving skills including proficiency with data analysis, for example with Python and SQL; entrepreneurial spirit with a general attitude to "figure it out" when faced with a difficult or ambiguous problem; can identify gaps, take initiative and drive the team to execute; strong leadership skills - you can translate between engineering disciplines and align stakeholders with different technical backgrounds or opinions; enjoy diving into the details of a problem and also understanding high level context; experience writing system requirements, test plans, or feature specs that guide cross-functional engineering team implementation. Preferred: Experience working on RF systems; Experience writing and automating test scripts for integrated hardware/software products. What You'll Do: first 30 days, 60 days, 90 days details. Pay and Benefits paragraph. We need to include all that. We'll put About the role paragraph containing About Us, Values, About The Job, What You'll Do (maybe summarised). But we must not invent or summarize away detail; we need to preserve ALL substantive information. Summarizing may lose detail. Better to keep as separate paragraphs under About the role heading, preserving the original text. We can include multipleelements. Thus:
About the role
E-commerce got real-time data infrastructure decades ago. Physical stores still have not. RADAR is changing that. RADAR is building the data infrastructure layer for the physical world, starting with retail. Our hardware-enabled SaaS platform uses proprietary overhead sensors, software, and AI-powered analytics to locate every product in a store, continuously, down to the fixture. We are deployed across 1,500+ stores with retailers including American Eagle Outfitters and Old Navy, processing tens of billions of real-world events every day, delivering 99%+ accuracy in complex, noisy environments - at fleet scale. RADAR is one of the best-funded companies in retail technology, backed by a recent Series B financing at a $1 billion valuation. Inventory accuracy is only the beginning. We believe RADAR can become foundational infrastructure for the physical economy, powering new AI-driven commerce experiences across retail and beyond. Join us if you want to work on a large, unsolved, technically challenging problem with an ambitious team building category-defining technology.
OUR VALUES Mission-Driven: We're transforming retail with cutting-edge technology and building something that truly matters.Collaborative Team: We thrive on curiosity, shared goals, and solving complex problems together.High Impact: You’ll make meaningful contributions from day one and help shape the future of our product and company.Clear Communication: We value honesty, humility, and respectful dialogue—everyone’s voice matters.Balanced Lives: We work hard, but not at the expense of well-being. We respect time, boundaries, and life outside of work.Diverse Perspectives: We believe better ideas come from diverse backgrounds, experiences, and viewpoints.Empathy-Driven Design: We build with deep respect for our end users, listening closely to their feedback and needs.
About The Job Radar is hiring a Senior Systems Engineer with end-to-end ownership of system-level inventory features. You will lead the problem solving process, analyze test data, write requirements and coordinate releases to ensure high quality for all customer deliveries. You will form relationships with the whole cross-functional team and bring clarity and efficiency to drive the group forward. You will own end-to-end testing for your feature and oversee your feature through design, implementation, testing, debug and customer release.
What You'll Do In your first 30 days, you will: Learn Radar’s mission, technology stack and core values.Complete onboarding and security compliance training.Familiarize yourself with Radar’s system architecture, especially as it relates to your key feature(s) In Your First 60 Days, You Will Dive into the current status of the feature to understand where the gaps or potential failure modes exist.Create a plan mapping out all required work and identifying key blockers for success. Develop relationships with key contributors and stakeholders for the scoped work Familiarize yourself with Radar’s tools and testing capabilities - understand existing test setups and data infrastructure, with capabilities to analyze relevant data as needed. In Your First 90 Days, You Will Understand the full scope of your assigned feature, with a plan for maintaining high quality through the upcoming release cycleLead a standing weekly cross-functional feature meeting where feature design, implementation, and test are planned and reviewedCreate a set of requirements to outline the key performance required for your feature. Complete hands-on data analysis to characterize the performance of your feature and compare against the stated requirements.
That preserves details. Now Responsibilities: we need to list each responsibility with its description. We'll create- ...