The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
Thanks.
Details of Position
--------------------
Job description
As a Trainee Web Developer you will be developing E-Solutions, as part of a team, to meet our clients' requirements in whatever technology platform is required. Working under the mentorage of a Senior Web Developer alongside other Web Developers, Designers and client facing staff. Developing expertise in and keeping up to date on salient Internet technologies.
All staff are expected to understand and abide by our QA standards and procedures as well as ensuring that colleagues do through the peer review process.
Responsibilities
* Develop e-solutions using appropriate languages and technologies
* Assist in the specification and scoping of projects
* Provide specialist technology expertise to other developers, designers and commercial staff
* Peer review code for colleagues
* Abide by the companys QA procedures and standards
Candidate
* Have knowledge and experience of more than one different web development language
* Probably hold a good degree in a computing, science or engineering
* Be keen to use various operating systems such as Windows, Unix and Linux
* Be able to communicate effectively with technical and non-technical staff alike
* Be ambitious and keen to take responsibility for their own work
* Have an over-riding desire to learn
* Have a passion for providing web based solutions that actually work
> ok guys need some help with flash, quick tutorials or something along
> that lines -- nothing special just so I know how to go about doing
> it.
>
> Thanks
Help > Lessons
Help > Tutorials
Thanks
Don't try and blag them by pretending you know stuff that you don't, they *will* see through that and will dismiss your application.
Do take examples of work you have done, just print outs of web pages will do, explain how you put the pages together, what tools you used, what problems you had and how you overcame them - take example HTML code if you must, but a javascript / ASP / CGI example might be more impressive.
By QA I'm assuming they mean coding conventions, like naming variables properly, take a look at coding conventions and try and drop in something about it in the interview. Most companies use MS Visual Source Safe for source code control, you might like to take a look at it.
Be confident, if they ask you a question you can't answer, tell them the truth that you can't answer, this is important, when you are coding and you are stuck, you need to ask for help rather than suffer in silence all day with a problem. It's just as important, if not the most important thing, that these people like you as a person, not just a coding expert.
Good luck, and let us know how you get on :)