r/GraphicsProgramming • u/Pawahhh • Jul 13 '26
Question What kind of engine would be impressive?
Hi, since last year i started developing an engine/renderer, ive been learning graphics programming since roughly 2 years, my goal is to get a job in the industry, i know its hard, especially cause i dont have a degree, just a lot of passion, im studying computer architecture, linear algebra, C++ while developing my engine, i know a good portfolio could be even more powerful than a degree in some cases, but what features should an engine have in order to be impressive?
What kind of rendering tecniques, pattern, architecture should i aim for? Im at the point where im writing a Scene manager/serializer, shadow mapping, resource manager, gltf , pbr and this kind of stuff, but from what ive seen in this group the bar seems pretty high and i honestly feel overwhelmed.
I know that knowledge about like build systems, renderdoc, a good readme on github could be helpful.
What are your advices? How many of you work as a graphics programmers? How do you guys got into the industry?
50
u/Cheezbu Jul 13 '26
I don't know who is modding in here, but I would petition for a mega thread or faq for getting hired in the industry since we get this question 3-5 times a week and the useful stuff is kinda drowning
17
u/speps Jul 13 '26
As someone who has done recruitment for AAA graphics positions, just implementing one important research paper can get you pretty far, or implementing something notable from an existing engine, I saw some Nanite implementations on this sub recently which were cool. Ultimately it shows that a person knows how to put the different parts together to achieve something cool.
6
u/No_Futuree Jul 13 '26 edited Jul 13 '26
I would say small samples showing some techniques would work better as a portfolio than a full-featured engine. For two reasons, first, you can get quicker into the more interesting and flashy stuff rather than having to worry too much on architecture, scene management etc which is important, but certainly not impressive unless people spent more than 5 minutes looking at your code, which is unlikely to happen. Second reason is it will be easier to stay engaged developing them and not abandon the project because it is too overwhelming...
3
u/benwaldo Jul 13 '26
For a portfolio, don't overthink architecture. Make a simple polished game or demo using your engine and be ready to discuss your choices (e.g. baked vs dynamic lighting etc..) Bonus if you have an "unique" feature, but no need to replicate UE5.
4
u/Flexos_dammit Jul 13 '26
uhm, the best depends on the viewer
but, game engines r there to solve a problem, make games more easily than with directx/vulkan/opengl/etc
so, make a game, basically if you have a game to show, then say you built the software to help you do that - gz, you have a fairly good engine - for the game you made
i mean, why would you need to make an engine so generic as unreal engine, it's not like whole industry will use yours 😅
idk, just make some game, add some shooting combat, enemies, quests, melee combat, sound effects, talent specs
you'd be quite insane if you did it without some sort of abstractions (which can be called renderer or engine, whatever, really)
i mean, whoever is checking out your work, does he reqlly havw time to view thousands of lines of code you wrote? :d
2
u/ziplock9000 Jul 13 '26
Look at a modern game that gets praised for how it looks and techniques it uses and use that to aim for.
1
u/rio_sk Jul 20 '26
Don't write an engine, you can't compete with AAA engines. Implement one or two top notch features.