We Don't Read CVs.
We Read Code.
We're looking for a communication architect who can translate complex AI systems into an organic presence across platforms. No CVs. No cover letters. Only a real challenge — and what you build from it.
The role
AION Analytics builds market-intelligence and execution-integrity infrastructure for Indian financial markets. The technical work is solid — calibrated probability bands, macro-event classification across 32 NSE sectors, open-source calendar infrastructure used by developers across India. The gap is communication: very few people outside the field know this work exists, and even fewer can explain it clearly.
We need someone who can sit with the actual code and models, understand what they do and why they matter, and then produce content that makes a developer, a trader, or a curious founder say: "I didn't know this was possible."
This is not a social media management role. It is a thinking role that sometimes outputs social media.
The application IS the challenge
There is no form to fill before you do the work. The challenge below is the application. Do it well and submit what you built. That is the only CV we read.
Part 1 — Understand the product (required)
Start by reading AION's live public work. Not our marketing copy — the actual technical artifacts:
Read the model card. Read the package README. Look at what the code actually does. Understand the problem it solves and the gap it fills (why does this exist when pandas_market_calendars already exists? what does the intelligence model do that a generic sentiment API can't?).
Then write a single content piece — a blog post, a LinkedIn thread, or a short video script — that explains one AION product to a non-technical audience: Indian traders, developers, or curious founders. Treat the format as your choice, not a constraint.
- Target length: under ~500 words for written formats, or a tight script for video.
- Audience: someone who has never heard of AION Analytics.
- Goal: they finish reading and understand what the product does, why it exists, and why it might matter to them.
Part 2 — Platform strategy (optional, high signal)
Design a 30-day awareness plan for one AION product across the following platforms — treated as an interconnected system, not a posting checklist:
One piece of original technical content should generate multiple platform-native outputs. A deep README change on GitLab becomes a developer thread on X becomes a practitioner post on LinkedIn. Show how you'd build that repurposing loop — and how you'd automate the distribution layer once the content pattern is proven.
The plan can be a short document, a structured list, or a simple diagram. The thinking matters more than the format.
What we're actually testing
We will tell you exactly what we weight. Transparency about evaluation criteria is part of how AION works.
| Criterion | What it tells us | Weight |
|---|---|---|
| Technical understanding | Did you read the code and actually understand what the product does? Did you get the taxonomy right — not the marketing copy, the actual mechanism? | Highest |
| Strategic thinking | Can you see distribution as a system — one input producing multiple outputs across platforms — rather than a list of tasks? | High |
| Communication clarity | Can a non-technical reader finish your piece and understand something genuinely technical? No jargon laundering — actual clarity. | High |
| Builder signal | Did you suggest how to automate or scale your own work? This is not required — it is a strong positive signal if present. | Bonus |
Submit your work
Use the form below, or email your submission directly to [email protected] with subject line Communication Architect — [your name]. Attach your piece as a PDF or paste it inline. Include a link if it is published somewhere.
If you're wondering why there's no "Apply Now" button — this is the application.
A generic cover letter is an instant pass. A thoughtful piece of work is an invitation to a conversation. We read every submission that demonstrates genuine engagement with the technical material. We don't read the ones that don't.
About the work environment
AION Analytics is a small, independent firm. The founder is active in the work — not a logo above a team. This means the feedback loop is short, the scope is real (not a training exercise), and the output matters from day one.
The role is remote. Compensation is output-based. The first engagement is a paid trial based on the challenge submission — if the work is strong, the conversation continues from there.