Multiple products. One small team. Noida.
Comhard Technologies has sold, installed and supported business software in India since 2001. Comsky is what we are building with that experience, and it is being built by a team small enough that you will know what every part of it does.
We should be honest about the shape of this before you read any further. Multiple products are being built at once on one control plane. Four of them — Cloud, CRM, TallyBridge and Backup — are live and have customers on them today. The other five are not shipping yet, and every page on this site says so rather than implying otherwise.
That is the job. It is not a large organisation with a narrow slot to fill. It is a short list of people who each own more surface than they would at a bigger company, working on products where the domain — GST, DLT, PF and ESI, Indian data residency — is not a detail somebody else handles.
If you want a defined brief, a long onboarding and a clear boundary around your responsibilities, this is the wrong place. If you would rather see something you wrote get used by a real business and then hear directly from that business about it, keep reading.
What working here actually looks like.
Not perks. The six things about this job that would show up in your first month.
You will own more than one thing
Multiple products share one identity system, one account hierarchy and one wallet. Work on a product and you end up in the control plane; work on the control plane and you end up in several products. Nobody here has a single file they are responsible for.
We publish what does not work
Comsky Cloud ships a written list of what it does not do. Product pages say “coming soon” where the thing is not built. You will be asked to describe your own work that plainly, which is harder than it sounds.
You will answer support
The person who built the feature answers the question about it. That is the arrangement we sell, so it is the arrangement engineers work under. It is also the fastest way to find out what you got wrong.
The office is in Noida
Our customers are Indian businesses and we answer them in IST. The working day is built around that rather than around another timezone’s meetings.
The rules are the product
GST worked out from the place of supply, DLT-compliant telephony, statutory payroll. A large part of the work is reading a rule carefully and turning it into code that does not need a warning label.
Real infrastructure, not just an app
Instances, volumes, snapshots and backup copies live in Indian data centres. Even if you write frontend, you are working on a product where somebody has to care about the machines.
Areas, not requisitions.
These are the parts of the work where an extra person would make an immediate difference. They are areas of the product, not job postings — see the note below.
Backend and platform
The control plane underneath everything: identity, the admin → distributor → reseller → customer hierarchy, metering, and tenant isolation that is enforced in the database rather than trusted to application code.
Frontend
Consoles that people use all day — a CRM pipeline, a backup job list, a monitoring wall. Dense interfaces where keyboard speed and honest empty states matter more than animation.
Mobile
Native iOS and Android for Comsky CRM are in internal testing rather than released, and TallyBridge exists mainly to put a business’s books on a phone. Mobile is not a companion app here.
Infrastructure and SRE
The compute, storage and networking that Comsky Cloud sells, and the pipelines that move encrypted backup copies. Provisioning, capacity, GPU hosts, and being the person who knows why it is slow.
Support engineering
The people who take a customer’s description of a problem and turn it into a reproduction, a fix or an honest answer. This is an engineering role with a phone attached, not a script.
Sales
Selling multiple products to Indian businesses and to partners who resell them. You would need to be comfortable saying which product does not do the thing being asked about, because that is how we sell.
There is no openings list. Write anyway.
We have not published formal requisitions, and we would rather say that than post a page of roles we have not defined. If one of the areas above is yours, send an email and we will tell you honestly whether there is something to talk about.
Say which area
Name the area from above, or describe your own if none of them fit. A mail that works for any company gets a slower reply than one that says which part of this one you want.
- ·One area is enough — you do not need to fit all six
- ·Tell us if you would rather do something we have not listed
Show one thing you built
A repository, a shipped product, a written post-mortem of something that went wrong. One real artefact tells us more than a page of adjectives.
- ·Links are fine; attachments are fine
- ·Work you cannot share — just describe what it did
Pick a product and argue with it
Open Cloud, CRM, TallyBridge or Backup, use the parts that are live, and tell us what you would change. Disagreeing with us in the first email is not a risk here.
- ·The four live products are open to look at
- ·The other five are not built yet — do not review those
Send it to careers@comsky.ai
One address, read by the people you would be working with. No form, no account to create, no tracking number to quote back at us.
- ·Include a phone number if you would rather talk than type
- ·We reply with a no rather than not replying
What people ask before writing.
Do you have open positions right now?
There is no formal openings list on this page, and we are not going to invent one. The areas above are where an additional person would matter. Write to careers@comsky.ai describing which one is yours and we will tell you whether there is a conversation to have.
My area is not on the list. Should I still write?
Yes, if you can say what you would work on and why it belongs in a suite of business products. Design, technical writing, quality and finance are all real work here even though they are not listed as areas we are actively looking at.
Where would I be based?
The office is in Noida, and support is answered in IST because our customers are Indian businesses. Ask about working arrangements in your mail — we would rather answer your actual question than publish a policy we have not settled.
What is the interview like?
We have not standardised it into stages with names. It starts with a conversation about what you have built, and we will tell you what the remaining steps are in our first reply rather than leaving you to guess.
Can I see the product before I apply?
Yes, and we would prefer it. Comsky Cloud, CRM, TallyBridge and Backup are live — open them, read the product pages, and come with an opinion. Books, HRMS, Telephony, Chat and Monitor are still being built, so there is nothing to try there yet.
Is Comsky the same company as Comhard?
Comsky is the suite built by Comhard Technologies, which has been in Noida since 2001. The name on the products is new; the company behind them is not.
One email, read by the people who build it.
No openings list, no applicant portal. Tell us which part of the suite you want to work on.