Careers in AI and IT services
Careers for engineers who build and run what they ship.
We hire engineers across India to build AI, software, data and cloud systems for companies in the US, UK, Canada, Europe, Australia and India, and to run those systems once they are live. Every role is remote, and the work sample is paid.
- Where
- Remote, anywhere in India
- Clients
- In the US, UK, Canada, Europe, Australia and India
- Hiring
- AI, full-stack, platform and data engineers
Engineering recordA few of the systems our engineers have built and run in production.
- 40,500requests a minute at peak, on a consumer backend
- 10,000players in live games at once, on a real-time backend
- −90%support tickets after an AI assistant went live
- 100+critical vulnerabilities found and fixed in our own systems
Open roles
Four roles, all remote in India.
We hire for these all year. If you do strong work that does not fit a title below, write to us anyway.
AI Engineer
You will build AI agents and LLM features for our clients and run them in production, inside the client's own systems. Getting a demo to work is the easy part. Most of the job comes after it, in deciding how to evaluate the system, getting retrieval to bring back the right documents, adding guardrails, and keeping its behavior steady as the volume grows.
We would like to see an LLM system that real users depended on, and to hear how you knew it was working. You should write good Python and be comfortable in TypeScript.
- Python
- TypeScript
- LangGraph
- MCP
- Postgres with pgvector
- OpenTelemetry
Full-Stack Engineer
You will own a product from the Postgres schema and the API to the screens people use, and you will talk directly with the people who use it. More of these products now have AI inside the workflow, so you will work closely with our AI engineers.
Show us production web applications you built. We work mostly in TypeScript, React and Node, and we value engineers who can explain a trade-off to someone who is not technical.
- TypeScript
- React
- Next.js
- Node.js
- PostgreSQL
- Redis
Platform Engineer
You will build the infrastructure our clients' systems run on, always in the client's own cloud account. That covers Terraform, delivery pipelines, Kubernetes when it is worth the complexity, and monitoring that warns us before a customer notices anything. Every change goes through a reviewed pull request, and you are on call for the systems you build.
You have run Terraform in production and you have an opinion on when Kubernetes is the wrong choice. You care about cost as much as uptime, and you stay calm in an incident.
- Terraform
- Kubernetes
- Argo CD
- GitHub Actions
- AWS
- Azure
- Google Cloud
Data Engineer
You will build the pipelines and models that get a client's data ready for analytics and AI. A lot of the work is making numbers trustworthy. That means agreeing contracts with the teams that own the source systems, testing every model, and being able to trace a figure on a dashboard back to the rows it came from.
We want to see pipelines you have run in production. Strong SQL matters more than any single tool, though we use dbt most often. It helps if you have ever had to reconcile one number across two systems that disagreed.
- SQL
- dbt
- Airflow
- Dagster
- Snowflake
- BigQuery
- Kafka
How we hire
How hiring works, from note to decision.
Four steps, usually about two weeks in all. These are the times we hold ourselves to.
- 01 · Your note5business days
You hear back from us within five business days, whether the answer is yes or no.
- 02 · A call45minutes
A conversation with the people you would work with, about something you have built. There are no coding puzzles.
- 03 · Work samplePaidrate agreed before you start
A small task similar to client work, done in your own time on a practice repository. We pay for it whatever we decide.
- 04 · Decision7days
Within a week of the work sample you get a yes or a no, with our reasons in writing.
Write to us
Tell us about something you built, and why it was hard.
Attach a CV and a cover letter if you like. A few paragraphs about your work and a link are enough on their own.
15 answers, on the recordQuestions before you apply.
The work
Are DigyAi's engineering roles remote?
Yes. Every engineering role is remote, for people who live in India. You can work from anywhere in the country.
Who are the clients, and what will I work on?
Companies in the US, UK, Canada, Europe, Australia and India. The work runs from AI agents and LLM applications to web platforms, data pipelines and cloud infrastructure, and you stay with a system after it goes live.
What hours do engineers work?
It depends on the client. Each engagement agrees a few hours a day that overlap with the client's working day, and you know them before the work starts. An engineer on a US client keeps a different day from one on an Indian client.
Will I be on call?
Yes, for the systems you build. The rota always includes at least one other engineer who knows the system, and runbooks are written before anything goes live. When something breaks, we write a postmortem and fix the cause in the code.
Do engineers use AI coding tools?
Yes, every day. AI agents write a lot of first drafts of code, tests and documentation. The engineer who merges a change is responsible for every line of it, and a second engineer reviews it.
Hiring
How long does DigyAi's hiring process take?
Usually about two weeks from your note to a decision. We reply to your note within five business days, the call follows soon after, and you hear our decision within a week of finishing the work sample.
What is the paid work sample?
A small task similar to real client work. You do it in your own time on a practice repository, never on client code. We agree the rate before you start and pay it whatever we decide.
Can I use AI in the work sample?
Yes, the way you would at work. Afterwards you walk one of our engineers through what you built, including the parts an AI wrote and why you kept them. On the call itself we just want to hear how you think.
Do I need a CV, a cover letter or a degree?
No. If you have a CV or a cover letter, attach it to the form and we will read it. If you do not, a note about something you built and what was hard about it is enough. We decide on the work you show us and on the work sample, and we do not ask about degrees.
Do you hire engineers early in their careers?
Yes, if you have built something real, whether in a job, in open source or on your own. Send us the most serious thing you have built and tell us what you learned from it.
Do you share the pay range?
Yes. We tell you the range for the role on the first call, before any assessment, and we do not ask what you earn today.
What if my role is not listed?
Write to us anyway. We hire all year by open application, and an engineer who has built and run real systems is worth talking to whatever the title.
Trust
How do I know a message is really from DigyAi?
We only write from addresses ending in @digyai.com, and we never ask for money, a deposit or bank details at any stage. If a message asks for any of those, it did not come from us. Please forward it to contact@digyai.com.
What happens to my application?
We use it only to consider you for a role at DigyAi. If you would like it deleted, tell us and we will delete it.
Why do you check identity before an offer?
Our engineers work on systems that businesses depend on, so our clients need to know exactly who is working on them. Before any offer we meet you on a video call and check your identity.
Not answered here? Two lines are enough.
Ask your own question