[Hiring] Strategic Technical Proposals Associate @Ixana

Role Description

We are looking for a technically fluent writer and structured thinker who can help turn Ixana’s technology into clear, credible, high-quality written artifacts: RFQs, proposals, RFIs, SBIR/STTR submissions, app notes, datasheets, manuals, technical briefs, and customer-facing documentation.

This is not a generic content-writing role. You will work closely with Ixana’s founders, engineers, product leads, and business teams to understand the technology, extract the right technical details, and produce documents that are accurate, persuasive, and useful.

A large part of the role will involve:

• Strategic technical proposals: SBIRs, STTRs, RFIs, BAAs, government opportunities, white papers, and non-dilutive funding submissions.
• Product and technical documentation: application notes, datasheets, manuals, integration guides, FAQs, technical explainers, and customer-facing product collateral.

You should be comfortable using LLM tools to accelerate research, outlining, drafting, editing, and review. But the final quality bar is human: technical accuracy, judgment, clarity, and taste.

Qualifications

• Technical degree or equivalent technical fluency.
• Ability to write clearly, precisely, and logically.
• Capability to learn unfamiliar technical domains quickly.
• Comfort in reading technical material and asking engineers clarifying questions.
• Strong ownership and ability to drive documents from messy inputs to polished outputs.
• Fluency with LLM tools, but do not blindly trust them.
• Care about accuracy, structure, and clarity.
• Ability to switch between persuasive proposal writing and precise product documentation.
• Willingness to assert the need for evidence or readiness of documents.

Requirements

• 1–4 years of experience in technical writing, product documentation, technical proposals, deeptech startups, product/application engineering, consulting, product marketing, or technical strategy.
• Experience in fields such as electronics, electrical engineering, mechanical engineering, computer science, robotics, biomedical engineering, aerospace, embedded systems, semiconductors, wireless, IoT, medical devices, or industrial systems.
• Prior SBIR/STTR, RFI, BAA, or other government proposal experience is helpful but not required.
• Prior technical documentation experience is helpful but not required if you have excellent writing, strong technical curiosity, and high attention to detail.

Benefits

• Opportunity to work on breakthrough wireless communication technology.
• Collaborate with founders, engineers, and business teams.
• Engage in strategic technical proposals and documentation.

Example Projects

• Evaluate whether a grant topic is a strong fit for Ixana.
• Draft a one-page concept note for a defense, healthcare, robotics, or wearable systems opportunity.
• Turn an engineer’s notes into an application note for a customer integration.
• Create a datasheet template for an Ixana module or development kit.
• Write a user guide for a demo system or evaluation kit.
• Build a claims library that tracks Ixana’s verified specifications, typical performance, use cases, and limitations.
• Use LLM tools to draft and red-team a proposal, then verify all technical claims with engineers.
• Standardize terminology across Ixana proposals, app notes, manuals, and technical collateral.

Skills We Value

• Technical curiosity
• Structured thinking
• Excellent written English
• Precision
• Strong editing judgment
• High ownership
• Comfort with ambiguity
• Ability to work with engineers
• LLM fluency
• Deadline discipline
• Taste for what is credible, clear, and useful

Interview Exercise

As part of the process, candidates may complete a practical exercise. You may receive a short non-confidential Ixana technical brief and a sample opportunity or product scenario. You may be asked to prepare:

• A bid/no-bid recommendation for a sample technical opportunity.
• A one-page proposal concept.
• A short application note or technical explainer.
• A list of claims that require engineering validation.
• A red-team critique of what is unclear, unsupported, or not ready.

We care less about prior exposure to specific acronyms and more about how you think, write, verify, and improve technical material.