#Graduated in 2022, but with significant work experience in early stage startups.

39 messages · Page 1 of 1 (latest)

grizzled swallow
spark rampart
#

Some initial feedback -

  1. please don't bold keywords.
  2. you're listed as founder but at least give a 1-liner what the startup actually is. i'd expect SOME information about funding, business strategy, etc.. otherwise this is just a "project" masquerading as a "startup" which is not a good look.
  3. this is my personal preference but i would separate your skills out just slightly more. also I find it useless to list something like "CLEAN architecture" - also why is that capitalized?
  4. random typographical errors, like the extra space after "Estate", the lack of space between GitHub and Actions, the capitalization of "JS" in Nuxt.js, etc..
  5. you built an app as a solo dev that was later acquired? why is this not listed under experience?

I rarely feel this way but your resume would strongly benefit from a summary at the top. it's clear you have great experience and can hit the ground running.

grizzled swallow
spark rampart
#

Yes. Most resumes I feel like it is a bit much to include one, but you are in a position where you might need to explain your resume a bit more because you have great experience that extends before you graduated.

#

It's a suggestion based on a gut feeling, but I am sure you will get opinions for the opposite.

grizzled swallow
#

I'm also a little confused about where I lie in terms of roles. Since I graduated in 2022, would I still be considered a new grad? or am I junior/mid-level?

spark rampart
#

You are not mid-level. You will be considered new grad/junior still.

grizzled swallow
#

Despite my experience in building distributed systems from scratch and managing a small team of developers?

spark rampart
#

Yes. It's not enough of the right experience.
Unless you built a startup that had legitimate funding with investors, etc.. it's a cool thing to have on your resume but not something that makes you suddenly mid-level. This might give you an edge more at small startups, but I wouldn't expect it to up-level you at a FAANG or even F500 company.

grizzled swallow
#

Oh okay that makes sense.

spark rampart
#

Look at the Dropbox Framework for reference.

grizzled swallow
#

@spark rampart What do you think?

#

I replaced UGC to "video ads" because idk if everyone knows what UGC means.

spark rampart
#

Third bullet point in your first role listed, you still have that extra space btw. Would also be more specific when you say "overhauled architecture" - what exactly did you do to make it more scalable and maintainable?
First bullet point second role listed, you have bold.

grizzled swallow
spark rampart
#

In addition to the above, if it were me, I would sacrifice the class bullet point to separate out your skills into two lines if possible.
Languages:
Technologies: (or something)

#

But that's a personal preference.

#

Speaking as a former hiring manager, ofc.

grizzled swallow
spark rampart
#

Those are some great details. Wrap that up into a succinct one-liner and add it. Don't need to break any NDAs to give an idea of what you did.

#

I would stay away from "overhauled architecture" language.

grizzled swallow
#

Thank you. Btw you're awesome for helping me out.

spark rampart
#

I am just one person with an opinion, so please take what I am saying with a grain of salt, as well.

grizzled swallow
#

Of course! However, I do agree with your feedback

#

I see that you're a senior backend developer; how long have you been working as a swe?

spark rampart
#

11 yoe, staff+ level now but previously a director of eng.

grizzled swallow
#

That's awesome. Are you allowed to share what company you work at now?

spark rampart
#

Allowed, but will not share.

grizzled swallow
#

Ah okay, no worries.

#

"Architected AI chatbot backend to accommodate N third-party integrations for code maintainability."

spark rampart
#

I think that looks fine. If you could spare a second line, then I would add more details related to dependency injection, etc..
In general, the more recent the more details the better. But otherwise I think it's a good resume.

grizzled swallow
#

Would you give me a chance for an interview with this resume?

spark rampart
#

Yes. If it were me, I would do a soft phone screen and focus on the following points:

  1. Your app got acquired, neat. Tell me more.
  2. You founded a startup and work at a startup as well, how do you balance the two roles? At what stage is your startup?
  3. I saw at YC startup you re-architected the backend, tell me more what you did.
  4. You've used both MongoDB at your YC startup, and also Postgres at your current startup. What are some of the tradeoffs when selecting one vs the other?
  5. What made you choose DDD when breaking apart your monolith?

Ofc there are other standard questions as well, but those 5 are where I would start.

#

But I often do not get the liberty of that, so I would prob work those into my actual interview!

grizzled swallow
#

Can I DM you? I want to share a slide deck I made for my engineers for my startup. It was used for onboarding to get them up to speed.

#

I also think that it could help me gain another perspective of insight from someone more experienced.

spark rampart
#

Yes, feel free.

grizzled swallow
#

Awesome!