fzwang

IMO, the proposed 5/5 compensation is a bit high. If I understand correctly, he's essentially asking for approx $1.2M total comp package for raising $4M. I'd suggest 2.5% and 2.5%, or some combination of.

There are terms other than valuation which are very important (board rep, liquidity pref, etc). Have you talked about what are the must haves and deal breakers for you and your team?

IME, the bigger issue in the long run with this situation is that you, the founders, do not have a direct relationship with the investors. These investors will most likely be "his" investors, which positions him as a key intermediary. This will be a problem in the future when you need to manage them and must go through a middle man.

The CEO should ideally lead the pitch and an advisor can help with coaching, networking, and strategy (and be well compensated for it). I think any competent VC will want to see that at least one of the founders can do sales.

Sorry to hear that you're going through this. I work with other students/recent grads going through the same thing. A few suggestions:

1) To echo some of the other comments here, getting a regular routine will help you get into better habits. Good sleep, regular exercise, and limited social media etc will help with your mood.

2) The setbacks are situational, not dispositional. It really is a shit job market and you likely don't know how to properly signal yet (ie. sell yourself to others). And to make things even worse, brute force ATS grinding is now even less effective since everyone can now game the systems and generate a plausibly good-looking coherent resume using AI.

3) IMO, one mistake I see often is that students think jobs are the only way to gain experience. This is not true. You really have to be constantly learning new things on your own. Your university education is not enough. This means working on projects specifically for learning purposes. I'd suggest you alternate between learning-mode and applying-mode, where you spend 2-3 months just working on shipping a complete project, then focusing on applying to jobs for another 2-3 months, get feedback and rinse and repeat. You can use the learn-mode time to adapt to feedback. I think this will yield better results than applying over and over again hoping for different results.

Anyways, feel free to reach out. As others have said, you're beating yourself up too much. You'll figure it out and find a way through these setbacks. The important thing atm is not to spiral into a vicious cycle. I applaud you even airing this on HN, as it's much much better than sulking alone.

I used to work in VC and have dealth with university commercialization/IP offices.

1) If it's serious, you need to lawyer up. It might not be now but if you can get some investors involved they could help with getting legal resources. If it's medical devices, you'll need investors anyways. One issue is this gives investors a lot of leverage to negotiate their interests against you.

2) The university office absolutely does not care about how "little" they gave you. Their perspective will be they've given you plenty, as office/lab space and anything else were not part of the deal (unless you have it in writing), and they've subsidized your funding. It's not "fair" but it is what it is.

3) This scenario is quite common, and one of reasons I tell grad students to negotiate this stuff first and pick your school wisely. Some schools are way better than others in allowing their academic staff commercial freedom.

4) You can make it a PR issue for them, to push the narrative of "university stifles innovation via obscure bureaucracy" but it's a risky strategy.

There are usually always room to negotiate/maneuvre, but you need the right contacts and political support within the university to pull it off.

Good luck!

Location: Toronto, Canada

Remote: Yes

Willing to relocate: No

Technologies: N/A

Website: www.divepod.to

Email: frank@divepod.to

I'm building out a new comp sci education program based on an advisory model. It is intended to complement instructor-lead models (like traditional schools/universities), with more emphasis on self-direction and real-world exposure. Part of the motivation is to address talent development problems in startups when I worked in VC and in hiring for projects for my own company. These issues are exacerbated nowadays with AI.

I'm the lead advisor and currently looking to recruit students to work with personally, ideally those who are in HS or university but is bored and/or feel like they are not learning useful/interesting things. Bonus if they have an interest in exploring entrepreneurship. I have a background in data engineering, VC, and ML R&D.

From my experience and talking to other founders/engineers ...

1) It's good to analyze what's the source of the burn-out. In many instances, it's not exactly exhaustion per se, but lack of meaning in what they are doing beyond the money. There are acute stressors, like coming out of an intense sprint, and chronic stressors, like not knowing why you're even doing this. If you had fuck-you money, what would you be doing long-term instead? beyond take a vacation, buy a house, etc.

2) Learning to say no to things. Let go of "hero" mode. Good enough for now is good enough for now. Cut down on complexity to reduce cognitive load. Really assess which things you do are real and which are performative.

3) Better understand how work fits in your long term goals. Having worked in VC, a lot of advice for founders are very investor-centric. The core of the thinking is that some sort of exit will solve all your problems, and is worth grinding for. I see many founders become entrepreneurs to "work for themselves" and not be a corp wage-slave, just to become a VC grind-slave. Their health falters, their personal life implodes (divorce/breakups), and they've no genuine friendships (just business acquaintances). When they do get to a good financial exit, they're still miserable. Do try to make the company/product building process enjoyable too. Sometimes it means slowing down, smell the roses, think things through to avoid problems.

Overall, the right advice is very situational. The most important part may be talking out loud to someone you trust about it. Sometimes just verbalizing it helps.

I work with students and junior engs.

Personally, I'd avoid using AI tools for learning atm.

1) As a learning path planning tool, I find LLM tools are very good at creating learning plans and next steps for popular concepts. However, the convenience of the tool also skips over a lot of accidental discovery/exposure, which IMO is useful in the long run in building out broader contextual awareness. The students following an AI plan only knows about the things in immediate vincitiy. Whereas more traditional methods, like a web search (use someting like Kagi, not Google) reveals more advanced stuff which they don't know yet, but plants a seed in their brains.

With the right prompting system, you can probably mitigate some of these issues, but atm I find the general trend is people want short fast answers.

2) For actual coding I'd discourage it. For people to learn quickly they have to build stuff from scratch so they develop the right mental models. Writing code manually is a good check on their understanding. When the work becomes boring/tedious they can offload it to AI tools.

Overall, my experience has been that the AI tools are useful in the short term, but too much reliance amputates a lot of the valuable, but hard to measure, learning experiences. If the goal is to form the right mental model of concepts in the human who is learning, then bypassing some of the "work" and frustration by letting AI do most of the planning and "thinking" actually harms the learning process.

It seems like the cashflow situation will rule out some options, at least for the moment, like boostrapping etc. Contracting could be a temporary option, esp for US companies that need in-person support with good language skills. This would blunt some of the competition from abroad.

Regarding learning "out of the tar-pit", it's hard to give out specifics without knowing more details about your experiences. But it might be worthwhile to reach out to other senior engineers in your network, not to ask for a job, but to ask for advice about switching from entrepreneur/founder to employee. It could be a good way to build rapport and identify what you should be learning next.

Your health obviously takes priorty over everything else. Medical problems can really push you into despair if left unaddressed. Money you can always make back later.

From your comments, it seems like there's a lot of internal and external issues you're dealing with. Internally, your sense of self worth is very much tied to your compensation/wealth. The recent rejections have triggered anxiety / negative self-reflection. The lack of a job/income is really straining your confidence.

Externally ...

1) It's actually a shit job market.

2) Your startup experiences don't really help signal your skillset as an employee. There's a sorta "founder tax" you're paying.

3) COVID, remote work, and new supplies of CS grads have changed the labour dynamics to depress wages. The top 20% may be doing ok, but the bottom 80% are getting diluted.

If I were you I'd consider a few things:

- Really think about what's a good/meaningful life to you. Volunteer/do something useful for other people (ex. a non-profit) to build up confidence again.

- Recognize your technical skillset may not be as "senior" as you think, since you had to expend valuable time learning other skills as an entrepreneur. It might mean more learning, building, leetcode grinding, interview prep, etc, before you can land the role. Concurrently, you can think about how to better communicate all the other useful things you've learned at a startup.

- If you enjoyed the startup experience, but concerned about the grind, then you don't have to build high growth businesses that require the 996 mentality. Boostrapping and organically growing a niche product may be more aligned with your skillset/goals.

Often solo-founders build very niche apps/SaaS which they already have a personal network for or can target smaller platforms and business networks for marketing/distribution. You can stay small and do very well.

The larger platforms are usually too saturated to be effective. In my experience, generally not a good return on $/time.

If you haven't already, check out the HTMX community [1].

I think there's some recognition that a lot of SPAs didn't need to be SPAs in the first place. At the end of the day, you're just submitting a form for a CRUD app. Good ol' HTML + a sprinkle of JS was enough for most use cases. CSS has evolved to take away some of the stuff that required JS before.

At the moment, I don't think there's really any strong incentives to cut down the complexity of apps by moving away from SPAs. There's real job security in creating complexity. And in some big orgs it's unavoidable. It can change when developers are more aligned with long term outcomes (ex. a product that they own), which usually means smaller projects.

[1] https://htmx.org/

Generally, less classrooms/traditional schooling, and more exposure to the real world. Taking more time to meet people and expand the social horizons.

I feel like I just didn't know what I didn't know. And I was making decisions on very little experience/information. The "adults"/"experts" didn't know what they were talking about or at least were not aware of their own biases/limitations.

Looking back, almost all the useful/important things I learned were self-directed.

It's an interesting conundrum, where everyone knows the system is bs but no one wants to take the first step. Hypothetically, some possible scenarios:

1) An external event, like a war, that stress test the credentials and to force selection based on outcomes. 2) Some sort of monetary benefit for employers, like extended internships for high schoolers. Assuming it's cheaper/more effective for an employer to train their workforce from scratch than pay the full salary of a recent grad. 3) A new field, where credentials haven't been established yet.

There are obv caveats to all of these. And they don't address the question of what a formal education is supposed to accomplish. At some point, it was supposed to be to train "better citizens". And that shouldn't be dictated by employers, imo. But nowadays it seems like the purpose is to get a job and survive.

I think this is the lack of accountability that I find frustrating in the education system. If the student gets a bad experience, they are always blamed first and the role of the teacher/professor/university is never questioned.

I agree with your general assessment, but not sure if the blame could be placed on employers mostly/entirely. They're also limited by bounded rationality and cannot (or should not) dictate what the purpose of an education should be. There's such diffusal of accountability that no one is really designing the system, just reacting to it. To your point, the system just do what it does. The ultimate unaccountability machine, per Dan Davies [1].

I think we're witnessing the collapse of the university value proposition. In the decades post WW2, the attendance/competition within universities was quite modest compared to today. Relatively fewer people went, and it was essentially a social class sorter, with a liberal education sprinkled throughout. This actually creates a better learning environment, as once you're "in", you can focus on the experience. Nowadays, the university is just another hamster wheel in the grind, in a never-ending arms race against the sea of other students/degrees/credentials. Failure to deliver results means you didn't consume enough, and must consume more. Eventually this dilutes the value of the degree, both from a signaling and a financial perspective. It seems like we're in the peak enshitification stage of higher ed.

For employers, requiring a degree doesn't cost them anything. So they're happy to keep piling on the requirements. I guess the question is what type of employers would actually be the first to decouple their recruiting/hiring from credentialism and rely on other metrics of competency?

[1]https://en.wikipedia.org/wiki/The_Unaccountability_Machine

This is an interesting question. I work with students (older teens/young adults) and they are dealing with similar issues. It seems like the world's expectations shifted very quickly under their feet.

I don't think anyone knows the answer. As a hiring manager, I definitely put less weight on generic CRUD apps etc nowadays. You can argue that people can actually just copy and paste from SO before, and that's true, but even with that you had to have some knowledge so integrate what you've copied. With AI assist, the process is orders of magnitude easier, as you can just re-try prompts etc.

What I look for instead is more information on the process of creation, which usually means examining their writing. How did they get the idea? how did they think about what features to build? But even this is not immune to AI contamination.

Overall, I think we're likely to move towards more reliance on verifiable longitudinal data rather than "spot checks". It's much more difficult/challenging to re-create for "portfolio cheaters", and easier for authentic applicants. I get my students to write a dev journal which I verify, and use that as part of a private portfolio that we can share with potential employers.

Overall, I'd say the vetting process is much more onerous on both sides and portfolios will now need proof-of-authenticity.

Sorry to hear that. This info does make it easier to rule out some options.

As a hiring manager, I'm usually not looking for a specific skillset from recent grads, but whether they are competent learners and have good communication skills. Both of these attributes means they can quickly adapt and more likely to contribute (or at least be less of a burden in the short run).

From your other posts, I'd recommend you work on your writing (English and your local language) to be more professional. Don't use AI writing, as you'd lose your writing "voice" and others will judge you for it.

For networking, I'd reach out to senior engineers in your area or prior companies to ask for advice on what's important to learn that you didn't learn in college. Don't ask for a job, as that could send their guards up. Follow through with their advice and update them regularly, every few weeks. The goal would be to show them you're a quick learner and can communicate well. They're more likely to recognize an opportunity and send a lead your way. It may not be with their current company, but a friend's company etc. Many jobs are shopped around informally via vetted social relationships before being shown in public.

If you're really strapped for $$, taking on any tech-adjacent job could be useful, including customer support roles where you can practice your communication skills.

If your financial situation allows it, I'd recommend you take some time off to recharge and reflect on what you'd want to do next. You've likely come off the hamster wheel, so to speak, and now is sorta lost. All the regular structures/incentives you relied on before is gone and there are uncertainties everywhere.

If you're not in a good financial position, stabilizing your finances would be the first priority. I would focus on developing your professional networks and reaching out to past colleagues etc for job leads/referrals. You're at a stage where you've very little to lose and everything to gain from any interaction with reality/real-world problems.

Working on AI/vibe-coding, esp understanding the fundamentals, will be advantageous as everyone is still figuring things out. Your lack of experience won't hurt you as much, since no one really have any. Be careful with using too much AI assistance for learning, as it can actually slow you down and give you a feeling of compentency/productivity without deep understanding.

Good luck!

This. For me, it was a few students/junior folks I know mentioned that they posted on here and reddit, but got no responses. So now I make an effort to comment/respond to new posts, esp AskHN.

I agree. Imo, #2 is becoming more of an emphasis over time. Teacher don't have much time/energy to pursue #1. Eventually, most of them stop caring and rely on testing metrics because that's what the admins want.

It's amazing what kids can learn if they just spent a little bit of time with a 1-on-1 instructor/advisor. The anxiety you mentioned can be crippling and something I deal with regularly. Even some of the "gifted" kids (perhaps due to the expectations) have trouble avoiding the trap of overindexing on productivity/competency metrics. They're not even self aware of it, just accepts it as normal.

For most kids I have to go through the exercise of separating these two concerns, the learning part and the signaling part, early so they can put things in perspective.

I run a program for high schoolers to emphasize this skill. However, the entire K-University pipeline is designed around credentialism. Ie. do whatever you need to, cram/cheat/regurgitate, to get the rubber stamp. It's really hard to communicate the importance of self-directed education/learning how to learn when the vast majority of students' formal educational experiences tell them otherwise. Very frustrating but perhaps things are changing ...

I'm glad you made the commitment to change something in your life. Your previous job, and perhaps the way you approached it, was obviously not healthy.

1) The degree anxiety is understandable, but just in your head. I run a comp sci program for high schoolers as an replacement for universities. They don't get a degree but must learn how to signal they are capable. It's a skillset that most people don't learn until later in their careers. In your case, you likely have accumulated a number of valuable skills in your previous job. Since you haven't switched jobs, you haven't had much practice in communicating your skills to potential employers. Most engineers I know hate this, but it's sales/persuasion, and it's unavoidable and beneficial for you in the long-run. Take the perspective that you don't have a skill issue, but a signaling issue.

2) RE: AI - I would learn the fundamentals, only if you're interested in the engineering aspect of it, and implement some toy projects just to keep learning. Try vibe coding, it's not going to kill you haha. Learn about its benefits and limitations so you can at least comment intelligently if it comes up.

3) Shipping projects is hard psychologically unless you've developed discipline or there are other constraints/deadlines. If I were you, I'd work on projects in a more social manner. That means building with other engineers, talking to people who would benefit from what you're building, or just helping out existing communities. The socialization would help keep your spirits up. It's also the best way to build relationships and open other opportunities.

4) Hiring/recruiting is going through big changes now, partially due to the rise of AI generated applications. Building trust via other channels is going to be much more important moving forward. We've had to more or less turn off all inbound hiring and rely on our vetted professional networks due to the massive glut of applications. Job search is brutal now, but it's just as bad on the hiring side. We're going through changes were the old methods don't work anymore, and the new haven't been figured out yet.

Good luck!

I second this. If you're trying to signal just on "I can code", then there will be fewer differentiating factors between you and younger people.

Typically, I don't think of software dev as an "industry" in itself, unless you're talking about dev tools etc, but that many industries depend on strong software. Your best bet is to target software problems related to your prior job. This way, your skillsets complement each other. You may not be the best at either side, but your ability to integrate the two could be a strong pt.

I work with students (older teens/early 20s) and I understand the feeling of fear/despair. The reality is there are things you can't change and you should focus on those that you can. We're still not sure what is the impact of this generation of AI and it's hard to get an unbiased view amongst the hype. There are non-AI factors (ZIRP, Post-COVID, economic/demographic trends) that are likely contributing much more to the poor hiring conditions we're experiencing. Some comments/suggestions:

1) Take the emotion out of it. AI is just a technology and you don't have to love/hate it. Do try to understand it. Even if you are a skeptic of the LLM/AGI hype, the technology underneath it all is still quite fascinating. It surprized a lot of technologists.

2) Don't count on your degree. I think we're in this weird period where the traditional institutions are slowly collapsing, but the new hasn't been invented/popularized. Do finish your degree, but take time to hedge your bets and gain experiences outside of school. The great thing about being in your stage of life is you have very little to lose and a lot to gain from risk-taking. If you're constantly surrounded by your peers and academics, you'll not have the exposure to reality that you'd need to adapt.

3) Biggest skill that's missing, esp in Gen Z and not taught in higher ed, is how to communicate/signal to others like potential future employers. Beyond the superficial stuff like how to craft resume etc, but genuinely building your professional network. Who you know really matters. And not in the casual/family/we-play-golf-together sense, but out of professional respect. Make it a habit to reach out to engineers you admire and just ask for advice and interesting trends they're seeing (ex. in cybersecurity). When you do it as a student, and not as a job/favor-seeker, it changes the social dynamics. You'd be surprized how many would not only respond but talk your ears off. If they ignore you, big whoop, don't take it personally and just move on. A small minority of these people could make a huge impact on your life and career.

Some more tactical stuff:

- I'd assume you already know this, but resist the urge to use AI to learn. I've banned AI assistants for our junior engineers because they really slow down learning. It feels faster but you actually retain very little. We're re-discovering that doing things manually has a ton of long-term benefits that are hard to capture.

- Do take some effort to understand how businesses work. You'll likely be working in one and it's in your interest to understand the flow of money, incentive structures, and how businesses make decisions.

- Learn to eat well and exercise. It'll help boost your mood and not get bogged down in despair. Find ways to keep your spirit up for the long-term. Diversify your information diet away from TikTok, Instagram, and social media in general. Young people today have the dubious honor of being the first generation to have to fight off mass algorithmic addiction. Try to talk to more people in person to get a better sense of reality.

That's pretty normal. The culture in the Bay area is quite unique in the early suppression of any "common"/status-quo sense. So even silly/"stupid" ideas are entertained.

If you're building anywhere else, I think you have to be more active in curating who you surround yourself with. Most other people are on salaries building/supporting businesses that are proven with low risk, so their mindset to life is quite different. There are risk takers in any city, but it takes more effort to find them.

When I worked in VC, I really enjoyed talking to builders from "unlikely" places, middle of nowhere Kansas, Atlantic Canada etc. They had to overcome much more social resistance to work on their ideas.

The route they use is pretty good for indoor runs when the weather or slush/ice gets bad. Mix of stairs + flat stretches. The only downside is that parts of the route are gated by doors which you have to open manually, but def a first world problem.

We also have a 5K race in the PATH! [1]

In the winter the tunnels are amazing for commute.

[1] https://www.bougebouge.com/en/shop/events/5km-bougebouge-tor...

All kids have the instinct to learn, but it's not a set-and-forget dynamic where you can just leave them with a computer/gadget. Their interests and curiousity feed off of those around them. Having access to "true play" and playmates are critical [1]. For example, you can introduce them to Scratch [2], make a small game together, and let them propose new games to make. Get their friends involved too.

But's not going to be spontaneous until you create the right environment, which includes not just physical things like books/etc, but the social support structures. It takes a lot of work and care.

[1] https://www.goodreads.com/book/show/15843125-free-to-learn

[2] https://scratch.mit.edu/

Not in SF, but talked to a number of Canadian founders when I worked in VC.

It depends on your financial/legal situation, those of your co-founders(if any), and what types of "returns" you are referring to by ROI.

1) The obvious benefit is to get plugged into the network there. You don't need to be there all the time to accomplish this. Waterloo, and Canada in general, is still cheaper COL wise compared to Bay area/NYC etc, so it'll help with your burn rate to build in Waterloo. Most people's burn rate at least doubled when they move themselves or their team. Flying in every few months could be enough.

2) If you're convinced you need to move to the Bay area, it might be useful to incorporate your business in the US and look at your visa options. I think there's a regular Ask HN about immigration issues. You likely need to do this anyways if you're fundraising in the US. The typical setup is some sort of Delaware corp with a Canadian subsidiary, if needed. IANAL and you should get professional advice here.

3) Get married to a US citizen and your personal visa issues will be solved lol.

I talked to a number of people who used AI to start their business in the early stages.

Some of the positive things I see is that vibe coding is pretty powerful for non-technical people. If you adopt the AI-as-floor-raiser mindset, it removes a major barrier for experimentation for people who don't know how to program. Some go a bit overboard and think they don't need engineers at all, but they eventually realize they still do. People either throw out the vibe coded prototypes or had to rebuilt them "properly". Some technical folks appreciate having this option available to non-tech people, as it shortens the experimentation cycle and acts like a filter to weed out bad ideas. One interesting new dynamic is that we could be seeing a new wave of fast-follower builders, where a good engineering team can replicate vibe-coded products quickly, in a way that's more durable and without reliability issues.

Using LLMs for market research is pretty mixed. The good cases seems to be using it for writing generic routine stuff, ie things that are not core to your business/product, but just need to exist. The bad is somehow expecting ChatGPT to identify novel business ideas. It seems like one of the major benefits of chatbots is actually forcing you to write down your ideas. For example, some of the LLM generated "ideas" are pretty generic and run of the mill stuff you'd find anywhere. But it was interesting to review the prompts and chat history, as a human reviewer, to get a sense of what the person is trying to ask. For example, when I work with students, it's great to see their chat/prompt history to "reveal" their thinking process. It works the same w/ entrepreneurs vetting ideas. It'd be interesting to have a highly hallucinogenic model just as an idea mixer.

VCs are going to look at a solo technical founder, and ask:

* Are they going to have an interest in the business side? If not, they may ignore/be unaware of problems that are existential to the company.

* Will they have the capacity to deal with non-tech issues? Running a company, esp a fast growing company, is too much work for one person to handle.

* Can they attract other talent to work for them? If they're a solo, are they difficult to work with/for?

It'd be good to address some of these underlying issues, rather than check the box.

* As you mentioned, having previous success helps alleviate some of the concerns.

* If your product is growing very quickly, they may take the risk.

* Finding another potential cofounder organically as a pre-condition for funding. VCs will rarely force you to find a co-founder. That might actually introduce further friction into the team and risk the investment. The hope would be for you to find another person with whom you have good working relationships, which is the key. Even if they're also technically inclined, they can be trained to handle the other sides of the business. Generally speaking, it's easier to train a tech founder on sales/business skills, rather than vice-versa.

Personally, I'd recommend you continue building, but with the intent to find other folks who are also interested in the product/business. It'll be good for you whether you decide to get venture fund or not.