Taro Logo
Profile picture

Resume Q&A and Videos

About Resume

Not able to get the job opportunities you want? It's extremely likely that your resume is lacking. With this core professional document, you must make a stellar impression within seconds.

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
40 Views
2 Comments

Fear of picking a specialization/niche: Is focusing on front-end okay?

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

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.

Show more
537 Views
5 Comments

How is the market right now for junior engineers?

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

Hey, I just posted a question related to me considering to quit my job here:

TLDR: I am seriously considering quitting my job due to the commute, I live in SF, have 1+ years of experience and am looking to work in the city/remote. I have 6+ months of savings and am a U.S. citizen. Effectively, I'd say there's a 95% chance I'll quit my job in Jan 2024.

Considering this, I'm evaluating the current tech job market.

Generally, my impressions are that while the overall economy is doing quite well, the tech market is in a bit of a lull w/ potential layoffs in 2024-2025. We had the major overhiring of 2021-2022, then the layoffs in early 2023 and now are in a period of stasis relative to the bull market of the past 10 years+. I believe this is also due to the end of zero interest loans making capital expensive. This then leads to profits being more emphasized, then cost-cutting in large corporations (employees being a major cost, so layoffs occuring) and then difficulty for startups to raise money.

Additionally, I recently read The Pragmatic Engineer's take on .

"Unfortunately, I suspect Spotify is early in having a realization which other tech companies will also have, next year. With the zero interest rate period (ZIRP) over, itā€™s expensive to borrow cash. Spotify making a loss meant it was effectively borrowing money in order to operate. Turning a profit is more urgent than when capital was cheap. But how do you turn a profit if you cannot significantly increase revenue? You cut costs, and the biggest costs for most tech companies are employees, sadly.

As a result, Spotify could well become profitable, assuming it generates similar revenue in future. And this is exactly the plan; to keep doing the same as before, but with fewer people.

In this way, Spotifyā€™s cuts make business sense in the context of business growth slowing, persistent loss-making, and a hiring spree in 2021-2022 which didnā€™t boost revenue. These cuts may be surprising for many at Spotify, but probably not for the leadership team. The only question is how many other companies are in the same position as Spotify, but with leaderships yet to draw the same conclusion from the economic conditions.

This is probably a good reminder that the tech jobs market remains volatile. If you have a stable job, it could be a good time to put aside some earnings for a nest egg, stay engaged with your network, and to position yourself to work in areas seen as profit centers, not cost centers."

What are your impressions of the tech market right now?
Any recommendations of how to navigate the market or resources to utilize?
Anything advice years-of-experience specific (Junior engineers vs. senior engineers vs tech leads vs. etc)?

Show more
304 Views
4 Comments

What should I add in my experience section in my resume?

Systems Engineer at Taro Community profile pic
Systems Engineer at Taro Community

I have been part of an MNC for last three years. During this time I have been part of four different projects. I have added following points in my resume for those three projects.

Data Scientist (Apr 2022 - Mar 2023)

  • Analyzed data from various sources to identify issues impacting growth and profitability across product and service offerings.
  • Utilized a variety of tools and technologies to conduct data analysis and visualization.
  • Recommended solutions to address complex business problems based on findings from data analysis.
  • Tech Stack: Python, Pandas, PySpark, Databricks, NumPy, SQL, Excel

SAP BW Analyst (July 2021 - Apr 2022)

  • Created custom reports and flowcharts to present the raw data to clients in an easily digestible format.
  • Utilized innovative methods to increase efficiency and decrease run times for all reports by over 15%.

Network Associate (Nov 2020 - June 2021)

  • Monitored network capacity and performance to diagnose and resolve complex network problems.
  • Successfully resolved over 500 complex network issues, resulting in a 95% customer satisfaction rating.

For the last six months, I have been part of a Django development project as a backend developer, in which I could not get any work because the use case we are supposed to work on has not been finalized yet. I am actively looking for a job switch, looking for an entry level SWE or Data role and could not think about what should I write in the experience for the last 6 months.

Show more
123 Views
2 Comments