Zero Maintenance Engineer retweeted
8 hired through @proofzme so far:
5 at startups, including Omnisavant and HighOnSwift
3 by us
(2 of them paid gig work for founders)
14 more got jobs on their own. They practised in mock interviews on Proof and wrote about their work while they prepared. 3 of them had been laid off after years of experience.
There are two ways into a job through @proofzme . of the 8 jobs, resume was never shared for any of them.
1. Build it. A founder posts a role with a small real project. You build it and write down why you built it that way. The project is your application.
2. Get pulled. You log your work on Proof for weeks, with the why behind it. A founder reads those logs and reaches out to you first. You didn't apply.
Pandidharan got interviews this way: founders read [23 days] of his logs and asked to talk.
133 people wrote on Proof this month. About 19 of them write the why: the trade-off, what it cost, what they weren't sure about. We keep showing them how, one log at a time.
Logs and a built project show how you think, so the interview is about work you've already done.
Hiring engineers? Post a role, and read who's already writing →
We have a referral program as well.
proof.zeromaintenanceenginee…
---
Zero Maintenance Engineer retweeted
best hiring approach @Radhakr08781352 @proofzme @0_main_engine
bonus: India gets to flaunt the open source contribution tech muscle :)
For startups that have open source projects, I’m increasingly hearing that before posting positions they just ping top contributors to see if they can hire them
Those contributors proved they know how to do the day-to-day work in ways better than an interview would prove. Plus they know what the product does, are motivated to help etc
Zero Maintenance Engineer retweeted
If you are referring someone and then they get hired via @proofzme in an org, you get paid Rs. 5000
Zero Maintenance Engineer retweeted
One more successful hire via @proofzme
Zero Maintenance Engineer retweeted
Another role opened for 40k for freshers.
Build it via @proofzme
proof.zeromaintenanceenginee…
You dont need a resume for this software engineering internship position.
Log for the next 10 days and get selected.
proof.zeromaintenanceenginee…
In the last 2 weeks,
4 power users of Proof have got a job. (Not for a role posted via Proof)
All have been using Proof to learn to articulate their thoughts.
Two of them used mock interviews to prepare well for the interviews.
2 months ago one of the power users got a job at Kuku FM.
For power users, Proof enables system 2 thinking making it easy for them internalize and recollect a concept in an interview.
P.S:
7 have been hired via Proof
1 of them have been selected to Lossfunk residency
Zero Maintenance Engineer retweeted
#hiring 2 interns to help grow Wispr Flow in India. Both roles are Bangalore-based.
1. You’re sharp with analysis, high energy, and you obsess over growth charts and dashboards, built both the old-school way and with AI.
2. You can own the execution work on marketing campaigns: the research and building behind the screen, and showing up on the ground to make shit happen.
Apply now👇🏼
Zero Maintenance Engineer retweeted
A 20-year-old entering tech is just getting started.
They won’t know everything and we shouldn’t expect them to.
Be more forgiving with early-career talent. Limit the requirements. Give them room to learn.
Hire for fundamentals, curiosity, and the ability to grow.
Zero Maintenance Engineer retweeted
Most people build their careers by collecting credentials-
Courses, Certificates, Degrees, Job titles.
We think there's another way.
> Build.
> Solve.
> Document.
> Improve.
> Become a ZME
...
Zero Maintenance Engineer retweeted
Mobile app looks sooo good! @proofzme
Zero Maintenance Engineer retweeted
If you learn GTM Engineering, you will never be unemployed again.
Stage 1: GTM Data Architecture and Reverse ETL
- Learn: Snowflake/BigQuery, Hightouch/Census, identity resolution, API webhooks.
- Practice: Build a pipeline that syncs raw Stripe billing data and product usage directly into HubSpot/Salesforce custom objects.
- Why: GTM without a single, code-level source of truth is just guessing.
Stage 2: Signal and Intent Pipelines
- Learn: Website deanonymization (Clearbit), intent data (Bombora), event streaming.
- Practice: Build a webhook router that instantly alerts a Slack channel when a target enterprise account visits your pricing page 3 times in one week.
- Why: In B2B, timing beats the pitch. You must strike while the intent is hot.
Stage 3: AI SDRs and Hyper-Personalization
- Learn: Clay, Apollo APIs, LLM data enrichment, web scraping.
- Practice: Build an AI agent that scrapes a prospect's recent GitHub commits or podcasts and writes a highly specific, 1:1 cold email.
- Why: Generic outbound is dead. AI makes infinite personalization mathematically possible.
Stage 4: Product-Led Growth (PLG) Telemetry
- Learn: PQL (Product Qualified Lead) scoring, event tracking (Segment/Rudderstack), feature adoption curves.
- Practice: Write a script that triggers a high-priority sales alert the second a free-tier user hits a specific "aha moment" API threshold.
- Why: The product is your best salesperson. Hand-raisers convert 5x higher than cold outbound.
Stage 5: Usage-Based Pricing (UBP) and Monetization
- Learn: Stripe Metered Billing, credit systems, value-metric alignment, API metering.
- Practice: Design and implement a pricing architecture that charges by "agent executions" or "tokens processed" instead of flat "per-seat" licenses.
- Why: SaaS pricing has permanently shifted from charging for access to charging for outcomes.
Stage 6: Revenue Operations (RevOps) and Attribution
- Learn: Multi-touch attribution, funnel leakage analysis, SQL, cohort analysis.
- Practice: Build a dashboard proving exactly which combination of LinkedIn ads, webinars and cold emails sourced your closed-won enterprise deals.
- Why: If you cannot mathematically prove ROI, the CMO will cut your budget.
Stage 7: AI Sales Enablement and Coaching
- Learn: Gong/Chorus APIs, transcript summarization, vector search on sales calls.
- Practice: Build a tool that analyzes 100 lost sales calls and auto-generates an updated "objection handling" battle card for the sales team.
- Why: Reps forget 70% of their training. AI reinforcement loops fix the leaky bucket.
Stage 8: Predictive Churn and Expansion (NRR)
- Learn: Health scoring algorithms, Net Revenue Retention (NRR) math, usage drop-off alerts.
- Practice: Build a "churn risk" model that flags accounts with dropping API usage 45 days before their renewal date.
- Why: In the AI era, switching costs are low. Retention and expansion are the only real growth.
Stage 9: Integration-Led Growth (Ecosystem GTM)
- Learn: App marketplaces, OAuth flows, Zapier/Make templates, co-selling motions.
- Practice: Build a native integration for a major platform (like Slack or Salesforce) and optimize its marketplace listing to drive inbound leads.
- Why: Buyers trust their existing stack more than your cold email. Ecosystems are the ultimate distribution.
Stage 10: Dark Social and Community Attribution
- Learn: Untrackable attribution, Discord/Slack community ops, developer advocacy metrics.
- Practice: Launch a niche technical community and build a survey-based model tracking how "word of mouth" correlates to enterprise pipeline.
- Why: B2B buyers buy from peers in private Slack groups not from vendor whitepapers.
Stage 11: The Automated QBR (Quarterly Business Review)
- Learn: Data visualization, automated reporting, ROI calculation frameworks.
- Practice: Build a script that pulls customer usage data and auto-generates a custom, branded ROI slide deck for the Customer Success team.
- Why: CSMs should be strategic advisors not manual data gatherers.
Stage 12: Public GTM Teardowns and Portfolio
- Learn: Pricing psychology, funnel teardowns, public writing, benchmark analysis.
- Practice: Publish 3 deep-dives on how top AI companies structure their pricing pages, onboarding flows, and credit systems.
- Why: GTM leaders and Revenue Architects are hired for their strategic judgment, not just their SQL skills.
Code builds the engine. GTM builds the fuel.
The modern GTM Engineer builds the nervous system for global revenue and autonomous sales agents.
Bookmark and Repost!


















