Avoid using an ORM so you can display your master of SQL.
I’d probably still ORM, but with targeted performance optimization queries does in raw SQL so you show not only you can handle both, but also understand the limitations of ORMs.
I’d also maybe throw in some explicit error handling to show if you lose connection things don’t just spin forever, crash, or just show “Error, something went wrong”. I see lots of fairly nice UIs until something goes wrong, the server times out or whatever and the app completely shits itself.
Generally, show understanding of the topics not just how to use them. I’ve seen so many promising developers get completely stuck once the real world hits and it’s not exactly how they’ve been taught.
I’d probably still ORM, but with targeted performance optimization queries does in raw SQL so you show not only you can handle both, but also understand the limitations of ORMs.
I’d also maybe throw in some explicit error handling to show if you lose connection things don’t just spin forever, crash, or just show “Error, something went wrong”. I see lots of fairly nice UIs until something goes wrong, the server times out or whatever and the app completely shits itself.
Generally, show understanding of the topics not just how to use them. I’ve seen so many promising developers get completely stuck once the real world hits and it’s not exactly how they’ve been taught.