Full Stack Engineer

Three engineers, joining a team of five that owns everything this company runs on. No senior-free team — two senior engineers are already here. No QA function — you test what you ship.
THE DATES THAT CANNOT MOVE:
In-person interview: 20–30 November 2026, at our Bengaluru office. It cannot be done online.
Applications close: 15 November 2026. We may close early once the positions are filled.
Joining date: 1 December 2026. Non-negotiable.
You must be free of notice period obligations by 1 December. If you are serving a 60 or 90-day notice, the timing will not work and we cannot make an exception.
Please read this advertisement to the end before you apply. It is long on purpose — it tells you exactly what the job is, what it is not, and what we will not budge on.
WHO WE ARE:
Jane Aerospace is a Bengaluru-based aerospace and drone supply chain company. We source aircraft parts, drone components and industrial materials for operators, MROs and manufacturers, and we are building Supply Chain as a Service — a subscription model in which we take over a client’s procurement function entirely.
We run three companies across India, Hong Kong and the UAE. We are bootstrapped, no outside funding and none being sought, and people here own real things early.
THE ROLE:
We are hiring three full-stack engineers to join our in-house engineering team. There are two senior engineers here already. The three of you would make it a team of five, and between you that team is responsible for everything this company runs on.
The main build is the SCaaS platform — the software the subscription business runs on, and the system our clients use. Broadly it covers the client-facing side where a customer raises a requirement and watches it move; the sourcing side where suppliers are matched, quotes compared and decisions recorded; and the operations side underneath — fulfilment, documentation, landed cost, and the integrations that keep everything in step.
Alongside it sit our hiring and assessment platform and our marketing tooling, both already running, and whatever we decide to build next. Five people, several products.
Which part you own is decided after you join, not before. We are not allocating modules at offer stage — we would be guessing, and we would probably guess wrong. The first few weeks are how we find out where each of you is strongest. Apply as a full-stack engineer, not as a specialist in one corner; all three of you are assessed the same way.
One thing we want to be honest about. Five engineers carrying three platforms is a broad surface for a small team. You will context-switch more than you would at a larger company, you will work outside whatever you consider your specialism, and some weeks the priority will change under you.
There is also no QA function. You test what you ship. Code review is real — our two senior engineers and your peers review everything, nobody merges their own work including the founder, and AI-assisted architecture and security review runs as a formal gate — but nobody downstream is going to catch a bug you did not look for.
What you get in exchange is unusual at this level: two seniors to learn from, real ownership of a production system from the first month, and your work in front of paying clients. If the work grows faster than five people can carry, we expect to hire again around March.
WHAT YOU WILL ACTUALLY DO:
Build and ship to production, weekly. We would rather see something working on Friday than something perfect next month.
Own your part of the platform — its architecture, uptime, backups, security, and the decisions about where it goes next.
Test your own work. There is no QA function here and we are not pretending otherwise.
Review code and have yours reviewed, by the senior engineers and by your peers.
Integrate substantial third-party APIs, primarily the Zoho suite, and LLM APIs for the AI tooling we run internally.
Demo working software to the Managing Director every Friday. Thirty minutes, running software, not a status update.
Write things down — standards, decisions and runbooks — so the next person is not reverse-engineering your head.
WHAT YOU GET PAID:
Rs 40,000 to Rs 45,000 per month CTC (Rs 4.8–5.4 lakh per annum), depending on experience and on what you can demonstrate you have built. CTC means cost to company; your in-hand figure will be lower after statutory deductions, and we will show you the exact breakdown at offer stage.
Compensation reviewed formally at six and twelve months, against evidence. We would rather pay well to keep someone who has become valuable than re-hire and start again.
A laptop, the tools you need including AI tooling, and a learning budget.
PF and ESI as per statute.
We will be straight with you: this is not the top of the Bengaluru market, and if your only measure is the number on the offer, you will do better elsewhere. What is unusual here is the ownership and the proximity. At one to three years you would be responsible for a production system that a paying business depends on, working directly with two senior engineers and the founder, with your work in front of clients. That is rare, and it compounds faster than a salary does.
WHO WE ARE LOOKING FOR:
MANDATORY — something you have actually shipped, that we can look at: a GitHub profile with real commits, or a live URL. An application without it will not be reviewed.
You can read code you did not write and work out what is wrong with it. With five engineers across several products, you will spend real time in code that is not yours.
1 to 3 years building and shipping web applications. This is not a fresher role.
One modern JavaScript or TypeScript front-end framework, to a working professional standard.
A back end in Python or Node, and the ability to design a sensible relational database schema.
Experience integrating a REST API from a large third-party platform — Zoho, Salesforce, HubSpot, a payment gateway, anything substantial.
You have deployed something yourself and kept it running. Not just pushed to a branch.
Git discipline, and the ability to explain your own code clearly to someone else. We will ask you to.
Nice to have, not required -
LLM and AI API integration — prompt design, output handling, evaluating what comes back. The Zoho ecosystem: Deluge, Creator, Catalyst. Authentication, access control and handling sensitive data properly. Having been the first or only engineer somewhere.
PLEASE DO NOT APPLY IF:
We mean this sincerely — it saves everyone time.
You cannot attend an in-person interview in Bengaluru between 20 and 30 November 2026.
You cannot join on 1 December 2026, for any reason, including notice period.
You are not in Bengaluru and are not willing to relocate here at your own arrangement before joining. We do not pay relocation costs or a joining bonus.
You are looking for a work-from-home or hybrid role. This is fully work from office.
Your experience is entirely in notebooks or coursework and you have never shipped a product users touched.
You have never deployed anything or owned anything in production.
You want a backlog handed to you each morning. You will be given problems, not tickets.
You want to work on one product, or only on research and prototyping. Everything you build here is meant to be used.
You cannot explain code you wrote six months ago.
OUR HIRING PROCESS:
Four rounds. We have deliberately kept the unpaid work small.
Application — short questions and your GitHub or live project link. The link is mandatory.
Technical test — timed, online, around 60 minutes. Finding and explaining bugs in code you did not write, plus written reasoning about how you would structure a system.
Video interview — recorded, online. You explain your own answers from the technical test.
In-person with the Managing Director — at our Bengaluru office, 20–30 November. Includes walking us through code you have written — bring it, and expect to be asked why, repeatedly.
On AI: use it. We do, you will be building with LLM APIs here, and an engineer who refuses the tools is not who we are looking for in 2026. What we test instead is whether you understand what you produced. The technical test asks you to find bugs in code you did not write, which no assistant can do for you without you understanding the code. Rounds three and four ask you to account for your own work. Code you cannot explain is worth nothing to us.
All online rounds complete by 19 November. We make offers on a rolling basis — if you are strong, you will hear from us quickly.
HOW TO APPLY:
Apply through the link on this posting and answer the application questions in full. Attach your CV, your GitHub or live project

Skills
Python, JavaScript, TypeScript, LLM

Experience
1-3 yrs

Work arrangement
No