Software Engineer I - Product / Full-Stack

Location: Jayanagar, Bengaluru — in office

Type: Full-time

Experience: 0–1 years; strong fresh graduates and builders are welcome

Compensation: the posted range is fixed pay; ESOPs come over and above.

Kulfi is where couples in India spend time together, even when they can't be in the same place.

About 100 million unmarried Indian couples don't get to be together most nights. Different cities, different homes, parents around. A phone is all they have. So they join a class just to be near each other, or stay on a one-way call, or watch a movie over video. They do all this for love, and nothing was built for them.

We are building that. Kulfi is a digital experiences app for couples, and close to a million people already use it. We did not get here by spending. Daily users grew 4x in 30 days this summer. We added 100,000 users in the first 20 days of August without paying for a single ad. 80% of all play happens between 9pm and midnight. That is bedtime, and we own it. We are backed by South Park Commons and by founders and CEOs from Swiggy, Mosaic Wellness, Snitch and Moonshot.

Next is an AI personalization engine for games. Every couple gets a new game every day, made for them on the spot from what they like. Our team already ships a new game in about two days. No couple should run out of things to do together.

India has more couples than any other country. We want every one of them on Kulfi.

We are a small, high-intensity team. Your work will reach real users quickly, and you will be expected to notice what is broken—not wait for someone else to notice it for you.

You will build product features end to end across our Flutter app, web surfaces, backend APIs, and data. We do not need you to know every part on day one. We need evidence that you learn quickly, finish what you start, care about the user experience, and understand the code you ship.

• Build and ship small product features across app/web, API, and data layers.

• Turn product/design intent into complete user flows, including loading, empty, error, and retry states.

• Debug issues across client, network, backend, and data—not stop at the first layer.

• Write tests, review your own diff, and verify behavior before handoff.

• Read user feedback and product metrics to understand whether a release worked.

• Use AI coding tools to move faster while remaining responsible for every line you ship.

• Ask precise questions, communicate blockers early, and learn from direct feedback.

• You have built and shipped at least one real software project, internship deliverable, freelance product, or meaningful open-source contribution.

• You can write readable code and reason through bugs without blindly relying on autocomplete or AI.

• You have worked across at least two layers: mobile/web, backend/API, database, or deployment.

• You care about product details and notice when a technically correct feature creates a bad user experience.

• You move quickly, but you test your work and own mistakes.

• You can explain your contribution, trade-offs, and what you would improve next.

• You are comfortable working in person in Jayanagar, Bengaluru. A computer-science degree is not required. Evidence of building matters more than credentials.

• Flutter/Dart and mobile fundamentals.

• State management such as BLoC or Riverpod.

• REST APIs, SQL, caching, queues, or real-time systems.

• Experience with Node.js, Go, Python, Java, or another production backend language.

• CI/CD, cloud deployment, monitoring, or app-store releases.

• Thoughtful use of Claude Code, Codex, or similar tools.

Within three months, you can own a scoped feature from problem statement to release, handle the obvious failure states, write useful tests, review your own work, and explain what user signal or metric should improve.

1. Short application review based on shipped work.

2. 15–20 minute screening call.

3. 75-minute practical product-engineering interview combining a project deep dive, live task, self-review, changed requirement, and product/UX discussion.

4. 30-minute founder and mutual-expectations conversation.

We allow AI tools during the practical exercise. You must disclose how you used them and be able to explain and defend the final code.

Please answer the application questions yourself. Clear and specific beats polished and generic.