Tech Intern ( Full Stack Product Engineer)

Tech Intern

Winvesta

• Mumbai / Surat / Remote
• 3–4 months

About Winvesta

Winvesta is an AI-native fintech on a mission to make cross-border payments and international investing seamless and affordable for Indians. We build two live products: a Global Currency Account for Indian exporters receiving payments from foreign clients, and an international investing platform for Indian retail investors. Founded by Swastik Nigam (IIM-A, ex-Deutsche Bank London), Winvesta has been recognised as Fintech Product of the Year 2024, Best Payment Solution 2023, Best Emerging Fintech 2023, and FinTech Company of the Year 2020 for Asia Pacific.

The Reality of the Market

The economy looks functional on paper. Companies are hiring. Campuses are placing students. And yet if you talk honestly to engineers two or three years into their careers right now, something is shifting underneath the surface. Roles that looked technical are becoming coordination jobs. Skills that took years to acquire are being compressed by tools that did not exist when the syllabus was written. The engineering programmes at even the best colleges were designed for a world that is changing faster than the curriculum can track.

The question worth asking before you take your first role is not "which company has the best brand?" It is: "will I emerge from this with capabilities that compound — or will I emerge with experience that is already becoming obsolete?"

That is not a comfortable question. It is the right one.

What Winvesta Offers

You will work on production systems, not sandbox projects. The code you write will affect real transactions for real clients.

You will use Claude — specifically Claude — as a daily work partner. Not in training, not in demos. In actual engineering work: debugging, writing scripts, building pipelines, generating first drafts of solutions that you then vet, correct, and ship. By the time you leave, you will have built a compounding capability that most engineers your age are still figuring out how to develop.

You will work directly with the founding team and understand why decisions get made, not just what they are.

The last month of your internship is an explicit adjudication period for a full-time offer. You will know this from Day 1. Both sides deserve that clarity.

What You Get

• Competitive stipend, disclosed at offer stage
• Direct daily access to the founding team — not a manager two levels removed
• Real work on live fintech products from week one, not internal exercises
• Structured Claude onboarding in your first week, with AI-native skill development throughout
• Formal full-time assessment in the final month, with a clear and honest outcome either way

The Attitude We Need

We look for raw intelligence first. The kind that shows up in board exam results — ideally 90% or above in both 10th and 12th — and in the way someone approaches a problem they have never seen before. These grades are not a credentialing exercise. They are one of the most consistent early signals of the underlying capacity we need: the ability to hold complexity in your head, reason through it systematically, and arrive at a correct answer without being walked there.

We also look for strong mathematical ability. Not just comfort with numbers — the ability to think quantitatively about problems that are not obviously quantitative. To model a system, spot where the logic breaks, and work back to why. Engineering at the infrastructure level of a fintech requires this constantly: in data pipeline design, in reconciliation logic, in debugging problems where the error is three layers removed from where it surfaces.

Beyond that, we need someone who treats Claude Code the way a serious engineer treats any powerful tool — uses it aggressively, knows its failure modes, and never ships something they have not thought about themselves. Claude is fast, capable, and reliably wrong about something in every non-trivial task. Your job is to find the something.

One thing we insist on before a single line of code is written: understand why. What is the business problem? What does the product need to do? What does the user experience look like, and what does a good outcome mean? An engineer who codes without that context produces technically correct work that solves the wrong problem. We do not want that. We want engineers who ask the right questions first, then build with speed and precision.

We also need someone who moves without being asked. Who flags a problem before it becomes someone else's emergency. Who is genuinely excited about building in an AI-native environment — not intimidated by the pace of change, but energised by it.

If you are the right person for this role, the bar we have described will feel like a reasonable expectation, not an obstacle.

The Role

This is a product engineering role. You will be building, shipping, and iterating on real features and systems — not writing documentation, not reviewing PRs from the sidelines. The measure of output here is simple: code committed to GitHub, every day, multiple times a day. That cadence is not a target to aim for — it is the standard we hold every engineer to, and it is the clearest signal of whether someone is actually building or just thinking about building.

Before every piece of work, you are expected to understand the business context behind it — the product reasoning, the user need, the commercial logic. Why is this being built? What problem does it solve? What does good look like when it ships? That understanding is not optional, and it does not slow you down — it is what makes the code you write worth committing.

We actively track commit frequency, code quality, and shipping speed as part of how we assess technical interns. Not as a surveillance exercise — as a genuine indicator of compounding. The engineer who ships clean, purposeful code multiple times a day, every day, is the one who grows fastest.

• Build product features and integrations across our two live fintech products — because shipping working code that real users interact with is the only measure of engineering output that matters
• Write and improve data pipelines and reconciliation systems — because in a payments and brokerage business, the data has to be right, and the person who ensures that creates real value
• Build internal automations and tooling using Claude — because a small, fast-moving team needs to eliminate manual work wherever possible, and the engineer who does that well multiplies everyone's output
• Debug and resolve production issues — because at our scale, problems do not wait for a sprint cycle, and the engineer who can move fast through a live issue is genuinely valuable
• Understand the product and business context for every task before writing a line of code — because technically correct work that solves the wrong problem is not an asset, it is a liability

The specific work will change week to week. The expectation — understand it, build it, ship it — will not.

Proof of Work

We are not looking for a polished CV. We are looking for evidence of things you have actually built and shipped.

If you have a GitHub with real projects — not just coursework — link it. If you have used Claude Code on a real task, tell us what you built, what it produced, and what you had to correct. If you have built a tool, a script, an automation, or anything that someone else used or that solved a real problem — show us. Tell us what happened after you built it.

Proof of work does not have to be impressive by conventional standards. It has to be real, and you have to be able to tell us what you did with the output.

Qualifications

What we require:

• Based in Mumbai or Surat preferred — in-office when possible; remote also works
• Active Claude user — must have used it to produce real work outputs before applying, not just tried it
• Experience with Claude Code on at least one real task, with a specific error caught and corrected
• Currently enrolled in or recently graduated from an engineering programme

What We Prefer

• 90% or above in both 10th and 12th
• IIT or Tier 1 engineering college
• GitHub profile with self-initiated projects
• Familiarity with backend development, APIs, or data pipelines

Logistics

Duration: 3–4 months minimum Work schedule: Monday to Friday, full-time Location: If you are based in Mumbai or Surat, we prefer you come into the office. Remote works too — we care about the output, not the postcode. Stipend: Competitive — disclosed at offer stage

To apply: Use the portal where you found this listing. In your application, include links to any proof of work — GitHub, project demos, scripts, or Claude-produced outputs you acted on. If your work is not publicly shareable, describe it specifically in your application answers. Please do not reach out to team members directly.

If you are shortlisted, you will hear from us. We keep a close eye on responses and move quickly on candidates we want to speak to. Due to the volume of applications we receive, we are not always able to provide individual feedback to those not selected — we regret that, and we mean it.

Winvesta

• BKC, Mumbai
• Fintech Product of the Year 2024
• Best Payment Solution 2023
• Best Emerging Fintech 2023
• FinTech Company of the Year 2020, Asia Pacific

Note: This is a paid internship.Skills: team spirit,communication skills,project management,client engagement,market research,research and analysis,proactivity,content creation,tech-savvy,communication,collaboration,team player,analytical skills,hubspot,cross-functional collaboration,proactive attitude,notion,data analysis