Career Advice About Startups

Hello! Are there any websites to assist with evaluating startup offers (e.g. salary and equity)? Pave and Carta are focused on providing benchmarks for the offer-givers, not the offer-receivers. seems interesting, but I'm not sure how much I can trust it?

Is it possible to just use Pave / Carta without paying for it?

Thanks!

Since our company is so small (< 10 engineers), we do code reviews across platforms – so I review iOS and web code even though I’m an Android engineer.

I haven’t gotten any negative feedback on my code review yet, but I want to make sure I’m doing it properly. How can I suggest improvements on other engineer’s code, even if they’re on a different platform, or if they’re more senior than me?

I am a deep learning research engineer at an early stage autonomous driving startup and I just got an offer for a senior deep learning engineer in the autonomous team at Qualcomm. I am confused about it as compensation is low compared to industry standards but overall a bit higher from my current salary. (The base is quite low, but RSU's make up for the rest). The work is same what I do, so that will be nice.

I can either keep looking for other opportunities while staying at the startup or take this. I am not too happy with the offer but it is the best I have right now. I will be shifting to San Diego from NY and will also take a major hit in my social life.

Any suggestion on how the culture at Qualcomm is and how their machine learning and AI teams are? I am really confused if it will be worth it.

Hey Folks,

I have the famous question here : Big tech -> startup : Should I do it?

Context:

I have a pretty toxic leadership. I have even got offers internally, but the leadership played political and I didn't end up switching teams. Also to note, I was told that I have been given "meets most" or the lowest rating a person can get.

This was a pretty horrible, as I was in exceeds in my mid year. I am not sure why they are being nasty.

And rumor is that they will be letting folks with this rating go this month. ( All on blind, and some managers from other teams also confirmed, but I have not been given a last day yet)

Given this a context, I just want to see if I should take up a startup offer.

I have 10+ YOE, and I see that I am not getting as many calls as I used to just 2 years back. And the interviews are much more random. This makes me concerned.

I am not on visa. But moving from big tech -> start up is a huge paycut.

What do you suggest I do?

As someone with a background as a Senior Software Engineer at Meta, I’m curious about the team matching process at FAANG and similar companies. In my experience, team matching at Meta wasn’t heavily influenced by one’s past experience, except for specialized roles. However, I’ve heard that at companies like Google, it might be more challenging to join teams if there’s a significant gap between one’s background and the typical requirements of the role. Can anyone share insights or experiences regarding this?

I also regret missing an opportunity with Meta’s global traffic routing team, which was a great fit for my learning and growth (published cutting edge industry practices) but I was afraid of failing. As I look to re-enter the FAANG space, I’m concerned about the difficulties of joining high-growth teams when my background differs significantly from the norm. Any advice or perspectives on overcoming this challenge and seizing similar opportunities in the future would be highly valuable.

When I joined my current company, it was a standard 40 hour/week company. Since the end of last year, we’ve been told that we’re all expected to work 55-60 hours/week to get our startup to a successful state (get funding, retain current customers, attract new ones). I’m feeling extremely miserable from the change because the schedule doesn’t allow me to do all the other things that are important to me outside of work, such as spending time with family, cooking and working out regularly, and dedicating time to my hobbies. I have subscribed to newsletters for years to keep up with how the javascript and react worlds are changing, but have stopped reading them. I feel like the work hours have made me less curious about keeping up with tech and growing, which is the thing that I used to like most about this career.

We’re asked to track and report our hours working on tickets, and any time we fall short of expectations it comes up in our weekly one on one with our manager. It’s making me want to leave, but the market is tough, I haven’t interviewed in years and never done DSA or system design questions, and it’s hard to start with the schedule I have, because again I’m already sacrificing time with my family for this job and don’t want to sacrifice more. It’s crazy how much the extra 15-20 hours per week is costing me emotionally.

How do I get out of a situation like this? I don’t have enough savings to fall back on, my wife doesn’t work, and my state doesn’t provide Medicaid even to households with no income.

I've got a performance review coming up. It's not my first one at the company, but it will be the first time I'll be actively pushing for a promotion. It's also the first review with a new format, where we'll need to align our accomplishments with company values and our roles' "competencies"—10 in total, which seems like quite a lot to me. In light of that, I have a few questions:

1. How long should a self-review generally be?
2. Should I cover all or as many of these values and competencies as I can, or should I focus on just a few of them?
3. Should I prioritize quality over quantity and share only the strongest achievements? Or does it make sense to include both the biggest achievements and just good ones?

I would love to hear what others here have learned while working with their PMs past and present. I have brushed shoulders with a few and only closely worked with two PMs in our sort-of-cross-functional team, in my career thus far. They are both likable people but it took me a long time to realize that their feature requests were poorly scoped, lacking crucial details, and oftentimes had no acceptance criteria. In hindsight, I am not sure why none of the IC's with years under their belt never really spoke up about that (which led me to believe that was just the way things were).

Fortunately, our goals with Product are better aligned these days and our relationship has been healthy, so we are pretty comfortable give/taking feedback during Sprint Retros, so much of said issues have diminished. However, the lack of clarity in the tickets is still present from time to time, and now when I notice this, it fatigues me to know that I will have to set aside time to hop on a call and ask them for information (which in my mind, should already have been in the ticket?). I see most of my teammates having to do this as well, but I have not noticed their irritation over it. Sometimes, I wonder if I am wishing for an ideal that is rare or does not exist.

Mini rant aside, I would love to know some of your guys's good/bad experiences with Product and how you navigated through them. (i.e. What made it smooth/difficult to work with them? What steps did you take to mitigate the issues?) Thank you!

I work at a relatively small private company, and we spend pretty much all of our time churning out features as customers request them. I'm wondering if it makes sense to also spend some time digging into data to better understand user behavior. I'm trying to find ways to add value to the company besides just feature work.

I am looking for new opportunities and based on what I am seeing on Taro. My strategy so far has been.

1. Create and polish resume
2. Prep for DSA and System Design
3. Apply to jobs.

This is the end of week 2. 8 Applications, 2 Rejections and not heard back from the rest.

So far I have been applying through LinkedIn and Otta only. I have intentionally avoided and not reached out for personal references. My thinking has been, that I don't want to waste the guaranteed interview opportunity if I am not ready.

My target at the moment is that I should be able to complete 90% of the grind 75 leetcode questions and at least a few system design mocks.

My questions to the community:

1. What are other good job listing services?
2. Is my approach sound or should I change my strategy?

With every rejection, I try to remind myself what said. "We can only do what is in our control; that is to continue preparing."

I have 2 core goals:

1. Learn from the best engineers and pick up as many skills from them as possible
2. Become a founder

Given that, should I work on side projects full-time and apply to incubators or continue doing internships like my current one and doing side projects on the side?

In my organization, there are SDE roles till level 4, and then on top of that, you become an EM. Many times, an SDE 3/4 (who is considered a technical lead) gives tasks or creates the sprint. But then when the junior engineer goes to an EM to show their work, the EM changes the entire approach or assigns vague tasks.

This impacts the velocity of the sprint. I do want to understand: How do I put it out to the upper management such that this doesn't happen? Also, should an EM make technical decisions in this way?

Since I’ve only worked in smaller companies, I sometimes feel uncertain about my abilities as an engineer compared to FAANG engineers. How can I identify the gaps between my current skill set and those of FAANG companies?

Large tech companies used to provide a sense of stability and financial security, but with falling stock prices and layoffs everywhere I wonder if joining a hyper growth late-stage startup with a growing business and hefty pre-ipo RSUs is a better choice?

I am working at a 2 year old startup that has just launched its product a few months ago. The launch was considered a failure because the product has so many issues and customer complaints. Some customers even stated that they prefer the competitor product.

After being here for less than 6 months, I observed that the company has a culture of rushing everything with lack of planning and resources/manpower to execute their vision. None of the upper management has business experience in this exact product, they only have experience in tangentially related product. Also, prior to the formation of the current engineering team, the company hired an overseas vendor that overpromised a 6 months project that dragged out into 2 years. That is the main reason the current engineering team I am part of is built: to replace the vendors. The investors are known to be very profit-oriented right from the start, and they are also funding another startup that has the exact same product as my company, although this startup will not be launching anything until next year. The combination of inexperienced upper management and culture of rushing things lead to product failure. Thankfully, I think the atmosphere in the office is still pretty positive and laid-back. People are not pointing fingers and they still do their best to recover from their mistakes and prepare for future initiatives.

My manager has stated from the very first time I join the company that he prioritizes quality over speed, and given our previous product failure by the vendor, I agree that this is the solution. However, the Product Manager doesn't agree with this and he pushes us to prioritize speed over quality, even if that's the exact mindset that leads to our product failure. The rest of the upper management seems to adopt the same mindset of quick fixes and rushing, and the most alarming part is that we don't seem to have identified our core users, so I'm not sure if our previous launch has actually taught us anything. Also, I noticed that the Product Manager is lacking competencies in some key areas. I expect a PM to be someone who can not only have a vision on what the product would grow into, but also someone who can do analytics, business projections, and prioritize the most impactful projects for the team. In our daily interactions, he seems to be someone who just passes words from one person to another without doing any substantial management. This is slowly leading to resentment from my manager towards the PM because the team is slowly being overwhelmed with unimpactful tasks that hinder our future milestones.

My questions are:

1. Which direction should I follow? My manager's or the PM's (majority)?
2. Should I consider this a sign for me to look for new company? Or is this still normal and workable? If yes, what kind of role / actions should I take in this situation?
3. How should I convey this in my 1-1 to my manager?

I'm in a difficult situation right now and feel I need some time off to recover and manage, but am also concerned with optics.

I've been interviewing for new roles recently and spent my time off over the holidays (~2 weeks) preparing for a particularly stressful onsite interview. The team I was originally interviewing with no longer has an opening and I'm stuck waiting for headcount to open up and find a new team.

The stress of this situation has been taking a toll on me mentally and physically, and I've been dealing with a lot of health issues over the last month. I think it would be best for me to take at least a couple of weeks off to help reduce my stress and focus on maintaining my health. This isn't extremely extended, but amounts to more like a month off when factoring the recent 2 weeks off for the holidays.

After writing this out, it seems more cut-and-dry that I need to just ask and cite the health issues. I'd be curious to hear how others have navigated asking for extended time off.

As a founder of an early-stage startup, what are the top things you look for in your first five engineering hires? Are you searching for people who can handle a bit of everything, or do you prefer specialists in key areas? How do you balance technical skills with ensuring they fit well with your company's culture and vision?

Besides their technical know-how, what personal qualities are most important to you in these early hires? Do you value problem-solving skills and creativity over past experience in similar roles or industries? How crucial are soft skills like communication and adaptability, given the fast-paced and ever-changing nature of startups? And finally, how do you make sure these first hires will not only meet immediate project needs but also grow with the company as it expands?

I am a recent graduate who just started a new position at a small startup. Along my short journey thus far, I have connected with a few people outside my company whom I have asked for career advice and whom I think could be great mentors for me. However, I would like to formalize, or start formalizing, our premature (I have only spoken to them 1-2 times in total) relationship which currently consists solely of advice-seeking to a mentor/mentee relationship. What is the best way to approach this? It feels inappropriate and unprofessional to ask them to "be my mentor please!" Any advice is appreciated. I expect the answer here to depend on whether the mentor figure is outside or inside one's company since if they are outside (as in my case) it is much less of an expectation for them to give me their time free of charge.

I have worked primarily on the backend, but my company now has assigned me features concerning our Android app, which is built mainly on XML for layouts & Java.

How can I get started on this, be productive & contribute effectively?
Thanks.

Context:
Over a conflict, an aggressive conversation occurred between the engineering manager towards the business lead. From the point of experience, there are ten years more on the side of the BL. Everything happened over Slack over the weekend.

Due to this, today, the entire engineering team had a 1-1 to skip meeting with HR to give our statements about the issue.

What usually happens after this meeting?

I've been working at a AI startup for around 4 months now, it ran out of money and cannot pay salaries anymore. I feel it's a pity the tool we build can do some amazing things, new customer onboarded and other customer uses it daily. Also our teamwork is in flow, we can do a ton of work in short time.

The company hasn't secured new funding and there's a breakup happening with previous investor. Creating a new company..
Previous company was in Europe now the new company is a US entity

From the lead I hear that there's much interest in funding us, but we need a cap table and to be US entity, which just happened. But they've already been looking for funding for over 1 month and haven't gotten the required funding.

This is my first startup and not sure what this means, It would be a pity if we dissolved now, cause team is great, there's some user traction, and our product are becoming pretty awesome.

I've only ever coded in js/ts; however, as I seek to grow my skills in react-native I've been trying to learn swift to deal with bridging. However, after coding a few hours in swift when I swapped back its like my brain stopped working and simple stuff I couldn't remember the syntax. After working in it again it kinda went back to normal; but, is this something that is normal or goes away with practice?

I am building an iOS team as the lead engineer. Here are the iOS roles I'm looking to fill based on my assessment of the product's requirements:

• Number 2 (capable of handling 60-80+% of my tasks as my right hand)
• Designer Engineer (specializes in dealing with design layouts)
• Real-Time Data Engineer (specializes in dealing with real-time data)
• Automated Testing Engineer (specializes in code coverage and unit testing)
• Bug Squash Engineer (generally a more junior engineer to address menial tasks)

What are your thoughts and anything I might be blindsided on?

Hey folks,

I'm currently facing a tough decision - whether to ask for a raise at my current company. I am unsure if it's the right time to do so or not. Here's a little context to help you understand my situation

My timeline in the company:

• In 2023
  • I joined the company as a Sr SWE II (L4)
  • I joined the company nine months ago on August 23'
  • I made it to the second review cycle of the year (mid-October), and I got a "Consistently meeting expectations." My manager then said that he was very impressed that I managed to get so much done in that short time and that he could see strong signs of a Staff Engineer (L5) in me.
  • I shipped the most important project in Q4, 2023, on time. I even ended up as the technical lead of that project (the Staff engineer in that project got pip-ed, but that's another story)
• In 2024:
  • I mentored a Sr SWE I (L3) on her first project as a lead.
  • I'm the lead of the web working group
  • I'm interviewing candidates almost on a weekly basis
  • I'm one of the owners of the Design System initiative
  • I just got a "Consistently exceeding expectations" in our current review cycle. I've been praised for how easy it is to work with me, my technical quality, my communication skills, and my thoughtful PR reviews. And that I should keep working on my influence across the organization.

How things are right now:

• My previous manager quit to join another startup, and I got an interim manager (we're hiring another manager for my team)
• I ended up talking about salary adjustments with my previous manager the other day (there, I didn't ask for a raise; it was just a casual conversation). He told me that the company does a compensation review every January and that I wasn't considered for the one that happened in January 2024 because I didn't join earlier than July 2023.
• The next performance review will happen in mid-Oct 2024.
• I will be leading a new tiger team (6 engs) until the end of Q2.

Questions I have right now:

• Is this the right time to ask for a raise?
• I've never asked for a raise.
• I know for a fact that an L3 has a pretty similar (<5%) salary to me, and I know that another L4 has a >5% salary than me.
• Should I wait until I finish this new project, the next performance review, or my first anniversary?
• We're in the hockey stick growth stage.
• I also really like working here, and the market has been bad lately.

Thanks!