# A senior software engineer for US teams, with the East Coast morning in common.

> A senior software engineer for US startups and product teams, working remotely from Mumbai so that the East Coast morning falls inside my evening. It is for founders and CTOs who need senior engineering without a full-time hire: MVPs, AI features, performance work and rescuing apps built in a hurry.

- Page: https://deependra.in/markets/united-states
- Type: Market: United States
- Last updated: 2026-11-02
- Author: [Deependra Vishwakarma](https://deependra.in/about), senior software engineer in Mumbai

## Key facts

- Cities: New York, Chicago, San Francisco
- Work week: Monday to Friday
- Invoices: USD
- Language: English

## What teams in the United States bring me

1. You need a production-grade first version before your next raise, and hiring a senior engineer full time would take longer than building it.
2. 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.
3. You want AI features that hold up in production, with evaluations and cost control, not a demo that works once.
4. Enterprise buyers send security questionnaires, and the number of state privacy laws keeps growing.

## Working with teams in New York, Chicago and San Francisco

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.

Each city's 09:00–18:00 working day on the clock in Mumbai (UTC+5:30), in January and in July, so daylight saving is accounted for.

| City | In January | In July |
| --- | --- | --- |
| New York (UTC−5 / UTC−4) | 19:30–04:30 (next day) | 18:30–03:30 (next day) |
| Chicago (UTC−6 / UTC−5) | 20:30–05:30 (next day) | 19:30–04:30 (next day) |
| San Francisco (UTC−8 / UTC−7) | 22:30–07:30 (next day) | 21:30–06:30 (next day) |

## City pages for the United States

- [New York](https://deependra.in/markets/united-states/new-york) (New York, USA): A senior software engineer working remotely from Mumbai for New York teams, with the start of your day inside my evening. It is for founders and product leads, often in fintech and media, who need a first version, AI features or a second opinion on rushed code.
- [San Francisco](https://deependra.in/markets/united-states/san-francisco) (California, USA): A senior software engineer who builds LLM and retrieval features with evaluations behind them, working remotely from Mumbai for San Francisco startups. It is for teams adding AI to a product that already has users, run on written updates because the Pacific day and mine barely meet.
- [Los Angeles](https://deependra.in/markets/united-states/los-angeles) (California, USA): A senior software engineer working remotely from Mumbai for Los Angeles media and consumer teams, planned around the Pacific clock. It is for premieres, drops and launches: fast Next.js front ends, editor-friendly content platforms and performance work.
- [Seattle](https://deependra.in/markets/united-states/seattle) (Washington, USA): A senior software engineer who takes on the cloud, database and integration work nobody owns, working remotely from Mumbai for Seattle SaaS teams. It is for teams on AWS or Google Cloud that want a second senior engineer and written handovers.
- [Austin](https://deependra.in/markets/united-states/austin) (Texas, USA): A senior software engineer who builds first versions at a fixed price, working remotely from Mumbai for Austin startups with your Central-time morning in my evening. It is for founders who want an MVP in customers' hands soon and a codebase they won't rewrite after the seed round.
- [Boston](https://deependra.in/markets/united-states/boston) (Massachusetts, USA): A senior software engineer working remotely from Mumbai for Boston health, biotech and SaaS teams, with the start of your day in my evening. It is for software that holds data that must not leak: secure web platforms, security audits and AI features.
- [Chicago](https://deependra.in/markets/united-states/chicago) (Illinois, USA): A senior software engineer who modernizes old core systems in stages, so the business keeps running, working remotely from Mumbai for Chicago teams. It is for established Chicago businesses more than startups, with your Central-time morning in my evening.
- [Denver](https://deependra.in/markets/united-states/denver) (Colorado, USA): A senior software engineer who builds Next.js products that search engines and AI assistants can find, working remotely from Mumbai for Denver teams. It is for product teams that need a SaaS first version, technical SEO or Core Web Vitals work, with your Mountain-time morning in my late evening.
- [Miami](https://deependra.in/markets/united-states/miami) (Florida, USA): A senior software engineer who joins Miami startups and agencies as the senior engineer on a build, working remotely from Mumbai with the start of your day in my evening. It is for first versions at a fixed price and client builds delivered under your agreement.

## Contracts and invoicing in the United States

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.

Tax and legal treatment depends on your company and country: confirm it with your accountant or counsel.

## Data protection and the rules that apply

### 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](https://oag.ca.gov/privacy/ccpa/gpc)

### 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](https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2)

This is engineering guidance, not legal advice: confirm what applies to your business with your counsel.

## Where teams in the United States usually start

- [MVP Sprint](https://deependra.in/services/build/mvp-sprint): A production-grade first version of your product, at a fixed price and on dates fixed after the scoping week. (price: Fixed price, agreed at the end of the scoping week; timeline: Set at the end of the scoping week)
- [Security audit and penetration test](https://deependra.in/services/secure/security-audit): An attacker's view of your application and infrastructure, and a fix list you can act on. (price: Fixed price per scope; timeline: Agreed per project after scoping)
- [AI features in your product](https://deependra.in/services/ai/ai-features): LLM features that work on your real data, measured before they ship. (price: Fixed-price scoping sprint, then a fixed-scope quote; timeline: A scoping sprint first, then a timeline agreed per project)
- [Performance and Core Web Vitals audit](https://deependra.in/services/scale/performance-audit): Find out in five working days exactly why your application is slow, and what to fix first. (price: Fixed price; timeline: Agreed per project)

## Case studies behind this work

- [InfluencerX](https://deependra.in/work/influencerx-voting-platform): Real-time voting platform. 1.6M+ users over the campaign.
- [Zyrobe](https://deependra.in/work/zyrobe-ai-wardrobe): AI wardrobe app. 3–8 s average time per image, upload to result.
- [TopGear India CMS](https://deependra.in/work/topgear-india-cms): CMS migration and modernization. 1–3 min → 3 s page load time, before → after.

## Questions from teams in the United States

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

### Which US state privacy laws affect my app?

It depends on where your users live and how many of them there are, because each state sets its own scope and has its own regulator. California's regulators treat a browser's Global Privacy Control signal as a valid opt-out, and Colorado and Texas also require covered businesses to honour universal opt-out signals; the [Denver](https://deependra.in/markets/united-states/denver) and [Austin](https://deependra.in/markets/united-states/austin) pages give those states' rules with their sources. The [guide to US state privacy laws and Global Privacy Control](https://deependra.in/writing/us-state-privacy-global-privacy-control) shows what the signal means in code. This is engineering guidance, not legal advice: confirm what applies with your counsel.

### How do contracts, invoicing and IP assignment work with a US client?

I work under your master services agreement with a statement of work per project, or under mine. Invoices are in US dollars, monthly or per milestone, paid through Wise or Payoneer, and I can provide a W-8BEN, the form a foreign individual gives a US payer to establish foreign status for tax purposes ([IRS: About Form W-8 BEN](https://www.irs.gov/forms-pubs/about-form-w-8-ben)). Intellectual property is assigned to you on payment, with the code in your repositories from the first day. Tax treatment depends on your company, so confirm it with your accountant; the [guide to working with an engineer in India](https://deependra.in/writing/working-with-an-engineer-in-india) lists the clauses I make sure every contract has.

## Related writing

- [US state privacy laws and Global Privacy Control: a guide for engineers](https://deependra.in/writing/us-state-privacy-global-privacy-control) (2 November 2026): Which regulators say a business must honour the GPC signal, what the Sec-GPC header means in code, and the consent and data-request plumbing around it.
- [Is llms.txt worth it in 2026? What Google, OpenAI, Anthropic and Perplexity document](https://deependra.in/writing/is-llms-txt-worth-it) (2 November 2026): What the llms.txt proposal is, what each company’s own documentation says about it, what Ahrefs’ crawl of 137,210 domains found, and what to do instead.

## Other markets

- [United Kingdom](https://deependra.in/markets/united-kingdom)
- [European Union](https://deependra.in/markets/europe)
- [United Arab Emirates](https://deependra.in/markets/uae)
- [Saudi Arabia](https://deependra.in/markets/saudi-arabia)
- [Japan](https://deependra.in/markets/japan)
- [South Korea](https://deependra.in/markets/south-korea)
- [India](https://deependra.in/markets/india)
- [All markets and shared hours](https://deependra.in/markets)

---

Cite as: Deependra Vishwakarma, "A senior software engineer for US teams, with the East Coast morning in common.", https://deependra.in/markets/united-states (last updated 2026-11-02).

This is the Markdown version of https://deependra.in/markets/united-states; the page is the canonical source. Start a project: https://deependra.in/contact