A hundred and fifty-plus engineers, AI specialists, designers and consultants across four markets - with the rooms in Kochi, Bengaluru and New York. This is what a year with them actually looks like - how we hire, how we grow people, and the handful of afternoons a year when nobody gets much work done at all.
Live roles sit on LinkedIn ↗
Focaloid moved into World Trade Center Kochi in 2022 - this photograph was taken the morning the floor opened. Bengaluru and New York carry the client side, on a delivery model that assumes somebody on your call is a long way away.
Before the festivals and the group photos, the honest part: what you would actually be doing here. We run three service lines - AI, data and AI-native engineering - and AI leads, but a great deal of the work is the platform, the pipelines and the product underneath it. Four things are true of nearly every role.
Not prototypes that stop at the demo stage. The agents, the lakehouse, the pipelines, the product around them - whatever you build goes live inside banks, hospitals and global enterprises, and it stays yours after it does.
Thirteen years of product engineering came first, then the data platform work, and the AI practice was built on top of both. That means you learn the full stack, not just the model layer.
Our engineers sit in the room with client CTOs and Chief Data Officers from project week one. You learn how the decisions get made - which platform, which trade-off, what is worth building at all - not just how the thing gets built.
Most of the team sits together in Kochi; the clients are spread across India, the US, Singapore and Europe. Hybrid and remote working is available for most roles.
Almost every photograph on this page was taken on a phone by somebody who works here; the two from the move were shot on a proper camera. There is no culture calendar pinned to a wall - these are simply the frames that turned up in the camera roll.
Kerala’s harvest festival, and the one the Kochi floor has taken most seriously. One year, on the Thursday before Thiruvonam, a pookalam went down in loose petals on the World Trade Center lobby floor, in a dress code of mundus and kasavu sarees. Another year the whole thing moved out of town - a resort lawn, and a sadhya on banana leaves down two very long tables.
Rangoli on the table nearest the window, hand-painted diyas set out around it, paper lanterns strung off the ceiling grid, and enough gift hampers to fill a desk from end to end.
Santa hats went up in the third week of December and stayed on through standup. There was a tree, a box with the logo on it for everyone, and a group photograph in the driveway that took three attempts.
The most committed of the lot, by some distance. Skull make-up, an all-black dress code, and about forty people arranging themselves into a photograph that took considerably longer than the standup did.
Kerala took its football personally, and the office showed it. In the old room, shortly before the move to Infopark, national flags went up across the whole ceiling, people came in wearing the jersey of a country they had never visited, and the arguments stayed good-natured right up until Argentina played. The habit came with us: the other two frames here are from the new floor.
One of the two occasions Focaloid actually publishes about itself. That year it was canvas, acrylics and a long table. The finished pieces were laid out together afterwards, nine of them in a grid on one desk. One is called Hope.
Hill roads, quad bikes, paintball, and a bonfire somebody overbuilt. The useful part was never the activity. It was the two hours afterwards, when a principal engineer and a first-year hire ended up arguing about something with nothing to do with a sprint.
Focaloid moved into World Trade Center Kochi, and the whole company went downstairs to stand in front of Tower A for a photograph. A fortnight later the breakout area carried a backdrop reading Witness the Milestone with a ten inside a gold laurel - and then everybody went back upstairs.
Pick an occasion · arrow keys work too
Not the good day and not the launch day. The ordinary one, in the order it tends to happen.
Hybrid is real here, so a pod is usually part in the room and part at home. The room is where the whiteboard arguments happen.
Engineers, QA, design and the delivery lead in the same call. What moved, what is stuck, and who needs to be unblocked before lunch.
The tooling drafts, scaffolds and reviews alongside you. The judgement, the architecture and the accountability stay where they always were.
Nothing crosses a stage on its own recognisance. Code review, then the gate the engagement actually agreed to, then it moves.
Demos, decisions and the awkward questions. This is the hour that makes a distributed team feel like one team, so it is protected.
A few times a year the floor stops being an office for an afternoon - which is the section you have just scrolled past.
Every one of these was taken on a phone by somebody who works here.Hover to stop the wall.
Onam, the whole groupHalloween, committedDecember, at the desks
Offsite, everybodyDiwali, the breakout area
Onam, from the front rowJersey dayWomen's Day, painting
A gift, handed over
Offsite, halfway up
The floor, decoratedWorld Cup daySadhya, both tablesQuad bikesDiwali boxesHalloween, the castChristmas selfiePaintballHampers, stackedBonfire, after darkOnam, downstairsNine canvasesEvery company publishes values. These are ours, written as the thing you would actually notice in your first month rather than as adjectives.
Product-grade discipline across AI, data and engineering work: tests, security, observability, CI/CD, MLOps and LLMOps, because most programmes live or die in operations rather than in the lab.
The team that promises the outcome owns the outcome - from the first workshop through production rollout and whatever comes after it.
The field re-bases every few months. Learning is treated as part of the job rather than something you fit around it, and it is funded.
Colleagues in Kochi and Bengaluru, clients across the US, Singapore and Europe. Good written thinking travels further here than good meeting attendance.
A result belongs to everyone who moved it - the client, the pod, and the person who found the thing nobody else had spotted. Wins get attributed, not absorbed.
We grow together, or we don’t really grow. Every step forward here was moved by a team - so the success belongs to the people who moved it, and we share it that way.
Outside Tower A, a couple of hours after the new floor opened. It is the only kind of photograph that settles the argument about what a company is: not a logo, not a numbers band - this many people, who all showed up.
AI, data and engineering all re-base faster than any single career ladder can be rewritten, so the ladders here are drawn per specialisation rather than as one line from junior to senior.
Structured onboarding and dedicated mentorship for the first ninety days. The point is that by month four you are the one answering the question, not routing it.
Six defined ladders rather than one generic one, so depth counts as progression and you are not forced sideways into management to get promoted. Product, cloud, platform, QA, design and delivery careers run alongside them.
There is a Rewards & Recognition programme with two standing awards, announced on the company’s own feed rather than in a private email - and a payout that follows the same evidence the award does.
As an HR Head, one of the most rewarding compliments I hear isn’t about our technology or our projects - it’s about how our people feel. They value the transparency in our leadership, the opportunities to grow, the freedom to innovate, the positive work environment, and the incredible colleagues who make every challenge worthwhile. To me, that’s the true measure of a great workplace, and that’s what Focaloid Technologies strives to be every single day.
A few things we have already said publicly about working here.
Six numbers, all of them the same ones we give clients. There is no separate set for candidates.
Most of our hiring happens in Kochi, into one of these. They span all three of our service lines - AI, data and AI-native engineering - and every one of them ships into production. There is no research bench here.
Architecture, agentic AI, data and AI, governance and risk - and a financial controller. Three were posted publicly as at 30 July 2026; the live list always sits on LinkedIn.
No role that fits? Send us something anyway. Our own careers page keeps applications on file for current and future openings, the form takes about two minutes, and every submission is reviewed by our team - those three sentences are its words, not ours. Write to careers@focaloid.com or start at focaloid.com/career.
Most of our hiring is into Kochi, and the roles posted publicly right now are all Kochi-based. That said, hybrid and remote working is available for most roles, and there are teammates in Bengaluru, the US, Singapore and Europe. If you are strong and elsewhere, write anyway - say where you are in the first line.
We are not going to publish a fixed number of rounds, because it genuinely differs by discipline and level and a made-up pipeline would only mislead you. What we do publish is the front of it: the application form takes about two minutes, every submission is reviewed by our team, and applications are kept on file for current and future openings. Ask for the shape of the process in your first reply and someone will tell you what yours will be before you commit any evenings to it.
No. The work is production systems inside enterprises that have compliance departments - multi-agent orchestration, RAG, tool use, evaluation, guardrails and observability on the AI side, lakehouse and real-time pipelines on the data side, and the product and platform engineering that carries both. You will read papers. You will not be paid to write them, though conference and paper contributions are sponsored.
Two things, concretely. First, our engineers are in the room with client CTOs and Chief Data Officers from project week one - there is no account layer between you and the person who has to sign the decision off, which is a privilege and an exposure in equal measure. Second, there are six defined ladders across AI, data and MLOps rather than one generic one - with product, cloud, platform, design and delivery careers alongside them - so going deeper is a route to seniority and not a detour from it.
They have not been. The clearest example is one we have already told publicly: a colleague returned after an eight-year break and joined us as an HR Executive, and we published her story on our own Life page. We would rather read what you did with the time than pretend not to see it.
We do not publish them, and you should be suspicious of the numbers you will find on aggregator sites - some are crowd-sourced from a handful of respondents and some are recruiter-entered ranges, which is why they disagree with each other by a factor of three. What we publish is the principle: compensation is benchmarked to your market, alongside health insurance for you and your family, hybrid and remote options for most roles, an annual learning and certification stipend, paid time off, parental leave and wellness days, structured mentorship and a defined growth ladder, sponsorship for AI conferences, papers and open-source work, and internal AI guilds, hackathons and tech talks. Ask for the numbers on your role and level early in the conversation rather than at the end of it.
We will never ask a candidate for a payment, a deposit, a training fee, or bank or card details - at any stage, in any process, for any reason. If an approach involves a fee, an urgent transfer, or documents demanded before anybody has spoken to you, it is not us. Forward it to careers@focaloid.com and we will tell you whether it came from here. The roles we have posted publicly are on our LinkedIn jobs tab, which is worth checking against anything you have been sent.
Most of the team sits together in Kochi, and the work reaches clients across the US, Singapore and Europe - which is why the day here is built around overlap rather than handoff. These are the addresses we publish.
Not a cover letter. A repository, a system you kept alive, a model you took to production, a decision you argued for and lost. Two minutes on the form, or one honest email to the address below.
Where the company came from, who leads it, how it runs the work, how it secures it - and what it owes beyond the contract.