Reputation: 4 Apprentice
- Active Members
- Active Posts:
- 80 (0.09 per day)
- 09-October 12
- Profile Views:
- Last Active:
- Jun 29 2013 07:25 AM
- OS Preference:
- Favorite Browser:
- Favorite Processor:
- Favorite Gaming Platform:
- Your Car:
- Who Cares
- Dream Kudos:
Posts I've Made
Posted 27 Jun 2013Create a blog, post about code. Live code and breath code. Always code. This will help you get noticed. If your passionate, good things will follow. I work 8 hours a day and come home and code. You gotta love what you do.
Advice for your interview:
Dress nice, suit preferably.
Eye contact is a must.
Be prepared to talk about past projects, what your learned.
Be prepared to talk about your team experience.
Be prepared to discuss oop principles and a few language specifics.
Be prepared to write code, sometimes white board or sometimes they will send you a project.
Share your code related interest and passion.
Have a five year plan.
Ask good questions.
What most are not getting is that this is an entry level position that does not require all these years of dev experience. I will keep this in mind though. Fact of the matter is I have no team coding experience
Posted 27 Jun 2013Whether you get this job or not, here are some things that you (and other potential employees) should think about getting for future interviewing. Many of these cost list to no money either.
1) A blog where you contribute postings regularly, talking about the industry, your work and your thoughts on the field.
2) A portfolio. I have carried a print one around with me, but you should also put everything on a website or computer ready to go.
3) Publications you have contributed to (got an article on stackoverflow or sitepoint.com? Show them!)
4) Start github repositories with some of your work. Easy to find, easy to download, easy for them to run and play with!
5) Knowledge from a few key books you have read. It is always fantastic to be able to bust out a quote from a book you read about a practice you do or believe in.
The idea here is that you want to show them everything you can do, you can show them quickly, you can show them on their own pace, and anything you can do to allow them to get in and play with code you wrote is often good for employers. They want to know they are hiring someone that knows there stuff and can get up to speed quickly.
If you show them all this and they still don't hire you, it is just not the right fit for you. Always improve the sites, demos and blogs you create. />
I have gotten frustrated with Git in the past, mostly when I just heard of it and attempted it (I'm sure this happens to many)..
Posted 27 Jun 2013It sounds a lot like you've never applied for a job before. And you're in college? Wow. Go back to your college and go through the library for books on interview preparation.
Like any job you'll need to fill out an application. That typically involves the last 10 years of employment with dates, addresses, phone numbers, supervisor names.
Generally an application has spaces for personal and professional references. Bring it printed if you like, or on your iPad. Whatever. Just so you have it for the application.
As for 'runnable' - I don't like to assume that my application is going to run on their PC. Or that they would be willing to put an outside application on a company machine. You do more harm than good by bringing a USB stick then have the app fail on their PC. So take your laptop with your portfolio and Visual Studio on it. Queue up your presentation then put it to sleep. That way you can open it up and go in less than a minute.
You can then run the application(s) you want to show, show them your code if you like. Screen shots of things you've worked on but are proprietary so can't bring with Etc. I always bring mine, but have only needed it once. But I think if it the same way I consider guns and condoms: I'd rather have it and not need it, than need it and not have it.
I have applied to many. I have never had the opportunity to hear back from any hiring managers because they all require 10+ years of dev experience. I don't have a laptop.. I've been needing to invest in one though.
Go easy on me man I am anxious, as any interviewee would be.
Posted 27 Jun 2013
Quotegoing above and beyond, bringing my résumé, even a printed copy of a program I have been redoing from a class, and following up with mailing a thank you letter afterward
That's not really 'above and beyond' when looking for work. That's pretty much the norm. Maybe not for McDonalds, but for any position above lot boy or short order cook. Of course you bring your resume, references, job history including dates addresses and phone numbers, your portfolio of work (both runable and reviewable) and send a 'thank you' to the interviewers for the time. That's right up there with bring a pen and pad, wear a shirt and tie.
My recommendation is to not see each interview as a potential job, but as a learning experience at how to interview. You'll go through 20 interviews before getting hired. Learn from each one. When they test you and ask you questions you'll see where you are weak with respect to employer expectations. Keep a pad in your car. As soon as you get out of the interview write down the parts you stumbled over so you can research.
Thanks. With this being my first interview in the field it is easy for me to have high expectations.
When you say to make your code runable and reviewable, do you mean to bring a flash drive with the code on it? And as for references, I can't think of many that are not personal, minus my supervisors at my current job (in retail), where I have worked for almost six years now. I will be sure to highlight that. What format should I bring my reference contact info in?
Posted 16 Jun 2013here my submission
Liking it. Very comprehensive. Creative use of the "wall" of technologies/languages.
- Member Title:
- D.I.C Head
- Age Unknown
- Birthday Unknown
- Programming Languages:
- Java, Visual Basic
- Click here to e-mail me
Zuelajindi hasn't added any friends yet.