Build infrastructure software that tells the truth
Aevora Systems builds software for infrastructure that cannot fail quietly. We were founded by people who develop and operate hydropower, which is why AEON treats a chiller and a branch router as the same kind of problem — and why it will not change anything on a running plant without a rule, an approval and a record. We are in Srinagar by choice, building for organisations that cannot hand their infrastructure to someone else's cloud.
What it is like here
Small team, real responsibility
Nobody is handed a ticket queue. You will own a part of the product, decide how it should behave, and defend that decision. The first pilots are being arranged now, so what you build this year is what a customer sees first.
Honesty is the engineering standard
AEON reports what it cannot determine rather than filling the gap with a plausible number, and we hold our own work to the same rule. Saying "I do not know yet" is expected; a confident guess is not.
Built in Kashmir, for anywhere
We are in Srinagar by choice, building software for customers who cannot send their infrastructure data to someone else's cloud. Good engineering does not require leaving home.
Open roles
If none of these is quite you but the work is, write anyway — the third paragraph of a good email has started more than one role here.
Deployment and field engineer
You take AEON into a customer's data centre and make it read their equipment: switches, servers, UPS, cooling plant and building systems. The first week of any pilot is capture work — walking a device's management interface, comparing a reading against the panel on the front of the unit, and writing the profile that makes it right. It is careful, physical, unglamorous work and it decides whether the product is trusted.
- Comfortable in a data hall and on a plant room floor
- Networking fundamentals: SNMP, switching, addressing
- Enough Python or YAML to write a device profile and read a packet capture
- The patience to check a number against the equipment rather than assume it
Platform engineer
AEON is Go collectors and a Python control plane on PostgreSQL. You would work across both: protocol implementations that must behave when a device lies, and a control plane where every action passes a governance gate and is written to a tamper-evident record.
- Go or Python to a professional standard, and willingness to work in the other
- SQL that you write rather than generate, and an interest in why a query is slow
- Tests written because the failure matters, not because a policy says so
- A protocol specification does not frighten you
Frontend engineer
The console is React and TypeScript, and it has to make a 10,000-device estate legible to someone at two in the morning who has been woken up. Clarity under pressure is the design constraint, not decoration.
- React and TypeScript in production
- An eye for information density: tables, topology, time series
- Accessibility treated as part of the work rather than an afterthought
- Interest in visualising physical infrastructure, not only dashboards
Engineering internship
For a final-year or recently graduated engineer who wants to work on real infrastructure software rather than a tutorial project. You would own something small and real — a device profile family, a report, a piece of the console — with review and without being left alone with it.
- Enough programming to read an unfamiliar codebase and ask good questions
- Curiosity about how networks, power and cooling actually work
- Willingness to be corrected, often
Apply
Tell us about something you have built or fixed, and what you found hard about it. A CV is useful; that paragraph is more useful. We reply to everyone who writes a real message.
Prefer email? Write to careers@aevorasystems.com Open your email app