Full-Stack Engineer

READ THIS FIRST — 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 interview on a rolling basis and may close early once the position is filled.
  
• All online rounds complete by: 19 November 2026.
  
• Joining date: 1 December 2026. Non-negotiable.
  

You must be free of notice period obligations by 1 December. If you are currently serving a 60 or 90-day notice, the timing will not work and we cannot make an exception. Please do not apply — it saves us both the time.

Please read this advertisement all the way to the end before you apply. It is long on purpose. It tells you exactly what the job is, what it is not, how we assess you and what we will not budge on. Applications from people who clearly have not read it are easy to spot, and we do not take them forward.

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 — imported and locally procured — and we are building Supply Chain as a Service, a subscription model in which we take over a client's procurement function entirely.

We operate three companies: Jane Aerospace Pvt Ltd in India, Jane Tech Labs Ltd in Hong Kong, and Jane Aero Tech Supply Chain FZCO in the UAE.

We are bootstrapped. No outside funding, and none being sought. We are small, we move quickly, and people here own real things early.

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. You would own a part of it with a named backup on someone else's.

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 actually strongest, and the allocation follows that. What this means for you: apply as a full-stack engineer, not as a specialist in one corner. All three of you are assessed the same way, on the same things.

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 on things 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 here — 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 before anything goes in — 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 rather than buried in an internal backlog. If the work grows faster than five people can carry, we expect to hire again around March.

• 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 two senior engineers and by your peers. Nobody merges their own work here, including the founder.
  
• 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.
  

• It is not a job with a backlog handed to you each morning. You will be given problems, not tickets.
  
• It is not research or prototyping. Everything you build is meant to be used.
  
• It is not one product. Five engineers cover the SCaaS platform, the hiring platform, the marketing tooling and whatever comes next.
  
• It is not a specialist role. You are hired as a full-stack engineer and allocated afterwards.
  

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.
  

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 to be told exactly what to build, in detail, every day.
  
• You cannot explain code you wrote six months ago.
  

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 months and at 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.

Four rounds. We have deliberately kept the unpaid work small.

1. Application — short questions and your GitHub or live project link. The link is mandatory.
   
2. 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.
   
3. Video interview — recorded, online. You explain your own answers from the technical test.
   
4. 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 — READ THIS PROPERLY. Use it. We do, you will be building with LLM APIs here, and an engineer who refuses to use 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. Round three asks you to explain your own answers. Round four asks you to walk through your own work in front of someone who will keep asking why.

Code you cannot explain is worth nothing to us. That is the whole of our position, and it is the same standard we hold ourselves to in review.

All online rounds complete by 19 November. In-person interviews run 20–30 November. We make offers on a rolling basis — if you are strong, you will hear from us quickly.

One last time: if you have skipped to this section, go back and read the rest. The answers to most of what you are about to be asked are above.

Apply through the link on this posting and answer the application questions in full. Attach your CV, your GitHub or live project link, and a short covering note in your own words. We read the notes, and the ones with a real voice get read twice.