03:40 IST. Meera has been on console for five hours, and the pass she has been waiting for is three minutes out.
The control room is quiet the way only a control room is quiet at night. Every screen lit, nobody speaking. Somewhere over the Indian Ocean a spacecraft she has never touched with her hands is climbing toward the horizon on schedule. When it comes into view she will have about six minutes, and not a second more, to confirm it is healthy and bring the night's work safely to the ground.
03:43. Acquisition of signal. The link locks and telemetry pours in. Health nominal. Power positive. The onboard recorder is nearly full from imaging passes earlier in the orbit.
03:44. Playback begins. The radar data the spacecraft captured earlier, over the Arabian Sea, starts streaming down to the ground station. Meera cannot see the imagery itself, only the telemetry around it: the downlink holding lock, the link margin steady, the recorder emptying. A contact this short is no place to lose lock. For the next several minutes, every second is either data on the ground or data lost for good.
03:51. With the recorder draining clean, she uplinks the next block of tasking, the targets the spacecraft will image once it is back over open water and out of her reach.
03:54. Loss of signal. The satellite drops below the horizon. The pass is over. Meera logs it, updates the handover notes, and waits for the next one.
She will not learn until much later that somewhere in the data take she just brought down was visible a trawler, dark inside waters it had no licence to fish. It had been captured on an earlier pass over an empty stretch of sea, transponder switched off, certain no one was watching.
Meera never saw the boat. She never saw the ocean. She did not point the radar, and she will not analyse the image or flag the vessel. But that image is worth nothing if it never reaches the ground, and tonight, bringing it down clean was her job. Someone has to be awake, keeping the spacecraft healthy and the data flowing, while the machine watches the sea.
That someone is the spacecraft controller. It is one of the most important seats in the building, and one of the least understood.
Tough and Competent
In 1967, after a fire killed three astronauts on the launch pad, flight director Gene Kranz stood in front of Mission Control and gave his people two words to live by. Tough and competent. He told them to write the words on their blackboards and never erase them. He returned to that moment years later in his memoir, Failure Is Not an Option, and those two words have outlasted almost everything else about the era for a reason.
Tough meant being forever accountable for what you do or fail to do. You never blame the procedure, the tool, or the shift before you. Competent meant never taking anything for granted, never assuming a green reading is fine just because it usually is. Strip away the decades and that is still the entire job description at the console.
India has its own proof of what those words look like, and the strongest version is not a story of getting it right the first time. In September 2019, the Chandrayaan-2 lander, Vikram, descended toward the Moon's far southern highlands, the high-latitude ground we loosely call the south polar region. The first braking phase went to plan; in the second, the lander shed speed faster than its design allowed, slipped outside the limits it was built to handle, and hard-landed near its target. The orbiter survived and works to this day, but the lander was lost in the final two kilometres. ISRO did not call it bad luck. Re-flying the whole mission was a steep cost to justify, so they went again leaner, no new orbiter and roughly two-thirds the budget, and rebuilt the lander around the assumption that things would go wrong rather than right: a wider landing zone, more fuel, more solar panels, and software meant to hold together even if sensors failed. ISRO's chairman, S. Somanath, called it a failure-based design, the discipline of asking what can fail and guarding against every answer. On 23 August 2023, Vikram landed, the farthest south any craft had ever touched the Moon, and made India the fourth country to land softly on it at all. Tough enough to own the failure in the open, competent enough to engineer the comeback.
Why a Radar Satellite, and Why It Matters Here
Most Earth-observation satellites see with light - clouds blind them and night switches them off. A Synthetic Aperture Radar satellite carries its own illumination and reads the sea by how the signal comes back. Through monsoon clouds. Through total darkness. A radar is the instrument you reach for when the thing you are watching does not want to be seen.
India learned the value of that the hard way. After the 2008 Mumbai attacks arrived by sea, the country accelerated a radar satellite, RISAT-2, into orbit specifically to close a coastal blind spot. Watching our own waters stopped being a nice-to-have.
The physics is elegant. On radar, a calm patch of the sea reads dark and a rough patch reads bright. An oil spill flattens the water and shows up as a dark smear on a brighter sea. A steel hull lights up. And a hull that lights up where the transponder feed insists there is nothing at all is the whole game.
One downlink can carry a great deal off the same six minutes of ocean. An oil slick drifting toward a coastline, caught early. A foreign trawler poaching inside Indian waters, stealing from fishermen who do follow the rules. Two vessels meeting in open water with no port logic, the signature of a transfer meant to launder a catch. A boat running dark for reasons nobody wants to imagine. A pirate skiff closing on a merchant crew in lanes India has long helped keep safe.
It is all the same data. One pass can defend a fisherman’s income, a sailor’s life, a coastline, and a clean sea at the same time, whether the reason is security or livelihoods or a cleaner ocean.
There is one line the job does not cross. Radar shows a hull, not a verdict. The satellite produces an anomaly, the analyst produces the judgment, and the controller makes sure the picture exists at all. The honest and frankly more impressive truth is that none of those outcomes happen unless the spacecraft was healthy, pointed right, and downlinked on time. That part is yours.
A Small Team, On Purpose
Here is the part that sounds like a catch, but is actually the whole appeal. This team starts with two or three members, and even when the constellation grows past thirty satellites, it will never exceed about eight.
That is by design, not understaffing. A handful of people flying a whole fleet is only possible if the system has been taught to fly itself, and teaching it is the work. This is already how the best operators run. In fact, some companies fly their missions with no dedicated operations team at all, because their teams are builders who automated the console away.
The mechanism is simple, and it is yours to drive. A controller resolves an anomaly by hand at three in the morning. Then, in daylight, that same controller writes the procedure, and then the script, that lets the machine handle it alone the next time. Every manual save becomes a permanent reflex of the constellation. Your reach multiplies with each satellite added, instead of your team multiplying to keep up.
Pure console hours are, in a sense, temporary by design. You are not. Those hours are how you earn the judgment the automation is built from. Pioneers, not caretakers.
You Do Not Have to Arrive Knowing This
Mission control was never built only with aerospace graduates. Gene Kranz was a fighter pilot. The teams that put India on the Moon and around Mars were famously young and mixed, and they learned the craft on the job because there was no other way to learn it.
This role is written the same way. An aerospace degree is welcome. So is a background in the armed forces, in radar, in air defence, in UAV operations, in communications, in any environment where you learned to stay disciplined while real consequences moved in real time. If you trained for aerospace and made it, good. If you did not get into aerospace but you have the temperament, the console does not know the difference and does not care.
What it cares about is whether you are tough, competent, and willing to learn fast. The console is a school, not a ceiling.
The Parts We Will Not Pretend Away
Now the hard parts.
This is shift work in a round-the-clock environment. Nights, weekends, holidays, and rotating shifts that run long during critical phases. The sea does not keep office hours and neither do our satellites. The control centre also sits where the mission needs it, a secure facility built for round-the-clock operations, and that is not always at the centre of a city.
Operating a company’s first satellite is intense. The procedures are still settling, the spacecraft is still revealing its personality, and the early phases ask a great deal from a small team. There will be hard nights. We would rather say that plainly than have you discover it in month two.
None of this is sacrifice in the way a soldier sacrifices, and we will not pretend otherwise. It is the ordinary, freely chosen cost of building something early. Time away from home, late nights, a quieter postcode. But it is worth being clear about what those nights are for. Today India still leans on others for a great deal of what it sees over its own waters. The people who take these seats now are laying the foundation for India to watch its own waters with its own eyes, on its own terms, and to depend a little less on anyone else to do it. That is a civilian job, done at a console, and it is still worth a few hard nights.
The Question
The job description for this role ends on a line worth repeating. We value people who are motivated by reliable execution rather than glamour.
That is the whole job in seven words. At 03:40 there is no glamour. There is a lit screen, a healthy spacecraft, six minutes of downlink, and one person making sure the picture comes down at all. Tough. Competent. Awake.
So the question is not whether the work is exciting. Some nights it is, most nights it is steady, and a few nights it is the most alert you will ever be. The question is whether you want to be one of the few the whole chain depends on while the coast is asleep and the satellite is not, and whether you want to spend the next few years turning that watch into something that can hold a fleet.
If the answer is yes, it does not much matter where you started. It matters that you are tough, competent, and ready to learn the rest on console.
We are not hiring a shift. We are hiring the few who will fly the first satellite and teach the next thirty to fly themselves. The console is where you start.