do i even have a chance

[long wedge]

I will say that game dev/embedded is completely out of my depth and I won't be able to give you specific feedback there for content lol. What I can say is that you could be more specific in your experiences, particularly about what you worked on and the relevance it has for a business.

The biggest thing that stands out to me is your founder/lead dev title with all the conflicting dates. I'm at a loss really for what you should do here. Can you explain your founder role and your other game studio role? Do you have a team? If you're solo, I would not have "Lead" in there

Projects
Content-wise, your projects are good overall - but your flight simulator sounds like you had a company? I also feel like the second bullet of the flight sim adds nothing much. I think your flight simulator should be first in your projects bc of the sheer impact there

Role 1
You can improve the first bullet to describe what game you launched rather than saying you had a "scalable framework to..". Bullet 2 and 4 feel trivial to me (too implementation detail heavy) and idk what you mean by "modular scripting system". Could be that I'm just not familiar with the field. If you have any metrics for other things (# players, how many cheaters were deterred by the anti-cheat system) that would be good

Role 2
I have no idea what impact you had on the business with the first bullet. Your second bullet reads like it needs to be rewritten for clarity (and cut the bs like "improved test framework robustness"). Test coverage is also typically described as an absolute value - saying you increased it 200% is a no-no (you can say you increased test coverage from xx% to xx%). Last bullet is unneeded

Role 3
I don't immediately see how weekly updates increase player engagement - this sounds like an uncorrelated impact. What I would go for is something closer to "Delivered weekly feature updates for xxxxx, impacting 2M+ DAU and [...probably something about player retention]". 2nd bullet is not specific enough. 4th bullet also isn't specific enough for me to derive anything from it there

[gilded gyro]

Brother have you applied to roblox

:[ same sorry to hear

Perhaps riot

Theres a bunch of game companies anyway

That would love ur resume

Lmaoo thats fair

Just saying tho at a first glance this is fr a game dev top candidate resume

[long wedge]

Honestly, I'm a bit on the fence. Doing simply "common" projects (like 99% of students out there) isn't going to cut it. What does stand out about your stuff is your massive business impact with your game work.

If you want to push for general SWE I would prob go a different direction wrt listing tech - specifically, I would highlight traditional tech skills used more e.g., Lua (not Luau), Python, C++, and not list tech besides your role (which is fine for your game dev since you're so Roblox-heavy you can afford to abstract)

Tbh in your case, even a summary would work out for you since your experience is so specific

I would call yourself just a normal software developer instead of a lead given such a small team. So "Founder, Software Developer" or "Founding Software Developer" along those lines

The other game studio I would make sure to say it's part-time in your resume - this is to reduce confusion on timelines

Test coverage is an absolute metric. I would not go for a relative increase (says a lot about poor testing practices, first off), and doubling tests does not correspond to a 200% increase in coverage (it's actually a 100% increase in tests). You can try to bullshit this or opt to remove it

I do think your experience seems relatively strong to me, so if you can highlight that somehow and express your clear interest in general swe (whether via highlighting tech or summary), I would consider you for general swe internships 100% based on your unique experience

[long wedge]

Depends on how impressive the numbers are. Acquisition is definitely impressive tho, shows that you built something that another standing firm would pay to have - which is bigger than most of “founder” resumes I see

I would look up software testing and see where your experience fits in there - I do wanna emphasize that I know very little about embedded, so I can’t give you industry-specific advice here. My suggestion would be to talk to other embedded devs.

My point about test coverage applies if you’re going for general SWE, but there are ways around this if you can dig more into the QA aspect among others.

[long wedge]

Like an objective statement of sorts, explaining your background and what you're looking for bc your experience is so specific

Role 1

• Wym by "scalable"? What's the cross-platform framework here?
• Wym by "implemented a modular scripting system for fast iteration"?
• Do you have metrics on the anti-cheat? Why add "to protect client-server communication"? Feels like fluff here

Role 2

• Is your work all just in testing? I would prioritize your biggest highlight in your first bullet
• Making only 24 tests isn't impressive for a lot of people in this industry
• I rarely find "saving hours" a compelling metric - it's better to convert this to more relevant metrics

Role 3

• Weekly feature updates as in?
• I would avoid BS "impact phrases" like "Enhanced team productivity" if you can't back it up with clear metrics
• How did creating player management tools streamline marketing efforts? I'm not understanding this here
• Last bullet has the same issues as bullet 1, I want to know what you're in charge of and what your highlights are

It's also odd to only be full-time employed for a few months to then go into an internship - I would clarify that this is either a part-time or intern role

[boreal cargo]

What games on roblox

[long wedge]

Role 1

• With sociotechnical problems (including code modularity/organization), they can pretty subjective, so you could literally be writing what the industry considers the worst code in the world. Without metrics on how it improved delivery (which you as a team don't have the maturity for), it adds no value here to use "scalable" - and people like me will sniff that out as BS. What DOES add value is talking about the cross-platform specific stuf (PC/mobile/tablets/console).
• "Modular scripting system" afaik doesn't really have a meaning to people in industry
• What did you do to validate requests? I would start there

Role 2

• Since you're going for general SWE, is there a way you can describe your work here that can be better understood by laypeople? This includes things like what the impact of your addition to the test framework was (metrics)
• Quality and difficulty of writing tests are subjective per team (I could literally spin up 500+ test cases in minutes thanks to AI tools) - so I would be leaving out number of tests, and emphasizing more the end-to-end aspect
• If you wrote automated tests to cut the QA cycle, should say that instead -> "Automated bootloader firmware testing". If you can quantify the costs saved from the hours saved (e.g., if the avg eng is paid $50/hr, and you do weekly releases, you would be saving a company $50/hr * 100hrs saved/wk * 50 wks / yr => $250k saved annually. This is how a business (your manager, product owner, etc) would justify your time spent on this work - and this is how you make it relevant to laypeople

[paper pebble]

what’s the font called? it looks rly nice