Skip to content

Careers · Ahmedabad · Not hiring right now

Software developer jobs in Ahmedabad: build real products, not just tickets.

QalbIT is a product-focused software company on S.G. Highway, Ahmedabad, building SaaS products, customer portals and mobile apps for clients in the USA, the Gulf and India. We are not hiring at the moment, and we have no open roles to apply for. Everything below is here so you can judge whether it is worth coming back when that changes.

There is no live vacancy and no application to make today. When a role opens it is posted on this page with a title, a team and a start date.

8+

Years shipping software

120+

Projects delivered

0

Open roles today

1

Office · Ahmedabad

Life & growth at QalbIT

Why developers in Ahmedabad build their careers at QalbIT.

Small, product-focused teams, modern stacks and direct impact on real products, not endless ticket factories. You see the full lifecycle of a product, not one isolated task.

  • Real product work, not slices of a giant system

    You work on full features, from API to UI, for SaaS platforms, marketplaces and internal tools, often talking directly with founders and product owners.

  • Modern stacks with room to grow

    Laravel, PHP, Node.js, React, Next.js, Flutter, Tailwind and cloud-native deployments, with guidance on architecture and trade-offs.

  • Strong fundamentals and mentoring

    We focus on clean code, Git discipline, reviews, debugging and communication. You ship, learn and improve with feedback, not just follow tickets.

  • Ahmedabad-based team with global clients

    Most roles are Ahmedabad / hybrid, working with clients in Europe, the Middle East and beyond, giving you exposure to international product work.

The QalbIT team at work in the Ahmedabad office, engineers at desks and two people talking over a screen in morning light.
The team, on a normal Tuesday

Open positions

We are not hiring right now. There is nothing to apply for.

No role is open, no interview is being scheduled, and no application sent today will be answered. This is the page that changes when that changes: a role appears here with a title, a team, an experience range and a start date.

Currently 0 open listings

Please do not send a profile today.

We are a small team and we hire a few times a year. Sending a CV while this page reads the way it does does not move you up any list, because there is no list being worked. It reaches an inbox nobody is screening.

  • Laravel developerLaravel · PHP · MySQL
  • PHP developerPHP · MySQL · REST APIs
  • Node.js developerNode · Nest · PostgreSQL
  • React frontend developerReact · Next.js · Tailwind
  • Flutter mobile developerFlutter · Dart · REST
  • QA engineerManual · automation · release checks

These are the roles we hire for when we are hiring, listed so you know whether this page is worth checking again. None of them is open today.

Benefits & how we work

Benefits and how we actually work.

We keep benefits simple: a stable environment, real product work, and enough structure for you to grow, balanced against a life outside the office.

  • Work you can be proud of

    • Real product and platform work, SaaS, booking systems, internal tools, used by customers in India, Europe and the Middle East.
    • End-to-end exposure: API, DB design, frontend, deployment, not just one layer.
    • Small, focused teams where your decisions and suggestions are visible and appreciated.

  • Learning & mentoring

    • Code reviews that explain the why, not just the what.
    • Opportunities to work across stacks, Laravel, PHP, Node.js, React, Next.js, Flutter, based on your interests and project needs.
    • Time to go deep on a problem instead of closing tickets by volume.

  • A calm environment

    • Predictable hours and no theatre around estimates.
    • Transparent discussions about roadmap, client expectations and how each project impacts the business.
    • A single office in Ahmedabad: no distributed-team coordination tax.

Life at QalbIT

A day in the life of a developer here.

A compact team, real products and a calm environment to do your best work. Every person has visible impact: we celebrate launches, share learnings and encourage people to experiment.

  • 01

    Start of day

    A short stand-up focused on blockers and priorities, not a long status meeting.

  • 02

    Deep work

    Blocks on actual product tasks: API, UI, refactors, debugging, tests.

  • 03

    Getting unstuck

    Ask early. Nobody is measured on suffering quietly through an edge case.

  • 04

    Reviews

    Feedback on the code, not the person: naming, trade-offs, and why one approach won.

A developer desk in the Ahmedabad office with two monitors, a notebook, a cup of chai and a lanyard, window light from the left.
A desk on S.G. Highway

How we hire

Our hiring process: four steps, no whiteboard puzzles.

You should know what happens after you press send. Four steps, usually inside two weeks, and you meet the founder before any offer.

  1. Send your profile

    A CV or LinkedIn, your GitHub or a project you are proud of, and two lines on the work you want to do. We read every one.

    Day 0

  2. A short intro call

    Twenty minutes with the person you would work with: what we build, what you have built, whether the role fits. No test yet.

    Within 2–4 days

  3. A practical conversation

    An hour on code you have written, or a small task on the stack you would use here. We talk through trade-offs; nobody writes on a whiteboard.

    Week 1

  4. Meet the founder, then the offer

    A conversation with Abid about the company and where it is going, then a written offer with the salary, the start date and who you report to.

    Week 2

The stack

The tech stack you would work in.

Standard, current and open. You will work across layers rather than inside one, and we will teach you the parts you have not touched yet.

  • Backend

    • Laravel and PHP 8, or Node.js with NestJS
    • PostgreSQL and MySQL, with Redis for queues and cache
    • REST and GraphQL APIs, documented and versioned

  • Frontend and mobile

    • React and Next.js with TypeScript and Tailwind CSS
    • Flutter for iOS and Android from one codebase
    • Accessibility and performance budgets on every screen

  • Delivery

    • GitHub, pull requests reviewed before merge
    • CI/CD with automated tests, staged releases on AWS
    • AI tooling for the application base; engineers write the product

What we look for

What we look for in a developer, whatever the stack.

The stack can be taught. These four are harder to teach, and they are what the intro call is really about.

  • 01

    Fundamentals

    You understand why the code works, not just that it does: data structures, HTTP, the database, the browser.

  • 02

    Ownership

    You take a feature from the conversation with the client to the release note, and you say when something is going wrong.

  • 03

    Clear communication

    You can explain a trade-off to a founder in plain words, in writing, and you ask early rather than guess quietly.

  • 04

    Curiosity with judgement

    You try new tools and you know when not to. A calm reaction to a bug in production counts for more than a long list of frameworks.

FAQs · software developer jobs at QalbIT

Frequently asked questions about software developer jobs at QalbIT

Roles, the stack, location, the interview process, freshers, notice periods and how growth actually works here.

Ask us directly →
The open positions band on this page is the live list and the only place we announce roles. When it says there are none, there are none: nothing is being interviewed for and no application is in progress. Each open role expands to its full description and the count in the hero moves when one opens or closes. We hire Laravel, PHP, Node.js, React, Next.js, Flutter and QA engineers, usually with one to three years of experience.
When a role is listed, use the form on this page or email hr@qalbit.com, and include your CV or LinkedIn, your GitHub or a project you are proud of, your current notice period, and two lines on the kind of work you want to do. Against an open role we reply within two to four working days. When nothing is listed there is no application to make: anything sent then is filed, not acknowledged, and is only read if a matching role opens.
Four steps, usually inside two weeks: a short intro call, a practical conversation about code you have written or a small task on our stack, a conversation with the founder, and a written offer. No whiteboard puzzles and no trick questions.
Most roles are onsite or hybrid at our office on S.G. Highway, Ahmedabad. We are a small team and the in-person overlap matters more to us than headcount, so fully remote roles are rare and say so in the listing.
Laravel and PHP 8 or Node.js with NestJS on the backend, PostgreSQL and MySQL, React and Next.js with TypeScript and Tailwind on the frontend, Flutter for mobile, and GitHub, CI/CD and AWS for delivery. Most engineers work across layers rather than inside one, and we teach the parts you have not touched.
Occasionally, when a role suits one and the fundamentals are strong. Most listings ask for one to three years because our teams are small and each person owns real features from the first month. A good GitHub counts for more than a certificate.
Standard full-time hours from the Ahmedabad office, with some overlap into US or Gulf client hours on particular projects, planned in advance. No late-night culture, no theatre around estimates, and a short stand-up rather than a long status meeting.
You can send a profile, but please be clear about what it does. With no role listed there is nothing to apply for: your profile is stored and read the next time a role opens, you will not receive a reply or an acknowledgement, and nobody will contact you unless an opening matches what you sent. That may be months away or it may not happen. Checking this page again is usually the better use of your time.
Yes. Most offers accommodate a thirty to sixty day notice period, and the start date is agreed in writing before you resign. Tell us your notice period in the first message so the timeline is honest from the start.
Both. We use AI tooling to lay the application base and to speed the tooling around it; our engineers write the product code, review every line and own the architecture. You will use the tools and you will still be the one who understands the system.

If you want to be on file

We will post roles on this page when they open.

There is nothing to apply for today. If you would still like us to hold your profile for the next opening, you can send it, but please read this first: it goes on file, we do not reply to it, and nobody will contact you unless a role opens that matches it. That may be months away, or not at all. If you would rather not wait on silence, check this page again instead.

Send a profile for the file