You control your workflow
Flexible hours, a hybrid schedule or fully remote — whichever lets you do the work. We measure output, not the hours you were visible.
Software · AI · IoT engineering
Careers
We are a small company doing work that ships. That means you own something real early, you get reviewed honestly, and there is nowhere to hide — which is either exactly what you want or exactly what you don't.
Open roles
We are looking for backend developers to join a small squad working on a real-time client platform. You will own services end to end — schema, API, deployment and the pager — with review and support rather than supervision.
You will build interfaces that stay fast on a mid-range Android phone and usable with a keyboard. We care about Core Web Vitals and WCAG the way other teams care about pixel alignment, and you will have room to push back on designs that will not hold up.
You will be the person who asks the question nobody wants asked before a release. The role is half automation engineering and half genuine curiosity about how things break.
You will run hiring for a growing engineering team and manage internship cohorts that now run every month. The job is part recruiting, part operations, and entirely about people having a good experience whether or not we hire them.
There is no open designer seat this quarter, but design work is growing and we keep strong portfolios on file. Send yours and we will reply — including when the honest answer is "not yet".
No seat open at the moment. We do hire analysts regularly as client analytics work grows, and we keep applications on file for three months.
Nothing that fits? Email hackedinsolutions@gmail.com with what you do and what you are looking for. We keep good CVs on file for three months and we do come back to them.
Why choose HackedIn
Flexible hours, a hybrid schedule or fully remote — whichever lets you do the work. We measure output, not the hours you were visible.
Small teams mean nobody sits on the bench. You will own something real in your first month, with support rather than supervision.
Courses, conferences and certifications are paid for. We also run internal sessions where people teach what they just figured out.
Code review here is specific and direct. That is uncomfortable for a fortnight and then it is the reason you get better.
Levels and expectations are written down. You always know what the next step requires rather than guessing.
Things we build go live and stay live. Nobody here has spent a year on something that was quietly cancelled.
How we hire
We would rather you did well. Here is the whole process and what actually helps at each stage.
A short note about what you have built matters more than a cover letter template. Our HR team replies to every application — including the ones we turn down.
Tip. If you attach anything you are proud of — a repo, a project, a write-up — your chances of reaching an interview rise sharply.
Thirty minutes with someone from the team about what you have done and what you want to do next. Ask us things; we would rather you interviewed us back.
Tip. Look at the role again and bring two questions. It tells us more about you than any answer would.
We do not ask for definitions. We want to see how you think about a real problem, ideally one close to what the job involves.
Tip. A worked example from your own experience beats a textbook answer every time.
By now we understand your level. This round is about fit, the work you would be given, and your questions about how we actually operate.
Tip. Relax and be yourself. We value honesty and open-mindedness more than a polished performance.
We prepare an offer, discuss it properly, and set a start date. No exploding deadlines, no pressure to sign before you have thought about it.
Tip. Welcome to the team.
How we operate
If a deadline is not realistic, or a feature is not worth building, you hear it in week one — not in the retrospective. Bad news does not improve with age.
Code, infrastructure, domains, accounts and documentation are yours from the first commit. No proprietary layer you have to keep paying us to maintain.
Every two weeks there is a URL you can open. Progress you cannot click on is not progress we will claim.
Every project leaves your team more capable. Every internship leaves an engineer more employable. It is why a services company runs a training programme at all.
Three or four people who own a thing completely, rather than a dozen who each own a slice and none of the outcome.
Proven tools for the load-bearing parts, new ones where the upside is real. Nobody should be debugging our curiosity at 2am.
Applications
Even speculative applications. If there is nothing open we will tell you what we expect to open and when, rather than leaving you refreshing a careers page.
hackedinsolutions@gmail.com · Bengaluru, Vijayawada and remote