ANISH JHAVERI · SOFTWARE ENGINEER · AUSTIN, TX

Modernize and ship reliable software without adding a full-time hire.

I help founders and product teams improve existing applications, build focused new systems, and connect AI or backend workflows to measurable business outcomes.

Client systems and internal toolsReliable backend workflowsDirect ownership through handoff
PRACTICE PRINCIPLES

Why teams work with Slake

I help teams turn ideas, requirements, and technical problems into working software, without unnecessary layers of communication or project management.

01 / DIRECT COLLABORATION
Direct Founder-to-Engineer

Technical decisions, implementation, and delivery are handled directly by Anish Jhaveri. Fast feedback and direct communication throughout the project.

02 / ENGINEERING QUALITY
Software Built for Real Use

Applications, backend systems, and internal tools built with maintainable code and practical deployment workflows.

03 / CLEAR MILESTONES
Predictable Scope & Delivery

Documented milestones, regular async code updates, and transparent timeline expectations from start to finish.

04 / HANDOFF
Complete Handoff

Your team receives the code, database schemas, documentation, and deployment details needed to continue development.

FEATURED PROJECTS

Selected Work

Projects demonstrating full-stack development, backend engineering, and practical AI implementation.

Natural-language marketplace search for a two-sided platformClient Engagement · Architecture Case Study

Built a natural-language marketplace search experience that lets users describe what they need instead of relying on rigid filters.

Read Case Study →
Grounded AI document search for technical APIsEngineering Project · Live System

Independent retrieval project over Stripe API docs, providing cited passages and bounded implementation answers.

Inspect Live System →
Distributed asynchronous job queue systemEngineering Project · Live System

BullMQ and Redis background task processing with retries, SQLite idempotency locks, worker telemetry, and failure handling.

Inspect Live System →
Model Context Protocol server for SQLite databasesOpen Source Project · Live System

MCP and SQLite project for validated database tools, JSON-RPC transport, and write-mutation controls at the proxy boundary.

Inspect Live System →
ENGAGEMENT PROCESS

How I work

A straightforward process to take software requirements from initial conversation to maintainable code.

01
Discuss the problem

We review your requirements, technical goals, and current architecture.

02
Propose a scope

I outline a clear technical specification, approach, and timeline options.

03
Agree on milestones

We align on concrete deliverables, acceptance criteria, and check-in cadence.

04
Build the software

I build, test, and deploy the software with regular async updates.

05
You own the code

Full code handoff to your repositories and setup docs. Post-launch support options available after delivery.

CURRENT AVAILABILITY

Currently accepting new software engineering engagements

Remote-first from Austin, Texas (US-based).

Typical response within one business day.

Discuss a project
TRANSPARENT BOUNDARIES

I may not be the right fit if:

  • You are looking for a large development agency or multi-tier account team.
  • You need a full agency team of visual designers, marketers, and copywriters.
  • You are looking for cheap offshore staff augmentation.
FREQUENTLY ASKED QUESTIONS

Common questions before starting

Do you work with existing engineering teams?
Yes. I can build software independently from spec, or integrate directly with your existing engineering team, GitHub repositories, and development workflows.
Do you take fixed-price projects?
Yes. Fixed-scope builds include a defined technical specification, documented milestones, and predictable pricing so there are no billing surprises.
Can you work remotely?
Yes. I am based in Austin, Texas (US-based) and operate remote-first with clear async communication, regular video syncs, and fast response times.
Do clients own the code?
Yes. All agreed code, database schemas, and documentation are transferred to your repositories upon completion. Ownership follows the written scope.
What happens after launch?
Projects can include post-launch support and monitoring depending on the engagement. Ongoing engineering options are available for continued development.
How does contracting and onboarding work?
I contract through a registered US LLC using a standard Professional Services Agreement, W-9 compliance, and standard corporate invoicing.