Skip to content
Ashish Jha
Explore

A few working principles / Not a privacy policy

What matters
in my work.

A few preferences that have shaped
the projects and roles I’ve taken.

I’ve also represented them as a small policy.
You can try it at the bottom of this page.

Start with the boundaries ↓

01 / Choosing the work

Reasons I’ve
said no.

These describe my choices, not advice everyone else needs to follow.

Boundary 01Forbid, when the condition matches

Take the job for the money

Turned down a full-time offer at nineteen. Said no to a bigger name later

I’ve turned down better-paid offers to pursue work I wanted to do.

Scope
Any offer · at any figure
Condition
motive = money

Boundary 02Forbid, when the condition matches

Do it in the conventional order

I freelanced before joining Okta, then moved to DevRev.

Freelancing came before corporate work for me.

Scope
Career path · as recommended
Condition
motive = order

Boundary 03Forbid, when the condition matches

Stay once it stops being interesting

My work has moved from voice applications to identity and AI agents.

I’ve changed roles as the work I wanted to do changed.

Scope
Any role · as my interests change
Condition
horizon = fixed-term

02 / Experience behind the rules

Work I’ve done.

These 6 examples supply the permissions in the demo.

Permission 04Allow

Answer a city at four in the morning

ATL311: website, app and IVR, all three surfaces

500K+city population served

Announced by Mayor Andre Dickens

See the work ↗

Permission 05Allow

Be the lion a child asks for

Wild Planet: 500+ animal sounds, co-developed

450K+monthly users

10M+ interactions a week. Most popular skill on Fire TV, 2020

See the work ↗

Permission 06Allow

Let the agent close the ticket

one8 and Lotto, live on WhatsApp, web and app

~80%resolved without a human, Aug 2026

Around 80% of conversations resolved end to end without a human, by August 2026.

See the work ↗

Permission 07Allow

Learn a framework over a weekend to win an argument

Flutter, against Auth0’s APIs, pixel for pixel

1weekend to learn Flutter and build the demo

The bank signed, and the demo opened seven or eight similar mobile opportunities.

See the work ↗

Permission 08Allow

Ship voice at industrial scale

Ten Amazon marketplaces, nearly six years freelance

UKfirst official skill

Fiverr Top Rated Seller, about 500 five-star reviews

See the work ↗

Permission 09Allow

Cold-email the CEO of Amazon

At nineteen, about a promotion Indian developers could not enter

One emailsent 25 Nov 2017

Amazon replied. It worked

See the story ↗

03 / If you’re curious how it works

You can ask the policy.

6 permits. 3 conditional forbids. Default deny.
One matching forbid overrides any permission.

Compose a requestOptional · Three choices, with the reasoning shown

An interactive model, not a real authorization service or a job application. Changing a choice only evaluates these rules locally.

Request choices

May I ship a voice app because it is the interesting problem, for as long as it holds?

The policy says

Allow

Rule 08: Ship voice at industrial scale.

A permit matched and nothing forbade it.

Fiverr Top Rated Seller, about 500 five-star reviews

Read rule 08 ↑Follow the evidence ↗
Show the working 1 of 9 rules matched
  1. Rule 01Take the job for the moneyNot matched
  2. Rule 02Do it in the conventional orderNot matched
  3. Rule 03Stay once it stops being interestingNot matched
  4. Rule 04Answer a city at four in the morningNot matched
  5. Rule 05Be the lion a child asks forNot matched
  6. Rule 06Let the agent close the ticketNot matched
  7. Rule 07Learn a framework over a weekend to win an argumentNot matched
  8. Rule 08Ship voice at industrial scaleDeciding rule
  9. Rule 09Cold-email the CEO of AmazonNot matched

96 possible requests: 24 permitted, 64 explicitly forbidden, 8 denied by default.
The result describes this small policy, not everything I might ever agree to.

Have something in mind?

Bring the
interesting problem.

Let’s talk ↗See the work ↗