How do you decide which early-stage startup to join?

A thread. Photo by Melissa Keizer on Unsplash.
There are key factors to consider when choosing the early-stage start-up you'll join:

- The Team
- The Market
- The Product
- The Culture
- The Stage of the Company

The decision to join a start-up should be based on a combination of these factors and your personal goals.
As a developer in an early-stage start-up, you have to truly believe in its mission as you’ll be so involved in it.

Therefore, you need to assess the relevance of the project for you (and its viability) before joining the company.

To do so, focus on these 3 specific aspects 👇
1️⃣  Your confidence in the product

Questions you should ask yourself:

- Do you like the product?
- Do you believe in it?
- Do you think it could bring value to customers?

If you’re not pretty sure about it, that’s definitely a red flag. 🚩🚩
2️⃣  Your interest in the product’s environment

Being a developer at a start-up is a challenging role.
In order to succeed, you must be dedicated & passionate about the product & the work.

Therefore, ask yourself: am I truly committed to this field and these stakeholders?
3️⃣  The sustainability of the business model and the robustness of the financing plan

- Did the project already generate profits?
- Do you believe it can do so in the future?
- Is the model scalable?
- What’s the burn rate?
- Has the company raised funds?

➡️ Ask the founders
Want to deep dive into tech career management topics like this: Join the talent club It's free!

trimurl.co/Ye4VCN

You’ll get access to interesting resources (how to become a VP, how to build your career as an IC, etc.) built with top-notch contributors. #Collab
IMO, Here are some, out-of-the-box reasons to join a start-up:

- Chance to be part of something special
- Access to industry leaders and mentors
- Fast-paced and dynamic work environment
- Collaborative culture
- Opportunities to learn and develop new skills
Ok, I'll stop here. If you like this thread:

- Retweet the 1st tweet.
- Join my 2-1-1 career growth newsletter
- Follow @TheAnkurTyagi your mentor

You can ask your questions 1-1 via email & get regular updates on my book and career stories.

Join here: theankurtyagi.substack.com

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Ankur💻🎧💪

Ankur💻🎧💪 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @TheAnkurTyagi

Dec 13
I made $50K+ from blogging in the last 2 years working as a part-time writer.

Here’s everything I learned.

A thread. Image
The only writing (blogging) hack you should know:

- Less tech is more, I work with React 90% of the time.
- If you’re writing for the first time, give yourself more time to figure it out.
- Allow yourself to write poorly.

Stop preparing and start acting.
Ask yourself questions which will help you be focused:

- Who do I need to send a cold DM/Email to?
- What do I do better than other writers in tech?
- What can I do for a long time in blogging?
- Where do I want to take my blogging skills?

Play not to lose; Instead to win.
Read 12 tweets
Oct 4
If you're starting a career in software engineering.

Here are 22 top life lessons for you from my career:

A Thread... Here are 22 Top life lessons for you from my career:
1. No one doesn't really care about you.
2. Nobody is your friend.
3. Find a healthy competitor, not a friend, so that you can grow.
4. Learn to say no, maximum fail here.
5. Build your knowledge, companies will follow you.
6. 80 % just work for promotions.
7. Don't be that person in a team, who is always available.
8. Learn to leave the meeting if you are not contributing.
9. Don't check & reply to emails in the first 1 hour of your day.
10. If it's really urgent, a person will call you.
Read 7 tweets
Jul 23
How to Find a Good JavaScript Developer...

A Thread.
As with any technology, there’s knowing JavaScript and then there’s really knowing JavaScript.

Let me share a couple of proven & effective techniques and questions for finding true masters of the language.

Note:
These sample questions are intended merely as a guide.
🚨 Alert 🚨

Not every candidate worth hiring will be able to properly answer them all, nor does answering them all guarantee a candidate.

At the end of the day, hiring remains as much of an art as it does a science.

JS is in the world of tech today has become fundamental.
Read 12 tweets
May 31
I completed 12 years as a software developer in 2022.

Few honest takeaways about my experience with the job and the software engineering industry.

A Thread...
1. No one can stop you when you master the basics

- You can start with any technology you want.

But if you’re struggling, take a pause & restart your tech journey.

- Remember all new & fancy frameworks are based on the basics.

- Master basics you can code in anything.
2. “What's more important to you: Quantity or Quality?”

- Your answer might be: it depends.

But until you do an experiment in your core areas, how do you actually know about the quality.

Go & take calculative risk & be the change.
Read 13 tweets
Mar 16
Things I Wish I'd Known Before Starting My First Full-Time Job.

A Thread...
Your 20s could be your most defining decade

You’ll have more freedoms & more choices than you’ve ever had in the past or will ever have in the future.

It’s going to be a great adventure.

The “real tech world” that everyone tries to scare you about is actually really awesome.
But you know:

-Don’t be afraid to learn on the job.
-Don’t pretend to know more than you actually do
-You're responsible for your career, not your employer
-Everything is negotiable
-Live to work, but the right Way
-Working late is overrated
-The grass will always be greener
Read 13 tweets
Mar 9
In my 13+ years of software engineering experience, I've reviewed a lot of resumes.

Some of the most common issues I discovered.

A Thread... Image
1- Don’t make your resume too long.

- Interviewers are busy with their daily coding issues while they need to take the interview as well & review dozens of resumes at any given time.

- They don’t have the time to read all lengthy resumes.

- Two-page resume is fine
2- Stay consistent in formatting/font.

- Try to pick one font and make sure you use it throughout the entire document.

- Use bullet points, but only use one type.

- Make sure your text spacing is consistent.

- Commit to a consistent comma strategy.
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(