Interviewing Q&A and Videos

Hello Taro Community

I want to pick a specialization now due to the market and the lessons I’ve learnt being in the group.

A little context on the issue:

I had a mindset that more technologies I know the more options I’ll have and also working as a full stack dev in my last position I got a lot of hands on experience on different stacks. More like breadth of knowledge but not depth.

I was applying to jobs like Database, UI/UX, Front End, Back End, Software and DevOps couldn’t land any interview in the last job hunt.

Last month I let everything go and I told myself I’ll specialize in “Full Stack”. I have been also working on side projects for my portfolio.

However, a lot of senior devs told me Full stack is too broad and 2 and 1/2 years of experience that won’t cut it.

I want to specialize in Front End with React and go very deep in that. Build projects pertaining to React Front End for my portfolio.

My fears:

• I’m closing down my options, and limiting myself to Front End
• Also being a foreign student where you kinda have to “work in tech” since that’s my major a lot of fear is coming up. In case the time I go back in the industry there is lack of front end openings
• A lot of family friends in the industry telling me that Front-End specialization will be a waste of time since the industry is very saturated with it

Deep down I have realized specializing will really make my portfolio, knowledge and resume stronger. Plus Front-End is something I genuinely am drawn to and enjoy doing.

Would love to know your input on this.

Hello everyone hope you are all doing well.

I got laid off from my Full Stack Developer position mid Sept. It’s Dec, and I’m at 1700 applications. I only got 1 interview early Oct, nothing after. I couldn’t get a call back from a few companies paying 15/hr.

Positions I’m applying to: Web Developer, Full stack developer, Front End Developer, UI/UX designer (occasionally), Software engineer.

What I have been doing this time

1. Setting a day every Thursday of the week to improve something in my resume
2. I’m a foreign student so I don’t have the luxury to wait out, or work any other job than tech so I’ve been working on a project alongside applications.
3. Finishing Meta’s full stack certificate on coursera so I can be prepped up with the basics
4. Collaboration posts contributions on LinkedIn
5. Walkins at recruiter agencies
6. Using referrals still no luck
7. Messaging hiring managers and recruiters - no luck or response on that end to
8. Going an extra mile with cover letters
9. Redid my LinkedIn

I’d be curious to hear your opinions on how I can break out of that cycle.

I’ll attach my resume below for your reference and feel free to point out everything that I can change.

Link to my resume:

Can you please share strategies in place for career growth ( L5 -> L6)

along side interview prep ( L5 / L6 ) for a FAANG+.

Goal: L6 at FAANG+, either direct or L5 -> L6.

Reason: More TC

Timeline: Not urgent, just waiting for the right opportunity.

My was “When given a take-home assignment, what is a reasonable turnaround time to get it back to them?” I now know it’s within a week.

I was given the assignment to create a basic Django app and was told to spend no more than 3 hours on it. Here’s the short text of the assignment description:

Table Metadata Extractor (Python)

Please provide a Python Django application that has one API endpoint which accepts a database connection string from your DB of choice (Redshift, BigQuery, Snowflake, MySQL, Postgres), connects to the database using and returns a list of the TableMetadata data objects (see below) for all tables in the database.

TableMetadata = {

columns: List[ColumnMetadata]

num_rows: int

schema: str

database: str

}

ColumnMetadata = {

col_name: str

col_type: str

}

Bonus points for:

·         Instructive error messages for improper connection strings or other invalid input

·         A solution that is efficient

As a Data Engineer/Analyst, I haven’t done web-dev stuff in years and have never used Django. My immediate instinct upon reading this project description was to find a resource to learn Django online. I’m not sure this is the right instinct, because software is about doing more than learning as Alex has mentioned so many times.

The way I see it, I have 3 ways to approach this assignment:

1. The way I just mentioned. Go down a learning path (hopefully not a rabbit hole), learn about Django and try completing the assignment.
2. Dive right in, try building the solution from scratch, Googling and ChatGPTing liberally.
3. Don’t do the assignment, spare myself the time and headache, and beef up my Python web-dev skills for the future.

The first approach requires the most upfront time. The second might be longer or shorter than the first. And the third doesn’t require any upfront time but requires a commitment to being in a much better position to do the assignment in future.

This is the second time in a couple of months I’ve been in this position since I was given an assignment for a different company to build a Flask app and did a shoddy job with it.

My first question is, which of the 3 options should I do to address this time-sensitive situation?

My second is, how should I address this situation long-term? Building some web-dev projects in Python with Flask/Django/FastAPI seems pretty logical. I don’t get to work with them at work, but I could spend a few weeks building stuff with them. I guess that’s the answer, the key is to avoid tutorial hell.

My third is, how should I think about take-home assignments in general? Should they stretch me a lot in terms of learning new things or conversely, should I be, say, 80% comfortable with what I need to do, just stretching a bit here and there to do stuff?

Thanks!

I have a follow-up coding interview with Meta after the Onsite rounds. Under what circumstances is a follow-up round requested? Is it because there were some strong hire rounds and some weak hire rounds? I am looking to gather inputs/tips on how I should be preparing for this interview. Would this interview be different from the other coding interviews that have already been completed?

I'm a Data Engineer looking to break into FAANG. As such, my time outside of work right now is spent applying to jobs, asking people for referrals, and networking. When I have interviews, my focus shifts to Leetcode.

I really want to build a side-project though both because it's fun and because it will help me perform better at future jobs.

My (common) issue is this: where do I start? Not in terms of the problem I am solving. I have a super-smart friend who's a lawyer and an MBA who's into fantasy sports and he has neither the time nor the ability to create an app. I feel like I could just generate a bunch of different ideas with him and pick the one most interesting to me.

I mean in terms of tech area. Alex and Rahul are both mobile developers and that naturally lends itself to great apps. I know Alex has mentioned that in a vacuum, it's better to focus on front-end for side-projects. I have no experience with front-end or mobile, some back-end dev experience and a fair bit of data.

I could build a data eng project. Start Data Engineering has some great projects on his blog () and there's definitely plenty of examples online (e.g. ).

My question is whether I should build a DE project. I'm not particularly wedded to DE because I feel like I want to do more SWE work and less business analyst work. Above all, I want to get into FAANG for the boost to my learning, career, and comp. DE is prob the easiest way of getting there but again, not wedded to it.

So I see my options as a) doing a DE project (maybe using the projects above to get my feet wet); b) doing a full-stack project (hard to do a back-end only project I think); c) mobile? (Alex and Rahul are tempting me).

Is there any advantage to mobile over a web-dev project?

If I do b or c, I'm concerned about falling into tutorial-hell or at least taking too long to learn before building. I'm tempted by a full-stack course like Zero To Mastery's full stack course, but it's 40 hrs, and I know it's prob not necessary.

Just want to add that I'm a newb for side-projects and I'm aware that I can and will experiment with multiple project types once I get started.

Sorry for the unstructured thoughts here. My brain works on NoSQL, not SQL ;)

I've just accepted an offer from a crypto startup, before my Meta interview loop is completed. Even if I got an offer from Meta, I would choose the crypto startup over Meta, so I'm debating whether or not to terminate the loop. If I continue the loop there are of course two potential scenarios:

1. If I pass the loop and get an offer and decline, I have read that if I apply again within a year the process would be easier to get through -- maybe I could go directly to hiring committee/team matching? Is that true?
2. If I fail the loop, then I would not be able to interview again for 6-12 months?

I feel like scenario 2 isn't such a big risk, while there are significant benefits in case scenario 1 happens to offset the risk of 2. I'm not sure though about how true the assumptions above are.

Any thoughts? Thanks!