Sketch an ER diagram to represent the aspects of a job$-$hunting website

described below. Note that your diagram should not be an Extended ER $($EER$)$

diagram, so there should be no inheritance, aggregation, or weak entities.

$1.$ Users have unique usernames, and we also store their password hash,

name, date of birth, email, phone number, and permanent address.

$2.$ Documents are identified by a unique document ID$,$ and we also store a

title, document type $($e$.$g$.,$ resume, letter of recommendation, etc.$),$ owner

$($required$,$ one of our users$),$ last update time, and file name.

$3.$ Employers are identified by a unique company ID$,$ and we also store an

name, industry, address, and company description.

$4.$ Positions are identified by a unique position ID$,$ and we also store a title,

description, and application deadline.

$5.$ Every position will be posted by an employer, and we keep track of when

each position is posted. The same employer may post multiple positions.

$6.$ Users may apply to positions. Users may apply to more than one position,

and multiple users may apply to the same position.

$7.$ Users$$ documents may be submitted for positions. The same document

could be submitted to multiple positions, and a user could submit multiple

documents for the same position