Profile picture

Resume Q&A and Videos

About Resume

Data Engineer at Taro Community profile pic
Data Engineer at Taro CommunityPosted March 27, 2024

Career Progression on Resume - How much to embellish?

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!
62 Views
2 Comments
Mid-level Software Engineer at Taro Community profile pic
Mid-level Software Engineer at Taro CommunityPosted April 8, 2025

Move projects above work experience?

Despite having a side project with 4k MAU, I'm not getting any interviews. I am concerned it might be because my current job which is listed first is more QA and not SWE is unimpressive and the recruiters see that and gloss over it. Also in the 2 interviews I got the recruiter/HM tends to overindex on the QA work instead of my project and other more impressive SWE experience My work experiences #2 and #3 are also way more impressive than my current job (which is why I worked on side projects) But I am worried that because my projects are listed all the way at the bottom the recruiter doesnt even see it and I get passed over. But also i'm worried putting the project over experience makes it look weird Questions: Can I put my current work experience all the way at the bottom and my work experience #2 and #3 above? (I know typically people say to sort it form most recent, but in my case my current job is working against me). Is 4k MAU (measured by number of unique visitors) impressive enough? or do I need more in this economy? I've maxed out my organic methods and the only bottleneck is more inorganic advertising via social media and praying to SEO gods Is there maybe a way I can list the project under work experience but kind of say that its not a paid gig? I dont want to get in trouble at work or elsewhere by making it seem like its a paid thing or I am working 2 jobs or something. This is just a solo completely free side project but i put in 800+ commits It would look something like this

Work Experience
Website Name Date
Software Engineer
Built and scaled as a solo free side project: 4k+ MAU, 25k total visits, .....
55 Views
8 Comments