# System for Job Posting... Please help!

**URL:** <https://forum.kirupa.com/t/system-for-job-posting-please-help/260013>\
**Category:** programming\
**Created:** [May 11, 2008, 5:26pm UTC](https://forum.kirupa.com/t/system-for-job-posting-please-help/260013 "2008-05-11T17:26:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dave321](https://avatars.discourse-cdn.com/v4/letter/d/e56c9b/32.png) [@Dave321](https://forum.kirupa.com/u/Dave321)\
**Post date:** [May 11, 2008, 5:26pm UTC](https://forum.kirupa.com/t/system-for-job-posting-please-help/260013/1 "2008-05-11T17:26:41Z")

</div>

I’m trying to determine what would be the easiest/best way to have a site where users can post jobs. Basically, they would have to fill out a form with the basic information, and the info would be posted on the site’s list and given its own page.

Is there any code aviable that I could use as a skeleton? Or should i hire some sort of coder for this? Thanks

Mike

---

<div class="post-metadata">

**Author:** ![simplistik](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/simplistik/32/7747_2.png) [@simplistik](https://forum.kirupa.com/u/simplistik)\
**Post date:** [May 11, 2008, 9:09pm UTC](https://forum.kirupa.com/t/system-for-job-posting-please-help/260013/2 "2008-05-11T21:09:24Z")

</div>

Would be super simple. Your fields would be something like:  
Company  
Location  
Company Website  
Job Title  
Job Description  
Application URL or Download

then just make a call to the database, easy cheesy

---

<div class="post-metadata">

**Author:** ![bear](https://avatars.discourse-cdn.com/v4/letter/b/ac8455/32.png) [@bear](https://forum.kirupa.com/u/bear)\
**Post date:** [May 12, 2008, 3:38pm UTC](https://forum.kirupa.com/t/system-for-job-posting-please-help/260013/3 "2008-05-12T15:38:23Z")

</div>

^ better to make all those different tables with references.

i.e.

Jobs\_content  
Jobs\_ref(references job content)

Also, I would include skills a needed or qualifications table for referencing and possibly, to help with similar job listings links.

---

<div class="post-metadata">

**Author:** ![simplistik](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/simplistik/32/7747_2.png) [@simplistik](https://forum.kirupa.com/u/simplistik)\
**Post date:** [May 12, 2008, 4:17pm UTC](https://forum.kirupa.com/t/system-for-job-posting-please-help/260013/4 "2008-05-12T16:17:24Z")

</div>

[QUOTE=bear;2325087]^ better to make all those different tables with references.

i.e.

Jobs\_content  
Jobs\_ref(references job content)

Also, I would include skills a needed or qualifications table for referencing and possibly, to help with similar job listings links.[/QUOTE]You would only need 1 table, anymore than that makes no sense at all and is overkill IMO. There’s nothing that really needs to be relational unless you’re allowing creation of user accounts.

```auto

CREATE TABLE `t_jobs` (
  `job_id` int(11) unsigned NOT NULL auto_increment,
  `post_date` varchar(11) default NULL,
  `name` varchar(255) default NULL,
  `location` varchar(255) default NULL,
  `website` varchar(255) default NULL,
  `title` varchar(255) default NULL,
  `description` text,
  `application` varchar(255) default NULL,
  PRIMARY KEY (`job_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

```

things like qualifications and things like that can just be kept as text inside the body/description. no reason to make it more complex than what it needs to be.