Show your Backend Engineering Skills To Recruiters - Building a Full Backend Portfolio

Inspired by your video I have created my first c4model of a project. I wish you could take a look at this! If you have some time from your precious time to check this then I will be very grateful.
Could you please let me know how can I send it to you?
Thank you!

Love it.

this is way too overkill, maybe this could be a good portfolio if you need to be hired as some sort of researcher but in 90% of cases recruiters just look for someone who can do the job, they wont care about how many papers or documents you write.

solid list thank you

.

But what If you have worked with SaaS projects that are not really in favor of you share your work to others to showcase?

Thank you for the effort you have put into this video.

Musashi!!

I made backend portfolio projects to display my skills how do you deal with the database?
With a local database the other person won't have that.

Can I just put it in a XML file so the database is inside the application in a text file to solve that
or make it run in a docker container?
Can I expect every employer to be able to download Docker Desktop and get it running?

Is there some general used way to deal with it?

thanks for this! i am also working on the gis, webgis field :) , trying to incorporate web maps to the portfolio

Can u give me example about technical decision that i have to add to documents because and didn't understand very well? and Thank You :)

Portfolio is not diploma. Diagrams are not required. 90% of reviers couldn't read UML at all.

really nice work I like how much effort you put in this <3

That 70's show!!

Wow this actually motivated me to start a blog!

I am curious about where are you from??

Excellent, as usual. Thanks!

You made me smile at some point. It is, sometimes, hard to prove that you did "all that work" 😆 - depends how deep of a proof they want, and how good your memory is when it comes to odd details. I'll never count out plain weirdness.

Hope no one will be so curious, even with all those nice comments I liked to plaster everywhere in my code, about the intricacies of notarizing something on macOS when I was doing it forced to disregard Apple's "way to do it"(TM) in an app that was using a custom runtime. It was like: "you're on your own, buster; here's some half-baked docs for your kind. Also, speaking of notarizing your weird JRE implementation-based app, here's access to an unoffficial support thread. Oh yeah, with some of our own engineers that are well-meaning but sometimes dumbfounded themselves...because you are a beta tester for a service we enforce. That, btw, goes down randomly and this will block your releases for days."

We were integrating some 3rd party web rendering component in the application and rarely have I felt as proud as when one of their guys asked me: "Can I publish on our internal Wiki what you sent me? We've had three engineers toiling at this for two weeks and they still haven't cracked it."

But the whole ecosystem in there? Long lost somewhere in the desert part of my mind.

When I left the company, I wrote "a book" on the subject, indeed, and had quite a few recorded seminars on the whole release topic.

I remember I worked for an IT company n I hadn’t seen evening for like 1 year because my office timing didn’t allow me to see it… but now I realise all this IT is shit … be a entrepreneur

If I specialize in backend, do I need to build a frontend for my projects in order to show them off in a portfolio?

This shows the GOD level requirements of employers. First you same we don't have time to look in a one page resume line by line and other time you say I dont have issues reading 5 page documents. Hiringh managers are very confused with whatever they do.

My portfolio is jobackdev (please add the dot and the normal extension). What do you think about it?

sorry to say but if these are the things you look in a candidate then why don't you say "we don't see ppl that can get the work done and can be innovative in their solutions but we see pple that focus on things that can be useless in industry but are appealing to our mind and eyes".
haven't expected this coming from you

Hi @hussein nasser, can we add the information about the projects which we did with companies during the job? I mean, just abstract level diagrams.

How to make design document?
Can h please make a video on that..

Great advice Hussein :) thank you

Such a great video. Gave me great ideas for my next job application

Corporate rats... all this bs documents before you even start writing single line.

Great

Write a very simple “Situation -> Complication -> Solution” memo on a integration / scaling / your problem space of interest - challenge. That tells me already a lot as a CTO. Cherry on top if you have it on github with proof of concept runnable as dev container / Docker Compose / Kubernetes set-up. Don’t forget that what backend guys experience as “skill signaling issue” is 1:1 the same for the rest of the world. A business or strategy consultant can also not build an example business and point people to a website. Use these techniques as well and don’t get sucked into the flawed “push vecel” done trap. I want to see problem solving skills… not how to avoid them (99% of businesses are by definition brown field projects). My 2ct.

I feel like the simplest way is to build very small projects and put them in a github repo. I'm talking small things that solve a specific problem just to show your skills on how you implement for example authentication or whatever you are really good at.

that 70s show 👍

One of the few guys who deserves my like and comment, Hussein Nasser. Thank you bro!

Pure talent. Thank you for such insights. I am going to start writing articles now.

Thanks @'Hussein for such awesome content, i could watch it for hours.

Always something new to learn ❤️

Yeap. Disclosure is my problem to prove my portfolio. Backend isn't a visual product too. Reference from people we have a work together is another way.

Through contributing in the Open Source

is it indeed learning pen testing as a backend engineer? Will this add up any value to the resume?

Thanks for this valuable video, it brings a lot of content and concrete information. It's very helpful for beginner backend developers or developers 'to be' :)

Thanks for ur information but still I have confusion about live project. If we build any project in backend technology like java then how client can understand as this project is not containing any UI

this video is fucking amazing. super underrated. i haven’t found this insightful information anywhere else. thank you.

Good examples of documents are srs (system requirenments specification) and sds (system design specification)

Solid advise

I'm not a native English speaker...
what does it mean by 'papers'?

I`m realy proud that you are an arabian, so thank u that u give us a great rodmap

thanks man you really helped me !!

Just starting to learn the back-end side so not too knowledgeable, but just curious:
He said maybe only 2-3 of these projects, how do you experienced back-end devs think an employer would react to you having all of them 🤣

Musashi book on the shelf 👍