Another alternative is contracting. Those who hire contractors usually don't have the manpower to test extensively, and they're more likely to trust you to deliver. Or not care that much because you'll be working on a non-core element.
I had the same idea about startups but have failed numerous technical interviews for positions I was probably overqualified for. Even asked a few for accommodations for my ASD/ADHD in testing but no go.
Some have a loose idea of what they want but need someone to guide them on what is or isn't possible. There's room for mistakes, and some flexibility.
I know about HN's "Who is hiring?" post but I'm interested in other sources too.
Same meat grinder approach to hiring a perm.
Many are those are dead end projects that never get off the ground, or don't have enough budget for a marketing team and a full MVP. Many are part time founders who make good money and want to throw money at a side project, but aren't fully focused. There's a lot of downsides to the path too.
How do you propose to demonstrate your "track record" without a technical interview?
And my LinkedIn history
And a resume
So does everyone else (well...maybe minus the blog)
And yet people lie (or don't tell the truth) on their resume and LI profiles all the danged time
when I interview for senior positions, I'm instantly turned off when I start getting trivia questions related to things that are clearly documented (like "which config file option does X") whereas situational or scenario-based questions are highly relevant and useful
As I wrote over a decade ago in how I do interviews[0],
>What I try to NEVER ask:
> “trivia” questions – I bet there are C questions even K&R couldn’t answer > - I guarantee I can ask you a question about your area of expertise you cannot answer…just like I guarantee you could do the same to me > - since that is the case, trivia questions are pretty pointless, and more of an ego stroke to the asker than anything else > pointless “MindTrap“, lateral-thinking questions - riddles are fun – but only add to the stress of the interview (like “why are manhole covers round”) > pointless problem-solving and estimation problems > - for example, “how would you move Mt Fuji”, or “how many gallons of water flow into New York Harbor from the Hudson River per hour” > - estimation problems are wonderful tools and games to play, but not in an interview
The best questions are practical application questions based on scenarios (real or plausibly-imagined) that discover what assumptions you make, what help you want/need, etc
----------------
[0] https://antipaucity.com/2011/10/03/doing-technical-phone-scr...
I nail any conversation that is just about approach or decision making. I could talk about software and the theories behind it allll day long. The problems start with the technical test.
100% this. I've administered close to 30 technical interviews and this was generally my approach as well. This is what surprised me when interviewing at other places. I didn't seem to get the same accommodations I was used to giving.
