Wahab retweeted
I almost didn't get hired at Dropbox. I did well in some parts of the interview, not so well in others, and a couple of people had to go to bat for me. Then I had to do a take home. And then, I think I just wore them down and they hired me.
That job ended up changing my career.
That's why I've been a little skeptical of how much you can realistically learn about someone in a couple of hours of interviews.
I've become more willing to take chances on people. If someone seems smart, curious, hungry and has a track record of building things, I want to give them a shot and see how they do.
xitter.gq/felixrieseberg/status/âŠ
The coding interview is dead, at least for my team at Anthropic. I've seen enough to know that it no longer provides signal. I removed it from loops this month.
I have a spicy, optimistic take - I think there's an opportunity for junior engineers: felixrieseberg.com/hunger-beâŠ
Wahab retweeted
Counting is REALLY hard.
Accounting is mostly about counting (hence why it's called a-counting and not a-something-else). Specifically it concerns counting money.
But in order for you to count money, you first have to first count the thing in the Real World that is associated with the money. Let's call this "stuff"...
Now - we humans have been counting stuff for a long time. Most historians focus on double-entry bookkeeping in medieval Florence. But in reality, we need to go back another 4,000 years to Mesopotamia to tell the whole story.
Ancient Sumerians in BCE 3,300 were using clay tablets to express their trading obligations of their stuff.
They learned to express the relationships of their obligations to one another in credit and debit in relative units of measure: I owe you 1/5 of a bale of hay because you gave me 2 bushels of wheat.
It took a few millennia to figure out how to get these "values" into a normalized system when Italian merchants created modern bookkeeping.
...And then it took another 500 years to put these in computers: IBM, SAP, and Oracle pioneered various patterns of fact tables, rolling consolidation, continuously reconciling sub-ledgers at a global scale. These power almost all of the worlds major commerce and financial systems.
As we built our ledger in DOSS, we ran into a problem over and over again: how do you make it such that a physical item in the Real World actually carries a value (cost) as a property, so that you don't have to keep going back to the item and spreading costs over it like very messy peanut butter? And if you ever need to "unspread" the costs, how would you do it without making a mess?
For anyone who's run an inventory-based business you know a few things:
- Tracking the real cost basis of something (as opposed to the 'estimated' amount) is shockingly hard (often impossible).
- The delta between the estimated cost and the actual cost often are wildly different because accounting systems are designed around tracking the money, not the value of the items.
We've redesigned into a framework that we internally call "Items-and-Values" that let's us unify the physical world of atoms and the virtual world of dollars with the fluidity and expressiveness required of complex supply chains.
Excited to share more in the coming months, but this allows incredible techniques:
- Seamlessly switch between costing methods
- Define rules to build different definitions of costing and revenue recognition on demand without having to post journal entires or edit transactions
- Apply a spectrum of traceability: verified with physical lots, assumed with virtual lots, and identify non-traceable segments of the chain of custody
How do you build an operations platform that accurately represents what's happening in the real world, right now, messy context, changes, and all, while giving clean, reliable finance inputs to Finance teams?
By making the real world the product itself.
We got into the foundations of our platform build in our engineering blog, "Where the Real World and Software Meet: Introducing the DOSS World Model."
Read it here: doss.com/resources/eng-blog/âŠ
Weâve been rebuilding workflows at @doss_hq to be authored in TypeScript. Agents are fantastic at writing code; our legacy workflow DSL was getting in their way.
Wrote about why we made the switch, and how we run customer code safely as real TypeScript:
doss.com/resources/eng-blog/âŠ
Wahab retweeted
i spent 4 years working towards this moment and now it is finally here
DOSS "Dragonfly" our upgraded platform, product suite, and agent copilot
xitter.gq/doss_hq/status/2110417âŠ
Introducing the next generation of DOSS.
Todayâs release includes:
[1] Dynamic Apps: describe the workspace you need, Dossbot builds it.
[2] Product Suite 2.0: procurement, inventory, orders, finance, master data on one record.
[3] Dossbot: from âwhy?â to a plan to action.
Live today.
Wahab retweeted
hot take: company culture matters more than the product roadmap right now.
with everyone building similar things, the real differentiator is who you hire, what gets rewarded and the culture those people create.
Wahab retweeted
I interviewed every person we hired at @Clay in my orgs until we passed 300 people.
We're scaling beyond that now, so our recruiting ops team built a system that keeps me involved in every hire.
We have a Slack channel called hiring-theses and I review it every day. Before we hire anyone, the hiring manager writes a hiring thesis about the candidate. It answers four questions:
1. Why should we hire this person?
2. What is one exceptional thing this candidate has accomplished in their career or otherwise?
3. What are the risks/concerns?
4. How will we support this person if they join?
A thesis draws on a deep dive interview into the candidate's whole story, behavioral interviews, scored feedback from every round, and thorough reference calls. The thesis also includes every piece of submitted interviewer feedback. When I review that feedback, I notice discrepancies, pieces of feedback from an interviewer that the hiring manager didn't address, or missing voices I want to hear from.
Then I approve, deny or discuss with the hiring team. I can't sit in every interview anymore, but I still read every thesis and every piece of feedback before someone joins Clay.
Hopefully this is helpful to other teams scaling past the point where a founder can meet every candidate. Let me know if you have any questions!
Wahab retweeted
This is the best use of time for college students who care about tech and startups. Iâve been lucky to be around @DormRoomFund from day 1, and have invested in DRF founders (@AnjneyMidha @tonioloko and others) and invested with DRF investors (@laurenmhreeder @nealkhosla @shawnxu @nunzi46 and others)
When I say #DRF4Life itâs these relationships - and the early belief in each of these @DormRoomFund alum - that mean so much.
Apply. Youâll see.
What do @tonioloko (Dandy), @mntruell (Cursor), and @laurenmhreeder (Sequoia) have in common?
While in school, they were all DRFers. Once they graduated, they stuck around.
It's the final countdown, apply to join the best group in venture by Thursday, 9/17 @ 11:59pm ET!
Wahab retweeted
For the icons, we discussed it at length in a sidechat and my Muse made me the initial list, helped with prompts, and the approach for expansion.
We rendered them right there in chat with Muse Image, and he made me a catalog Artifact to manage them and add notes for re-runs.
Wahab retweeted
One of the most surreal parts of designing Muse was my Muse being my main collaborator. It is very funny to be asking the question "How do you think you should work?"
Brainstorming how different features work, generating mockups and prototypes, critique, etc.
Wahab retweeted
Super excited to get Muse out into the world today. I've never worked on something like this before that has genuinely helped me in every major area of my life.
Having an agent that has a computer, is always on, connected to the things I already use, and understands what I care about, is immensely powerful.
So proud of the team.
1/ today we're rolling out Muse, our new personal ai assistant. Muse is always-on, wicked fast, can use a browser, connect to your apps, and is designed to be secure.
try it now: muse.ai.
Wahab retweeted
Thought a lot about using AI in my work. Wrote about how it makes me feel here:
open.substack.com/pub/phinbaâŠ
Wahab retweeted
Got an ask for some product animations to update our marketing site.
Decided to deliver tools and workflows instead of assets:
- @figma chrome plugin to grab screens from current app
- point agent at the code package for our yet-to-be-released design system to update Figma mocks
- prompt in some dummy data
- Pit Figma agents head-to-head against Claude for motion work
She got sick results in a couple of hours, and Iâm never a bottleneck. We love to see it
Chemistry was there
Inner voice
Gut feel
Most important hiring decisions are not âdata drivenâ at all.
Steve Jobs really pulled a reality distortion field to poach Tim Cook from Compaq (in 1998, it was worth $30B+ to Appleâs $3B).
All of Cookâs friends and advisors told him not to join almost-bankrupt Apple.
Cook says it took Jobs one meeting to convince him:
âI had gotten a call several times from the search people that [Jobs] had employed, and I kept saying no.
I was happy at Compaq â or thought I was â and they were persistent.
So, I finally thought, âyou know, Iâm going to go out and take the meeting. Steve created the whole industry that Iâm in. Iâd love the meeting.â [âŠ]
All of a sudden, heâs talking about his strategy and his vision and what he was doing.
He was going 100% into consumer when everybody else in the industry had decided you couldnât make any money in consumer. They were headed to servers and storage and the enterprise. [âŠ]
I always thought following the herd was a bad idea.
He showed me a bit of the design to get me interested [of what later would be called the iMac].
The way that he talked and the chemistry. I could tell I could work with him.
I looked at the problems Apple had and I thought âyou know, I can make a contribution hereâ and working with [Jobs would be] the privilege of a lifetime.
All of a sudden I thought, âIâm doing it. Iâm going for it.â
You hear this voice in your ear that says, âGo west, young man, go west.â
[The move to Apple] didnât make sense. And yet my gut said âgo for itâ and I listened to my gut.
There was literally no one around me that was advising me to do it.â
In March 1998, Cook joined Apple as Senior Vice President of Worldwide Operations on a $400k base salary (and a $500k signing bonus).
He was 37. Incredible gut call.
***
Full episode here from 2014: youtu.be/u9Sy3qwthCw
Team Photo update đ·
The DOSS team just wrapped up our annual offsite in sunny San Diego, spending quality time together, planning for the future, and strategizing on how we can better help our customers grow.
â
Vision setting by @wileycwj and @arnavgmishra
â
Getting locked in on the value we're bringing to the consumer goods industry
â
Outcome showcase of what we have created for our customers
â
Incredible ice breakers
â
Team dinners across the city
â
Demos of our soon to be released features
â
Little Italy unofficial scavenger hunt
â
All the laughs you could ask for
Join us next time: lnkd.in/gvKhuPTb
#doss #operationsplatform #companyoffsite
Wahab retweeted
Looking at AI to replace recruiting is plain foolish! It should be used to augment recruiters and not keep them out of the loop!
this. is. happening. everywhere. the great AI unfucking has already begun and it's glorious. futurism.com/future-society/âŠ
Wahab retweeted
My biggest takeaways from @wardadamp (Head of Talent at Cursor):
1. The forward deployed engineer is the hottest role in tech right now. These are deeply technical people who can partner with sales, be confident in a room with executives, translate complex products into business outcomes, and help customers shift from âtoken maxingâ to optimizing AI bills. Adam likens this to the mobile-engineer hiring boomâexcept that one played out over two years, and ânow weâre in days or weeks.â
2. The traditional recruiting funnel, what Adam calls the âfunnel of doom,â is designed to build mediocre teams. The standard hiring funnel (reach out to 100, 20 reply, weed out at each stage, hire who remains) rests on a broken premise: the 100 people who reply in the first place arenât the top 20%. Theyâre whoever you caught on a bad day. By the time a candidate gets to the bottom of the funnel, youâre selecting from an already-suboptimal pool. Even with an rigorous interview process, this leads to average teams.
3. The alternative is treating every hire like an executive search: rigorous scoping (what does âgreatâ mean for this specific role?), deliberate candidate mapping (who are the 50 best people in the world for this role?), and relentless pursuit (go after these 50 people and donât stop). The shift is starting with a âpillar of excellenceâ rather than a wide funnel.
4. The new danger zone is after the offer is signed. Candidates reneging on accepted offers is a rising trend, and senior hires often sit for weeks between signing and starting. So Cursor treats the post-accept period as its own campaign, with dinners alongside other incoming hires, a laptop shipped before day one, and a community forming before anyone officially starts. It makes sure people actually show up, and it gives them a head start on ramping up.
5. Work trials are the highest predictor of success. Research has consistently shown this to be true, yet the default on-site is still a series of one-on-one conversations across a table. Cursor runs long on-site experiences where candidates work side by side with the team on a real (or realistic) project. That format generates technical signal, core-values signal, and collaboration signal simultaneouslyâand it gives the candidate data to self-select. When Cursor ran an experiment removing the work trial, hiring confidence dropped significantly. They brought it back.
6. Asking your network âWhoâs the best engineer you know?â is a trap. Instead, ask hyper-specific questions tied to your scoping details insteadââOf all the product engineers youâve worked with, whoâs most collaborative with designers?â or âWho can translate a framework into a product better than anyone youâve seen?ââbecause specific prompts make names easy to conjure. When multiple trusted people independently mention the same person (âLenny mentioned them, but so did Sallyâ), youâve triangulated a target for your top-50 list.
7. Scoping the role is the most under-invested step in most hiring processes. âIâll know great when I see itâ is a trap. Without spending time up front to define and stack-rank the skills, experiences, and attributes that you need in this specific role at this specific company, you have no sourcing strategy, no pitch, and no way to design a real assessment. Everything downstream flows from this. And resist the logo shortcut: a strong team at a company at the right time is only âpossiblyâ shorthand for great, and copying someone elseâs definition means piggybacking on a hiring process you already believe is broken.
8. When a top candidate says âbad timing,â shrink the ask: âIâm not asking you to interviewâIâm asking for our next conversation.â Adam plants seedsâa coffee, an office visit, an intro to a teammate fascinated by their workâthat bear fruit over weeks, months, and sometimes years, because going silent until âlate fallâ means, at best, you get them if no one else has grabbed them first. Almost as much effort goes into finding a warm intro as into the message itself, since once someone ignores your first note, ignoring the second and third gets much easier. Cursor also plays âhome games,â centering touchpoints on shared mealsââa disarming act and a joining actââand office visits designed to trigger the campus-tour gut feeling of âthis feels like home.â
9. Closing is a team sport, and it starts at the first conversation. When Cursor has a high-caliber candidate in process, there are daily standups focused on that specific person: What did we learn about their motivations? What objections came up? Who on the team can speak to those concerns? Every candidate gets a dedicated Slack channel. The âcloseâ shouldnât feel like a separate sales push but, rather, the natural conclusion of a process that has been consistently demonstrating the same answer.
10. Caring is free, and itâs the biggest unfair advantage in recruiting. In candidate-satisfaction scores across the history of the field, Adam says the number one driver is feeling that the company genuinely wanted you, so Cursor curates every touchpoint: who greets a candidate, who sits beside them at lunch, which interviewer shares their niche interestâhandpicked rather than left to calendar availability. The reframe that makes it sustainable: youâre hiring one person for this role, not 10. âDonât get caught up in the 10; focus on the one.â
Cursor has spent its entire existence competing with every major AI lab and incumbent in the toughest market in techâand has continued to win. So much so that @elonmusk bought them for $60 billion to help SpaceX win the AI race.
They've done this by building one of the most talent-dense teams in history.
Adam Ward (@wardadamp) is Head of Talent at @Cursor_AIâwho acquired his legendary recruiting firm after he spent 20+ years building the most elite teams in techâand in our conversation he shares the entire playbook for building high talent-density teams.
We discuss:
đž Why the traditional recruiting funnelâthe "funnel of doom"âguarantees mediocre hiring
đž Adam's three-step playbook for hiring the top 1%
đž The rise of the forward-deployed engineer
đž Today's "tale of two cities" talent market
đž The biggest mistake founders make with their first recruiting hire
đž The worst question you can ask when sourcing talent (you've definitely asked it)
Watch the full episode right here đ
Wahab retweeted
If you are a recruiter, this is literal GOLD!
AI / @TownAI tips for recruiters:
Was thinking about all my recruiter pals out there who do superhuman work managing processes that donât follow clean templates (e.g., scheduling around everyone's calendar constraints, engaging a maybe-ghosting candidate, offer to prep) with context split across inboxes, LinkedIn, spreadsheets, Slack, Drive, your ATS etc. Some ways a Townie can help:
1. Interview scheduling
Navigating calendars to schedule interviews for candidates always takes more brain capacity than it should. You canât just look for open calendar spots b/c one person has a lunch rule, another wants their first day back from PTO left clear, and every on-site round needs its own room. A Townie can do all this for you. prompt to set it up:
>> âWhen I schedule interviews for a candidate, build around each interviewer's real constraints, not just open calendar slots. Pull those from our hiring Slack channel and past emails too: no one booked their first day back from PTO, a room for every on-site round, each person's own lunch rule. Reuse the exact invite wording I've already approved, no paraphrasing. Confirm the constraints with me first, then run it on one open req as a test."
2. Post-offer approval logistics
Once an offer is approved, closing the candidate consists of things like generating an offer, scheduling follow-ups, updating the ATS, keeping the hiring manager in sync, all while accounting for the candidateâs timeline. A Townie can help! Prompt to set it up:
>> "Once an offer is approved for a candidate, handle the post-offer approval logistics for me. Generate the offer summary, schedule the follow-ups around the candidate's own stated decision date pulled from the recruiter-screen notes and our email threads, keep their stage in my ATS current as things move, and post an update to the hiring manager in Slack at each step. Confirm the follow-up timing and who to notify with me first, then run it on one open offer as a test."
3. Candidate responses and check-ins
Candidate replies come in sporadically throughout the day across email and LinkedIn, and each one needs a next step that fits where that person sits in the pipeline. A Townie can work through the replies, check each candidate's stage and req in the ATS, and draft the next message in the tone already used with that specific person, so a recruiter opens the day to a stack of ready-to-send replies instead of a cold inbox. Prompt to set it up:
>> "Each morning, build me a candidate-reply queue. Go through the overnight replies from candidates in my active pipeline across email and LinkedIn, check each person's stage and req in my ATS, and draft the next message in the tone I've already used with them. Leave anything ambiguous or high-stakes for me to review. Confirm which pipelines to cover with me first, then run it as a test on tomorrow morning's replies."
































