Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

blasto333

macrumors regular
Original poster
Jan 3, 2004
247
2
In December of this year I will graduate with a degree in Information technology.

I have a lot of experience in programming and web development, but have decided that a career doing programming is really not for me. I am actually fairly good at it, but I have begun to hate it as a job every day.

I have learned this though my past internships (and current one). I have learned it is important to me to HELP people during my job and establish a routine.

I have skills in:
* Java, php, mysql, xhtml, css, perl...but I want to work at Apple as an internal help desk person or an apple care rep. I know a ton about the mac os and windows helping people figure out common problems. (I have done this for all my friends and their friends). I would find a job like this much more enjoyable and fulfilling.

I know it won't pay as well as a programming job, but I was wondering what is the best way to get a job at Apple? (I have applied online, but have not had any luck)
 

saminsocks

macrumors regular
May 12, 2008
130
0
I'm in a similar boat. I hear personal contact usually works the best. I'm assuming you want to work as an Apple Pro and not in store as a genius or specialist? If you're not close to a location try calling and talking to someone, just to let them know who you are. Good luck!
 

blasto333

macrumors regular
Original poster
Jan 3, 2004
247
2
Should I just call Applecare and be like, can I talk to your supervisor? (lol)

I'm in a similar boat. I hear personal contact usually works the best. I'm assuming you want to work as an Apple Pro and not in store as a genius or specialist? If you're not close to a location try calling and talking to someone, just to let them know who you are. Good luck!
 

superman193

macrumors regular
Apr 15, 2008
131
0
I would say to call Apple HQ (not apple care) and ask about employment or to talk to a superior.
 

GeekyTiki

macrumors newbie
Jun 21, 2008
12
0
I graduated with a degree in Computer Engineering December 2006. As I neared graduation I started looking at job listings on Apple.com. In September 2006 my senior project was related to one of the jobs posted online so I sent my resume along with filling out the online form. I believe I explained my experience a little bit and how it applied to the job posting. It was for a position having to do with audio codecs, wifi, and compression. I did not hear anything for several weeks. I figured they were not interested. In October I was contacted by a human resources person to arrange a phone interview with iPod engineering. I went through 2 phone interviews the first about 1 hour in length, where they asked me one kind of complex coding question. I was so nervous my brain locked up. It had to do with a function call for a void pointer to a void function. I eventually stammered out a response. It seemed to me that they were looking for people with experience working with very large programs(25,000 lines+). I got off the phone and figured I blew it. 2 days later I got a call to arrange a second interview with someone from firmware. I had about a 30 minute discussion and apparently I did well. A day or 2 later I got an email with a programming problem to solve. I was one of 3 people up for a job. This was late Friday afternoon, and I had an exam on Monday. The answer was due by tuesday morning. Bad timing! Although in my discussions with the firmware guy, he explained the long hours and pressure to produce. In discussing this with my wife, we have 3 kids one of which has autism, I decided the job was probably not the best choice for me. I chose to focus on studying and turned out a half decent program to answer the question I was asked. A week later I got an email from Apple, saying that my answer was not the one they were looking for. It was okay with me, as I had a job offer from somewhere I wanted to work and the situation is better for my family. It was the right thing for me. I have had the question posted to my neglected .mac webpage, just incase anyone wanted to see what apple has asked in the past.

Here it is: See what you come up with.


Range allocator
===============

For certain subsystems rather than allocating physical memory, we are more interested in effectively managing address spaces. Write a small simple range allocator. The API would be:

typedef range_allocator_t *void;

enum
{
ALLOCATE_ANY,
ALLOCATE_EXACT,
ALLOCATE_ABOVE,
ALLOCATE_BELOW,
} allocation_flags;

typedef unsigned vaddr_t;

range_allocator_t create_range_allocator(vaddr_t baseaddr, size_t range_length, size_t granularity);
vaddr_t allocate_range(size_t req_length, allocation_flags flags, vaddr_t optional_hint);
void free_range(vaddr_t base, size_t length);


All allocations will be rounded to a size multiple of granularity. Optional hint is not used for ALLOCATE_ANY, for the other option flags it represents the address at which (or above which, or below which) the allocation must take place; it must be a multiple of granularity. If allocate_range cannot satisfy a given request it must return: (vaddr_t)-1;
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.