pwep consulting// THE FIRM
01 / 05 Overview00:00:00SAHIL TALWAR ↗

Waypoint 01 // Engineering leadership

pwep consulting

I'm Sahil Talwar - consultant, advisor, fractional CTO, former Oracle engineering director and RedShelf VP. I help engineering leaders adopt AI, improve delivery, and build stronger teams through independent assessments, practical plans, and leadership coaching.

50People led · Oracle
20%+Delivery gain via AI · RedShelf
25%Lower operating costs · RedShelf
30BAPI calls / day · Oracle

Waypoint 02 // Engine Room

Where I can help

Independent advice grounded in the code, the workflow, and the people doing the work. I assess, recommend, and coach. Your team owns implementation.

Service 01

AI Engineering Assessment

  • Review of agent workflows, tests, and release controls
  • Gaps between intended behavior and what gets checked
  • Baseline for delivery time, rework, and defects
  • Ranked risks and recommendations for leadership

Service 02

AI Adoption & Change Planning

  • Where AI helps, where it does not, and why
  • Pilot plans with success measures and stop criteria
  • Recommendations for context, evaluations, and review gates
  • Clear ownership and a staged adoption roadmap

Service 03

Engineering Organization Assessment

  • Team interviews and a review of delivery evidence
  • Bottlenecks in ownership, decisions, and handoffs
  • Recommendations for team structure and management practices
  • A prioritized improvement plan tied to business goals

Service 04

Leadership Coaching & Advisory

  • Coaching for engineering managers and executives
  • Technical strategy and architecture decision reviews
  • Guidance through changes in tools, roles, and expectations
  • Follow-up on outcomes as your team makes changes

When to bring me in

  • AI produces code faster, but we’ve just moved the bottleneck to review.
  • Nobody can show whether AI adoption improved delivery.
  • Agents pass tests without addressing the actual user need.
  • Team structure and decision-making slow the roadmap.

Who I work with

  • CTOs and VPs assessing AI adoption and delivery risk
  • Founders rethinking engineering structure and priorities
  • Engineering leaders navigating organizational change

Waypoint 03 // Casefile

Selected work

Across separate roles at Oracle and RedShelf, I led engineering for platforms supporting $185M in combined annual recurring revenue. Below: work from those roles, an advisory engagement, and an independent AI project.

A

Job Hunter: evaluating agent workflows

Selected work
  • Built an open-source workflow to match jobs and tailor resumes against source material.
  • Reduced average runtime from over 7.5 hours to ~10 minutes with identical inputs and the same processing stages.
  • Applied LLM-as-a-judge best practices, including blind grading and a separate truthfulness reviewer.
  • Tested through a full pipeline of automated tests: evals, a variance harness, fake data, and real data.
B

Advisory: unblocking a stalled organization

Selected work
  • Advised a CTO for 20 months on a 30-person engineering organization - structure, delivery, and leadership.
  • Redrew team ownership so most work could ship inside one team, and cut the dependencies between them.
  • Retired a PMO reporting cycle that was causing the missed deadlines it existed to prevent.
  • Coached two directors and six managers, two of them to promotion, and ran a team directly when one needed it.
C

RedShelf: improving delivery

Selected work
  • Led engineering for a platform supporting $35M+ in annual recurring revenue, 8M+ users, and 20M API calls/day.
  • Improved velocity 20%+ by modernizing delivery around AI tools, hard quality gates, and better tests.
  • Launched a new product that grew annual recurring revenue 10%; cut legacy operating costs ~25%.
D

Oracle: operating at scale

Selected work
  • Ran engineering for a $150M ARR platform from software to compliance to privacy to abuse prevention.
  • Managed internet-scale infrastructure (30+ billion requests per day and 1M+ requests per second at peak).
  • Created a deeply loyal org with my engineering managers and saw only four departures in four years.

Waypoint 04 // Protocol

How engagements run

  1. 01

    Assess

    Talk to the team, inspect the workflow and technical evidence, and establish a baseline. Separate observed problems from assumptions.

    Findings
  2. 02

    Recommend

    Lay out the options, tradeoffs, and priorities. Agree on owners, success measures, and what not to change.

    Plan
  3. 03

    Guide

    Coach leaders through the changes and review decisions along the way. Your team owns implementation.

    Coaching
  4. 04

    Review

    Compare results with the baseline. Keep what works, address what does not, and leave the team able to continue without me.

    Evidence

Rules of engagement

Control the workflow
Models are probabilistic; production systems must have close to deterministic output.
Show the evidence
Define intended behavior before choosing checks. Measure delivery and defects, not just code volume or tool usage.
Strengthen the team
Make the reasoning clear, develop the people doing the work, and avoid creating a dependency on the consultant.

Formats

Evaluate
Focused review with written findings
Plan
Adoption roadmap and decision criteria
Coach
Support for engineering leaders and managers
Advise
Ongoing reviews of decisions and outcomes