upvote
I'm going through the job search process, and doing things very similar to what you recommend here. Unfortunately I don't see much interest from recruiters on my "high agency" projects. For context, those include a macOS app with over 300 paying customers, or an iOS and Android app with a handful of non-paying customers.

They're mostly interested in things I've already done in the past that involved large amount of users, which automatically filters out all those high agency projects.

Getting many users for your projects would be an option, but I see two problems there: - finding users requires a set of skills that is completely orthogonal to software development, so you'd need to learn those skills on the side - finding users is getting harder and harder, as your new project is the 100th release of the day

Besides, if you manage to build a good project and find users, you might not need a job at all. But let's say there's a 10% chance that happens. Then there's a 90% chance you go into your first interview as someone who failed to get a project off the ground, which is kind of the opposite of showing high agency.

And the odds of success are probably closer to 1% or smaller.

reply
I was a hiring manager/director for 30 years. I really liked to hire for "initiative" although that's hard to evaluate.

When scanning resumes, I would look for interesting projects and then on inteviews, drill down deep on one or more of them to see what the person actually did, how they think about it and how they worked with others.

Unless it's a senior position, I wouldn't care about the customer/business aspects or even if they were the creator/leader or not. I hired in one country where they had a rigorous math education but the professional projects weren't a good fit. But they had interesting things to say about the technical aspects of open source projects they worked on. That's better than having to project someone's aptitude. I also let my engineers assess technical ability, of course.

reply
I can't speak for the others, but I would highly disagree that a failed project is the opposite of high agency! I know companies have this fetish for candidates who have worked "at scale" (even though they themselves don't, but I think it's misplaced. If I see that somebody made something end-to-end that even a few people would actually use, I would not blame them for a failure of GTM. As you said, those are not skills they should be required to have. But everything else that went into it matters a lot.

If they failed to launch at all, even with all the generous free-tier options out there, I'd agree that would be a concern. But at least in Silicon Valley and many tech circles, a failure is considered a badge of experience as long you gave it a proper try.

Yes, we now have to build orthogonal skills, but that is also kind of the point. Not only does it show adaptability and capability with AI, we need to be building proof of competency that could also become a source of revenue. Because I feel like these days counting on getting a job is like having hope for a strategy.

I totally feel the discouragement you're facing, and sorry if I make it worse, but this may increasingly be the only path left for us and at least you're farther along than most. Because a) what else could you be doing instead? and b) 300 paying customers is non-trivial and may even become a source you could grow.

reply
GTM - getting to market?
reply
AI has totally demolished portfolio value. Anyone can build a portfolio in a weekend and a hiring manager has neither the time nor the expertise to evaluate it. Even portfolios built without AI have lost their value because the general sentiment is that manual coding is obsolete.
reply
> Anyone can build a portfolio in a weekend

The funny thing about people is even though anyone can, so few do.

reply
Not if you have a portfolio project that has paying customers.

That is what they are looking for.

reply
I have a project with over 300 paying customer. It's on my CV and many times is part of an answer in the initial application form. I haven't gotten a single question about the project in a handful of interviews.
reply
That's surprising. As a hiring manager that's one of the first things I'd ask about and would drill down into your experiences with it.
reply
Well if you are operating a succesful business, it is not a portfolio project anymore.
reply
There are far more people successfully employed as developers than have achieved projects with even one token paying customer.
reply
> Not if you have a portfolio project that has paying customers.

Impossible to prove, trivial to lie about. Take note how many genuine startups lie about their recurring revenue or partnerships.

Let's say a candidate even sends you IRS statements, tax returns, corporate filings, bank transfer records.. How can you, as an interviewer, verify that those records haven't been fabricated? Or even if they are 100% legitimate, how can you verify that the clients who purchased their services haven't been coerced in some way? Aka getting a few dozen friends or family to subscribe to your app while never ever using it once. That candidate could show, say, $1000/month recurring revenue for 3-4 months, while having 0 genuine users. And just for the record, a LOT of startups use this method to boost their early traction. A lot.

reply
I have done this multiple times, both by hand and with coding agents. I'm not finding prospective hiring managers express any interest, even when I offer demos or repo access.
reply
Very wordy but counter productive advice IMO.

From my experience of interviewing candidates, I can conclude, nobody cares about your pet projects.

I was one of the few, who'd even look at a candidate's CV more than 5 minutes before the call, let alone, follow links and explore candidate's GitHub.

The hardest part is getting past the first stage, because it has nothing to do with your actual experience or skills. Latter stages are a lottery too, but at least you know the rules and can prepare. Hence the advice somewhere above to get in front of people who are already in the industry – is the best advice.

reply
In the past I would have agreed, I've had the same experience with interviewing and being interviewed. As in, interviewers were surprised when I mentioned I had an open-source project with a few stars related to the very same topic that they'd been grilling me about. I had assumed they were grilling me because it was right there on my resume and highly relevant to the job. This was ages ago, but I didn't get that job of course ;-)

Given that, I used to always make it a point to glance at the candidate's GitHub or pet projects and bring up any that seemed interesting, at least to make them feel seen.

But things are changing, and these are not pet projects. These are complete, working end-to-end products that (ideally) you've gotten actual users for. Maybe even paying users.

At which point, it could actually become a revenue source, and hence, an alternative path.

reply