Location: Bangalore, India or Remote

Type: Full-time, on-site

ABOUT IXANA

Ixana is building breakthrough wireless communication technology for the next generation of wearable, edge, and physical AI systems. Our technology enables ultra-low-power, high-speed communication for applications across wearables, robotics, healthcare, industrial systems, defense, and human-machine interaction.

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.

ABOUT THE ROLE

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. Another major part will involve 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.

WHAT YOU’LL DO

1. STRATEGIC TECHNICAL PROPOSALS

Create proposals for Ixana partner companies
Track and evaluate relevant SBIRs, STTRs, RFIs, BAAs, government programs, defense opportunities, healthcare opportunities, industrial programs, and non-dilutive funding opportunities.
Read opportunity statements and assess whether Ixana has a credible technical and commercial fit.
Prepare concise bid/no-bid memos for leadership.
Convert Ixana’s technology roadmap into proposal concepts, abstracts, technical narratives, commercialization plans, work plans, and milestone descriptions.
Interview founders and engineers to extract technical facts, evidence, risks, assumptions, and success criteria.
Draft and refine responses to SBIRs, RFIs, BAAs, white paper requests, and strategic partner inquiries.
Red-team proposals before submission by identifying reviewer objections, unsupported claims, weak logic, and missing evidence.
Coordinate internal reviews, document versions, deadlines, and submission checklists.

2. TECHNICAL DOCUMENTATION

Own and maintain Ixana’s technical documentation library.
Write and update application notes, datasheets, manuals, integration guides, user guides, technical FAQs, and product explainers.
Translate engineering discussions, test results, design notes, and product behavior into clear documentation for customers, partners, and internal teams.
Ensure documents distinguish clearly between verified specifications, typical performance, planned features, assumptions, and limitations.
Work with engineers to validate technical claims, diagrams, instructions, tables, and usage guidance.
Maintain consistency in terminology, formatting, product descriptions, and technical claims across documents.
Build reusable templates for app notes, datasheets, manuals, proposals, white papers, and technical briefs.

3. LLM-ASSISTED WRITING AND REVIEW

Use LLM tools to accelerate research, outlining, drafting, rewriting, summarization, compliance checking, and red-team review.
Build repeatable AI-assisted workflows for proposal writing and technical documentation.
Verify AI-generated content against Ixana’s technical source of truth.
Avoid unsupported claims, vague language, hallucinated details, and generic filler.
Use AI tools to improve speed without compromising accuracy.

4. TECHNICAL NARRATIVE AND KNOWLEDGE MANAGEMENT

Build and maintain Ixana’s technical claims library.
Create reusable explanations of Ixana’s technology for different audiences: engineers, reviewers, customers, partners, and investors.
Maintain internal documentation on use cases, product capabilities, limitations, competitive differentiation, and common reviewer/customer questions.
Help ensure that proposals, datasheets, manuals, app notes, and customer-facing materials tell a consistent technical story.

WHO YOU ARE

You may be a strong fit if you:

Have a technical degree or equivalent technical fluency.
Write clearly, precisely, and logically.
Can learn unfamiliar technical domains quickly.
Are comfortable reading technical material and asking engineers clarifying questions.
Can separate what is proven from what is planned or speculative.
Have strong ownership and can drive documents from messy inputs to polished outputs.
Use LLM tools fluently, but do not blindly trust them.
Care about accuracy, structure, and clarity.
Can switch between persuasive proposal writing and precise product documentation.
Are willing to say, “This claim needs evidence,” “This opportunity is not a fit,” or “This document is not ready yet.”

PREFERRED BACKGROUND

Strong candidates may come from:

Engineering programs such as IITs, IISc, BITS, IIITs, top NITs, or equivalent institutions.
1–4 years of experience in technical writing, product documentation, technical proposals, deeptech startups, product/application engineering, consulting, product marketing, or technical strategy.
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.

WHAT THIS ROLE IS NOT

This is not a generic content-writing role.

This is not a grant-writing-only role.

This is not a marketing copywriting role.

This is not an administrative documentation role.

This is a technical communication role for someone who can understand complex technology, structure messy information, write clearly, use AI tools intelligently, and produce documents that Ixana can confidently send to customers, reviewers, partners, and agencies.

EXAMPLE PROJECTS

In your first few months, you may:

Evaluate whether an 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.