deependra.in

Local time in MUMBAI · UTC+5:30 ·

Services · 05 lines · 22 services

Five ways I can help.

I'm Deependra Vishwakarma, a senior software engineer based in Mumbai. I design, build, scale and secure web platforms and AI features for teams in the United States, the United Kingdom, the European Union, the UAE, Saudi Arabia, Japan and South Korea, and I plan my working day around theirs.

01

Which line fits your problem

Start from the sentence that sounds like your week.

  1. I need a first version of my product.

    Start withMVP SprintBuild · Week 1: scope

  2. My pages are slow and I don't know why.

    Start withPerformance and Core Web Vitals auditScale · Day 1: access and baselines

  3. I want an AI feature that holds up on real data.

    Start withAI features in your productAI · Scoping sprint (one week)

  4. A security questionnaire or audit is coming.

    Start withSecurity audit and penetration testSecure · Scope

  5. Google and AI assistants don't find or cite our site.

    Start withSEO, AIO and GEO: AI search visibilityScale · Crawl and measure

  6. I need an independent view before we invest, acquire or rebuild.

    Start withArchitecture review and due diligenceLead · Agree the questions

Something else? See all 22 services

02

Everything I do, at a glance

22 services in five lines. Each name opens its page.

Secure

Services: 02

Find the holes before someone else does, and make the code do what the policy promises.

Lead

Services: 01

Senior technical judgment, in writing, before you commit.

The work falls into five lines. Each one is a different kind of problem, but they share a way of working: one senior engineer who owns the result, a small fixed-price first step with a written outcome, code in your repository from the first day, and a written update every week. I've been building for clients since 2018, most recently as the senior engineer behind a media group's products, where I ran 15+ production servers across Google Cloud and AWS. If you're not sure which line fits, the first step of any of them will tell you.

03

Proof, in case studies

04

Further reading

05

Where I work

The markets page shows our shared hours, contract terms and the data-protection rules I design for in each market.

Engagements

How engagements work

Start small, then grow the engagement only if it's working.

A fixed-price first step
A small, bounded piece of work with a written outcome: an audit, an assessment or a scoping sprint. You see how I work before committing to more.
A fixed-scope project
Scope, timeline and price agreed in writing, with working software to review every week.
A monthly retainer
A set number of days each month for ongoing development, maintenance or performance work.

Always

  • Intellectual property is assigned to you on payment.
  • An NDA before we discuss details, if you'd like one.
  • A written update every week, and a demo whenever there's something to see.
  • Working hours that overlap yours.

Process

From first message to handover

  1. A conversation

    A short call or a written brief: what you need, by when, and what success looks like.

  2. A small first step

    A fixed-price audit, assessment or scoping sprint with a written outcome. It's useful on its own, whatever you decide next.

  3. Scope in writing

    Deliverables, timeline, price and what's out of scope, agreed before the build starts.

  4. Build in the open

    Working software on a staging URL, weekly updates and demos, and priorities you can change as we learn.

  5. Handover or keep going

    Documentation, a runbook and a handover session, then a retainer if you want ongoing help.