You write to us
An email with something you have built and a paragraph on why this place. No cover letter formula. We read all of them and we reply either way.
Careers
Small team. Real products. Nowhere to hide.
We are a bootstrapped engineering company in Visakhapatnam. We started as StackZero in 2022, shipped four products of our own from 2024, and wrote the infrastructure layer underneath them. There are not many of us, which means the work you do is visible and the decisions you make are yours.
See open roles ↓
The work
Two kinds of week, and you will have both.
Our own products — LastClass, LenV, Fimyd and Lyka — are the reason the company exists. Client engineering is how we fund them. Everyone here does some of each, and we are honest that the balance shifts with what is on.
This suits people who want range and ownership more than they want a narrow, well-defined lane. It suits people who like knowing why the thing they are building exists. It does not suit people who want to work on one service for two years, and that is a legitimate thing to want elsewhere.
Our products
You own a piece of something we bet on
Marketplace matching, multi-tenant identity, media pipelines, workload placement, private model serving. The problems are real because our own products break when we get them wrong.
Client engineering
You talk to the people you build for
Small senior teams, direct contact, no account layer in between. You will sit in the room where the constraint is explained rather than receive it as a ticket.
What we look for
Evidence over credentials.
- Something you built that you can walk us through — a side project, a fix, a tool nobody asked for. Scrappy is fine. Unfinished is fine.
- The ability to say “I do not know” and then go and find out, which is most of this job.
- Curiosity that goes one layer below where you had to stop. Why is it slow? What is it actually doing?
- Writing that is clear. Half of engineering is explaining a decision to someone who was not there.
- A tolerance for ambiguity, because we frequently do not know the answer when we start.
We do not filter on degree, college tier or years of experience. We have hired people early in their careers who were plainly better than their résumé, and we would like to keep doing that.
Open roles
Where we need people right now.
01
↓02
↓03
↓04
↓
Product Engineer
Full-stack · VisakhapatnamBuild features end to end across our platforms — data model to interface — and stay with them once they are live.
Suits someone who has shipped and maintained something real, at any career stage.
Platform Engineer
Infrastructure · VisakhapatnamWork on Lyka: Kubernetes, workload placement, identity planes, artifact promotion, and the developer experience on top of it.
Suits someone comfortable in Kubernetes and infrastructure, whether or not it was your job title.
AI / Inference Engineer
Data & models · VisakhapatnamTake models from notebook to request path — retrieval, serving, memory-aware scheduling, evaluation and rollback.
Suits someone who has taken a model past the notebook.
Engineering Internship
6 months · VisakhapatnamPaid, with real ownership of a real component. Several of our engineers started here.
Suits students and recent graduates. No prior industry experience expected.
Nothing listed that fits you? Write anyway. We have created roles for people who were clearly worth having and we will do it again.
How hiring works
Four steps, roughly two weeks, no puzzles.
A conversation, not a screen
Forty minutes with an engineer about what you have worked on and what you found hard about it. We are trying to understand how you think, not to catch you out.
Real work, paid
A small scoped problem close to what we actually do. Take it home, take a few days. If it takes longer than we said, that is our estimate being wrong, not yours.
You meet the team and decide
You spend time with the people you would work beside, and you ask us the uncomfortable questions. Offer and compensation discussed openly, with the reasoning behind the number.
Apply
careers@stackinfinitygroup.com ↗
Show us something you made.
Send the role you are interested in, a link to something you built, and a paragraph about what was hard about it. That last part matters more than the rest.