Skip to content
Deependra Vishwakarma

Where I work · United States

Senior engineering for US teams, with the East Coast morning in common.

Founders and CTOs who need senior engineering without a full-time hire: MVPs, AI features, performance work and rescuing apps built in a hurry.
Your week
Monday to Friday
Cities
New York, Chicago, San Francisco
Language
English
Currency
USD

Sound familiar?

  • You need a production-grade first version before your next raise, and hiring a senior engineer full time would take longer than building it.
  • An app built in a hurry, by an agency, a contractor or AI tools, is now slow, fragile or risky to change, and customers have noticed.
  • You want AI features that hold up in production, with evaluations and cost control, not a demo that works once.
  • Enterprise buyers send security questionnaires, and the number of state privacy laws keeps growing.

Working across the time difference

My evening block lines up with the East Coast morning, so a daily call at the start of your day works. With the West Coast the shared window is short, so we plan around it: written updates, recorded walkthroughs and one or two agreed call slots a week. US federal holidays are in my calendar.
When my day overlaps with the United States
MarketCityOverlap, local timeWork week
United StatesNew York EDTMon–Fri 09:00–14:29; Mon–Fri 14:30–18:00Mon–Fri
United StatesChicago CDTMon–Fri 09:00–13:29; Mon–Fri 13:30–18:00Mon–Fri
United StatesSan Francisco PDTMon–Fri 09:00–11:29; Mon–Fri 11:30–18:00Mon–Fri

Contracts and payment

Invoices in US dollars, monthly or per milestone, paid through Wise or Payoneer. I can work under your master services agreement and statements of work, with intellectual property assigned to you, and provide a W-8BEN.

  • 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.

The rules your product lives under

Engineering guidance, not legal advice: what these rules mean for how software is built, with the official source for each. Your lawyer decides what applies to you.
  • State privacy laws

    A growing number of states have comprehensive privacy laws, California's being the most developed, and California's regulators treat a browser's Global Privacy Control signal as a valid opt-out. The engineering: a map of personal data, consent and opt-out handling that honours those signals, retention rules, and deletion that really deletes.

    Source: California Attorney General: Global Privacy Control

  • SOC 2 and security questionnaires

    Not a law, but a condition of many enterprise deals. The evidence buyers ask for (access control, logging, change management, restore-tested backups) is easier to show when it is built in rather than added later.

    Source: AICPA: SOC 2, SOC for Service Organizations

Questions

Can you work US hours?

Partly, and by design: my evening block covers the East Coast morning every weekday. The hours we share go to decisions; the rest of the work runs on written updates you can read on your schedule.

Who owns the code?

You do. The code lives in your repositories and cloud accounts from the first day, and the agreement assigns the intellectual property to you.

How do we start?

With a small, fixed-price first step: an audit, an assessment or a scoping sprint that ends in a written outcome you can use whatever you decide next.

Working from the United States? Start with a brief.

Tell me about the problem. I’ll reply with the smallest useful first step, when I could start and how our hours line up.