Taro Logo
Profile picture

Interviewing Q&A and Videos

About Interviewing

Tech has one of the highest rates of job switching, making this skill incredibly high-leverage and vital to master. Understand what it takes to convince companies you are strongly competent.

Career Progression on Resume - How much to embellish?

Data Engineer at Taro Community profile pic
Data Engineer at Taro Community

I'm an engineer with about 4.5 years of experience. I've had 2 jobs since graduating university. The first was a small startup (<10 people) where I did backend engineering and worked like a dog. The second (and current) is a large (~1500 people) company that's far more chill.

I've heard, read, and generally understand that recruiters (and probably hiring managers as well) like to see career progression when reviewing resumes. Makes sense.

My questions are:

  1. rather than calling myself "Backend Engineer" for my first job on my resume, should I say I was a "Junior Backend Engineer"?

  2. for my current job, rather than calling myself a "Data Engineer", can I call myself "Senior Data Engineer"? My company isn't technically advanced to the point where they formally use the title "Senior" engineer for anyone (although engineers definitely are paid differently based on tenure, impact, negotiation skills). Hence I feel like I have that lee-way. Heck, it might even be better to arbitrarily take the 3 year block at the company and pick a point around the 2-year mark where I say I became "Senior", so I can have Junior -> Intermediate -> Senior on my resume.

There's irony in down-leveling myself for my first job, although I really was junior and titles are fungible. As for up-levelling myself in my current role, isn't the point of a resume just to get an interview? And are people really going to check with my employer and say "aha, caught you! you said you were a Senior Engineer, but really you were an Engineer!" and even if people do, I would imagine it's a small number, that's offset by the upside of demonstrating that progression, even if it is a little messaged'

Finally, to address a question that will probably be asked, I definitely feel like I have learned a good deal since I started 4.5 years ago, technically, but more importantly knowing what to work on. Prioritization, time management, etc.

Thanks!

Show more
44 Views
2 Comments

What to do when hired as a SWE2 with 15 years of experience?

Senior Software Engineer at Taro Community profile pic
Senior Software Engineer at Taro Community

I am a 15 year experienced software professional holding H1B. In my last 3 companies, I was a Senior Software Engineer. In my penultimate company, I was due for Staff promotion. Fast Forwarding, I was impacted by layoffs in Jan this year. I had 3 months to find a job in this market. I was applying and passing on my resume through all my network. Most of my applications got rejected quoting they picked another candidate. Some of my applications materialized into interviews , but I ended up not clearing (was in bad form and stress and also didn't get ample time to prepare thoroughly).

Finally, I got my application picked at a company through a referral, but they only considered me for SWE2. I explained them my experience and requested to consider me for SSE level, they said the panel will be open to it. But in the end, they ended up offering me SWE2. I took the offer as I had no choice. I was running out of time and did'nt want to risk rejecting this offer and waiting for a better offer. I took up the offer and joined, but I don't feel happy. I wish I had more time to really choose what I wanted.

I would like your thoughts on how "wise" is it to be SWE2 with 15 years experience. Would my age become a factor for further career progressions as they would prefer younger people? I am confused if I should stick to this, be patient, work smart and work my way up inside, or would it make more sense to keep interviewing and find something that I feel happy about. Look forward to helpful replies or referrals for SSE :)

Show more
175 Views
2 Comments

How to navigate career after layoffs

Mid-Level Software Engineer at Taro Community profile pic
Mid-Level Software Engineer at Taro Community

I recently got laid off working as a developer working within an agency. I currently have around 5 years of experience working in the agency setting utilizing React, Next js, Vue, Liquid, and the Shopify API to create custom eCommerce sites. During my time at these agencies, I also had the opportunity to act as a lead, interact with clients, set timelines, and cross collaborate with designers/projects managers to meet deadlines.

I have been looking for new opportunities since January and I've been able to secure a couple of interviews, technical challenges, and one onsite. Most of my interviews have been coming from agencies, but my preference is to join a tech startup or maybe more on the brand side of things within the Shopify niche. Below are a couple of questions:

  1. Will working at another agency hurt my career in the long run? My ultimate end goal is to work for a bigger tech company if possible.
  2. If an agency does want to hire me right now, should I take the job for now or just wait for one of my preferences?
  3. I notice a lot of developers within the agency space freelance after their 9-5. Does studying for interviews or future jobs provide a higher ROI instead of freelancing?
  4. Lastly, I just finished (super helpful!). It seems like the best course of action for me is to apply a lot, work on side projects instead of grinding leetcode, and study system design. Does this seem correct?

Thanks in advance!

Show more
299 Views
3 Comments

Learn About Interviewing

Interviewing is an essential skill for every software engineer. The tech industry has one of the highest rates of job switching, so learning how to get good at interviewing can elevate your career. Your ability to transition between roles and companies depends on how well you perform during the interview. Taro offers resources for helping you to excel in software engineering interviews. We provide insights on effective preparation strategies and guide you on how to master the interview.
Interviews are a test for you to demonstrate your problem solving and technical skills. The ability to navigate complex challenges during an interview shows how prepared you are to take on the demands of being a software engineer.
Interviews also assess cultural fit and communication skills. This is important because you’ll be working in collaborative work environments where you need to talk to your team and other teams to execute well on your projects. Having great communication skills means you are able to effectively outline a broader vision of your project, dig into the technical details of your project, and communicate any potential issues to your stakeholders.
It’s crucial to thoroughly research the company to get valuable insights and make a good first impression. You can filter our Q&A by company to see whether there are any relevant conversations about the company to help with your interview. You can also check Blind and Reddit to understand what people are saying about the company. Use our Taro Networking feature to reach out to people in a company to get an insider perspective of the company. The company page should include information about their values and culture. Make sure that you align with these values. You should get a sense of the company’s financial reports to understand their products from a revenue point of view.
You should have a solid foundation in data structures and algorithms to show your experience and problem solving capabilities. Pick a programming language that you are proficient in, and use it for the technical portion of the interview. Leetcode is recommended as the best tool to practice for data structures and algorithms type of interviews. The provide a large set of problems with a code editor for you to solve the problems, and they have test cases and performance profiles so you can evaluate your solution. it’s also recommended to prepare through mock interviews.
The above strategies, along with diving more into Taro interviewing resources, can help you effectively prepare for an interview at a tech company.
Show more