Mobile Applications Developer

Employer	Symbyo Technologies, Inc.
Job Title	Mobile Applications Developer
Country	Egypt
Job Category	Computer Software
Job Type	Full Time
Description	Symbyo is currently looking for self-motivated problem solver for a mobile developer role. This individual will be comfortable with all aspects of software development, produce quality work in each area and advocate quality concerns in each area. In particular, the candidate must have demonstrated ability and experience in using object-oriented techniques to produce correct, extendable, reusable, and efficient solutions.
Qualifications	The ideal candidate will have a strong applied and theoretical understanding of object-oriented programming in an enterprise environment and will have worked with at least one OO languages over the last 2 years. Experience with mobile technologies, web-based mobile applications, and carrier integration concerns are viewed as highly desirable.
Gender	Any
Education major	Computer Science
Experience	1 - 2 Years.
Salary (L.E.)	Negotiable
Job Contact Person	Mr. Sameh Elgazzar
Job Contact Email	apply online at www.symbyo.com

C++ Software Engineer

Employer	Symbyo Technologies, Inc.
Job Title	C++ Software Engineer
Country	Egypt
Job Category	Computer Software
Job Type	Full Time
Description	Technical professional who participates in design, implementation, and/or support of Software Products and/or Systems. Develops new, modifies and improves, or supports existing software products and solutions. Work is usually part of a larger project. Works under the general guidance of more senior professionals, and decisions are aided by tools and processes. Competency Requirements: • Bachelors Degree in Computer science • 2 years technical experience in C++ • Understanding of prior position level requirements in order to guide a Junior Software Engineer’s education of technical knowledge. • Understands and applies best practices in his work. • Determines and examines software alternatives. Recommends and implements basic software solutions. • Contributes to project planning in the team or local unit. • Assumes additional responsibilities as assigned. • Very Good English Communication Skills
Qualifications	1. Environment: • Has a basic professional theoretical and conceptual knowledge in a specific field of software development, typically acquired via a bachelors degree or professional experience. • Applies basic professional knowledge related to software engineering processes and tools used within the team or local unit. • Quickly develops and applies new skills. 2. Communication/Negotiation: • Effectively uses teamwork skills to interact and collaborate on technical issues within team and department. • Positively contributes to a high-morale/high-performance team culture. • Communicates effectively and shares basic software and component knowledge within and across department work teams. 3. Problem Solving: • Position requires analytical ability and creativity in using existing techniques to analyze and implement basic software solutions. • Recommends solutions to problems/issues that impact the team.
Gender	Any
Education major	Computer Science
Experience	1 - 2 Years.
Salary (L.E.)	Negotiable
Job Contact Person	Mr. Sameh Elgazzar
Job Contact Email	apply online at www.symbyo.com

Business Objects Developer for Bahrain:VAMSYSTEMS

Job description:

VAM SYSTEMS is a Business Consulting, IT Solutions and Services company with operations in UAE, Qatar, Bahrain, USA, Australia, Singapore & India.
VAM SYSTEMS is currently looking for Business Objects Developer for our Bahrain operations with the following skill set and terms and conditions:
Skill Set required:
Skills       
1.        Strong development experience on Business Objects with flexcube.
2.        Should have experience in MS SQL Reporting.
3.        Banking Experience is mandatory.
Domain                : Banking
Experience Required        : minimum 3 + yrs.
Terms and conditions:
Joining time frame        : 2 weeks (maximum 4 weeks)
The selected candidates shall join VAM SYSTEMS – Bahrain and shall be deputed to one of the leading banks in Bahrain.
Should you be interested in this opportunity, please send your latest resume in MS Word format at the earliest at ambili.krishnan@vamsystems.com or call us +91 0476 2681150.

Skills:

Job Reference:	vamvin
Job Category:	IT
Language requirements:
Employment type:	Full Time
Salary:	Unspecified
Degree:	Unspecified
Experience (year):	Unspecified
Job Location:	Bahrain
Address:	Sasthamangalam
Company Type	Employer
Post Date:	27/11/2010 / Viewed 32 times

SQL Server DBA for Qatar:VAMSYSTEMS

Job description:

VAM SYSTEMS is a Business Consulting, IT Solutions and Services company with operations in UAE, Qatar, Bahrain, USA, Australia, Singapore & India.
VAM SYSTEMS is currently looking for SQL Server DBA for our Qatar operations with the following skill set and terms and conditions:
Skill Set required:
Strong administration experience in SQL Server.

Should have experience in production support.

Should have experience in Migration and Clustering

Domain: Bank.

Experience Required : minimum 6 years.
Terms and conditions:
Joining time frame: Maximum 4 weeks
The selected candidates shall join VAM SYSTEMS – Qatar and shall be deputed to one of the leading Banks in Qatar.
Should you be interested in this opportunity, please send your latest resume in MS Word format at the earliest at ambili.krishnan@vamsystems.com or call us +91 0476 2681150.
Skills:

Job Reference:	vamvin
Language requirements:
Employment type:	Full Time
Salary:	Unspecified
Degree:	Unspecified
Experience (year):	Unspecified
Job Location:	Qatar
Address:	Sasthamangalam
Company Type	Employer
Post Date:	27/11/2010 / Viewed 93 times

Resume Building

You've figured out the secret to job hunting: where you want to work, what you want to do, and what you want to create. Now it's time to write that killer resume to make your dream a reality. Here at JobsBlog, we've shared our best resume tips for years so check out a few of our favorite posts to get started. But be sure read through our archives and keep following us for the latest and greatest in resume building technology!

What a recruiter looks for in an initial resume review 

When I do initial resume reviews, there are certain things I'm focusing on in each section. I’d like to share with you what I look for (and don’t look for) in the resume during this quick scan. Of course, keep in mind that every recruiter is different and what I look for in a resume might be different from what other recruiters look for.

• Target job title: I love Monster because I don’t even have to open the resume, I can view the target job title from the candidate’s profile. This can also be seen in the objective statement at the top of the resume. I look to see that the role the candidate is interested in is one that I am recruiting for.
• Technologies: This is very important. If you have experience with a technology, list it. I don’t like viewing resumes that are only about “keywords” and trust me, hiring managers hate it. However, so I can pull your resume in my search results, make sure you have technologies / programming languages you’ve used (ex. OWL, schema, distributed, data mining, IR) listed in the projects on your resume. This also helps me see how long you’ve used a technology and when it was last used.
• Company names: I’m not looking for anything really specific in terms of company names, but it gives me an idea of the size and type of the project the candidate might have worked on. Was it a small scale banking project which 3 team members completed in a month or was it a high transaction number, large user base online service project with a team of 50 that took over a year to complete? Both types of projects are great, but it gives me an idea of the level and type of experience the candidate might have.
• Dates of employment: I look to see if there are any gaps in the resume. I don’t mind those as long as it’s documented what took place during that time (ex. maternity leave, took care of family member, pursued a higher degree, etc). I also see how long the candidate was at each company. Are they a job hopper? Have they had longevity with a company or for a specific project? Have they experienced the entire lifecycle of a product?
• Responsibilities: I look to see what specific pieces they took ownership of and how much they contributed to the projects. When I view a resume that talks all about a project, but it never mentions what the candidate actually did for the project, I wonder if they had a very minor piece.
• Education: I look to see the highest/most recent degree received and what major it was in. Yes, I do look at all degrees, but I zoom in on the last degree received because generally the candidate would have pursued their current interest for that degree. If someone just received their MBA, they are probably looking more towards program management over development. If they had a Bachelors in Computer Science but received their Masters in Biology, they might be looking to go the Biotech route.

Well, that’s about it. Nothing too out of the ordinary, but now you know what I really look for. How many of you are off to make some quick changes to your resume? ;)

The Art of the Resume: How to make a lifetime impression in just 40 seconds…

I’ve been asked recently by some candidates what recruiters ACTUALLY look for when screening a resume. I have worked on both sides of the fence:  I spent several years working at the Career Center for MBAs at the University of Washington, assisting students in how to make their resumes POP, and now I find myself on the other side, looking for something that POPS out of a stack of hundreds of resumes.

Let me first say that every recruiter is different; I can only tell you what I look for. Hopefully some of these tips will help you better understand how your experience and skills can translate into getting that highly desired contact from a recruiter.

1.  Keep a constant log of what you do: This may sound silly, but trust me; it’s hard to keep track of everything that you have done in school when it’s occurring in real time. I have always kept a word document of great things I have done ... i.e. an ongoing list of projects, classes, ideas, deliverables, etc that I have been a part of.  This way, when you are looking for ideas, you have a running tab of things that you have worked on. It’s hard to think of things when you are stressed looking for a job; this way you have it all in one place. For instance, when I worked at Expedia on our referral program, I wrote a paragraph about what I did, who it affected, and what the results were. Then when I was looking for a job that required that kind of experience, I was able to stick in a great bullet point in my resume that matched what they were looking for (it also helps on job interview questions. look to this list before any interview and you will easily be able to look back on all you accomplished).

2.  Results:  Everyone has bullet points on their resume (i.e. “Created new programming tool for current team) … but what many people forget is the results of this. Try something like “Created new programming tool for team THAT RESULTED IN"… and say what happened from it. Think more about how you impacted your environments and less about just the basic facts of what you did. Your resume should be about accomplishments and not just a laundry list that reads like a job description.

3.  Consider your audience:  I like to tell students to have several different copies of resumes that correlate to the jobs that they are looking for. You shouldn’t just have one general resume if you have a million different types of experience. The best resumes are those that aren’t five pages. Maybe you have done a lot; maybe you are a PhD and have published 20 different articles … If the job you are applying for doesn’t care, then it’s okay to leave some things out. If you are applying for an IT job and a dev job, then you should have two different resumes that can highlight your experience for each. Whatever gets your point across is always a safe bet.

4.  Proofing by a stranger: When I was working for the MBA program, I heard a statistic … when applying for a job, you should assume that each person who looks at your resume looks at it for an average of 40 seconds … Although I can tell you that I do look at resumes longer, sometimes it’s that first look that really decides someone’s fate. A great way to help you understand how the overall message of your resume reads is by finding a stranger ... find someone in one of your classes or in your department that doesn’t know you. Ask them if they would look at your resume for 40 seconds; then have them flip the paper over and write down the top 3 things they learned about you. This is a great indicator of what others see when they look at your resume. If they say something like, “Where you went to school, your major, and your first job title,” that’s great! If someone can’t get over some bizarre fact or typo in your resume, it’s a safe assumption that recruiters will notice the same thing.

5.  Don’t write checks that you can’t cash:  We have all been in a situation where we need to make ourselves feel more important than we actually were ... a document such as a resume is not the place to do this… make sure that what you put on your resume can be questioned. The worst feeling that a candidate can experience is having to back track on their resume. Let’s say you wrote on your resume that you were the Program Manager for a release during an internship and that you managed all of the other interns during the summer. If you are in an interview and someone asks you your role and you have to say, “well, I never really managed but I was the lead,” then say it, and state how you made the project better. Don’t make up facts; the truth is more impressive because you can confidently speak about it. It’s better to build yourself up in an interview when questioned than have the rug pulled out from under you while caught up in a story.

Well, those are my 5 cents; I hope they shed some light in resume writing. If you have any other questions, I am open to helping you out. I love seeing people able to not only achieve their potential and greatness but also write about it on a resume, with great results.

Resumes and accomplishments: what, how, and why

  you should list a little of both your job-related accomplishments and your major accomplishments. And good for you for knowing that “accomplishments” are the key here, not just a listing of prior job responsibilities.

I suggest starting with a general, one-size-fits-all resume that will serve as your "template." On this resume, list all the educational, professional, extracurricular, etc, accomplishments that you might want to mention if you were applying for a new job, regardless of what that job actually is. Personally, I update this master document about every 3 months to make sure I’m recording new accomplishments – and even dropping ones that just don’t measure up any longer.

Once you have your master resume, you can use this document to craft specialized resumes for a specific job, a discipline, an industry, or a company. This might mean trimming or deleting some accomplishments that don’t relate at all or don’t help your cause. It will also probably mean re-ordering some accomplishments to put the most relevant ones first or second under prior roles.

Finally, be sure to include a summary statement to the beginning of your resume where you can highlight the most relevant, important, and impressive info right up front.

Head on over to one of my former blogs to watch a screencast that Zoe (the other co-founder of JobsBlog) and I produced a couple years ago to talk about accomplishments on a resume... and the big What, How, and Why. Part 1 and Part 2. (I’m a geek; I know.)

Customizing your resume to fit a job description

 rewriting your resume to match the job description word for word is a good idea. I do think reviewing your resume to make sure that it addresses the responsibilities of a job description is a good idea.

A resume is something very personal. First and foremost it is important that your resume reflects accurate information about your experience. We see some resumes that have every technical skill and acronym known to mankind listed! This is frustrating for recruiters and managers to see, because it's hard for us to figure out your focus.

We don’t necessarily expect that a candidate will be a completely perfect fit for a specific job. Most hiring managers and recruiters I have worked with like to see the following:

• A Summary / Skills section listing things you have done
• An Experience section that speaks in detail how you might have gained the skills listed in your summary. For example, if you have C++ experience it is important to show in the body of your resume where you used this skill or gained this experience. Just listing something like this and not backing it up in your experience is not helpful to us in matching your skills to the job being filled.
• Telling a story with your resume – what did you do personally, what were you responsible for on an overall project, how many products / services have you shipped, etc…

That type of resume is much more likely to get attention than a resume that's just a rewrite of the job description!

Job Hunting

The first step to getting a job at Microsoft – or anywhere for that matter – is to figure out where you fit. Start by asking yourself these questions:
Where do I want to work? While we’re headquartered in the Seattle area, Microsoft is a global company, and our career opportunities span the globe. Begin your search by visiting our Careers Site and selecting the region or country where you want to work (not necessarily where you live now). In the US alone, we have offices in almost every major city – with major development and support centers in Seattle, Silicon Valley, Fargo, Boston, Dallas, and Charlotte.
What do I want to do? We’ve got lots of career paths to choose from, and once you’re here, we invite you to explore as many as possible. But the hard part is choosing where you want to start. If you’re currently a software developer, you might be a program manager, developer, tester, or architect here. And that’s just one example! Great places to meet employees and learn about their jobs – especially in technical careers –are Microspotting and View - and, of course, JobsBlog's Job Hunting posts.
What do I want to create? Systems, servers, hardware, home entertainment, online services, business software, developer & designer tools … These are just a few technologies and products we create. Whether you work in development, sales, marketing, or finance, you directly affect our products and customers – and it’s important to have passion around what you create. To get an overview of a few of major business divisions, check out View and find out what the acronyms Corp R&D, E&D, MBD, PSD, and STB mean to us.
Get started with a few of our favorite posts:
Can I get a job at MS without a degree?
How do I get a recruiter?
Get your name out there
How much does GPA matter?

What is your greatest strength? What is your greatest weakness?

 what you should say when an interviewer asks you to describe your strengths and weaknesses.  The  great answer is :  Tell the truth.   

This is not a trick question, and the interviewer just wants to learn more about how you work and determine if you have good self-assessment skills.  After all, one of the values Microsoft requires of its employees is the ability to be “self-critical, questioning, and committed to personal excellence and self-improvement.”  No one’s perfect.  Not even BillG. :)   

That said, “Tell me about your strengths and weaknesses” is probably the most frequently asked interview question (not just at Microsoft), and it’s smart to be well-prepared with a good answer.  You definitely don’t want to say, “Uh, I’m really lazy.”  Be ready!  

As an avid Apprentice watcher, I will once again make a comparison between that entertaining (albeit pathetic, at times) show and it’s less cool cousin … real life.  In last week’s episode, Bill was asked what his biggest weakness was, and while he did have the right idea, his answer was not great.  He told his interviewer that his biggest weakness is that he is never satisfied.  The good part is that he thought of a weakness that could be a positive if properly controlled, but the bad part is he, quite honestly, sounded pretty cheesy and insincere with that answer, and his interviewer immediately realized that.

I’m not unlike Bill.  I remember when I interviewed for my job at Microsoft, I was asked this question, and I answered with the most cliché thing possible (which at the time, I thought was quite brilliant.)  I told my interviewer that I’m too much of a perfectionist.  I thought I was so clever to think of something most people would think was a strength and make it a detriment.

 Sometimes I still can’t believe I got this job.

Luckily, my interviewer pushed me harder on this question, and thankfully, I pulled it out of the water.  When he asked me to elaborate, I told him that since I am a perfectionist, I have the belief that if you want something done right, you have to do it yourself.  Consequently, I have a really hard time delegating tasks to others, and in the end, I often work overtime to finish a project, I walk away bitter, and my teammates feel like they don’t get to contribute as much as they would like.  I told him I was aware of this weakness, and I was working very hard to be a better team player.   I continued by telling him a specific example about a group project I had recently worked on back at school where the team assigned specific responsibilities and goals to each person … and so on and so forth.

 When the interviewer asked me my greatest strength, I think I again answered with the same statement:  I’m a perfectionist.  But this time I elaborated about how results and quality driven I am.

 I am by no means saying my answer was the best I’ve ever heard.  In fact, it was pretty lame.  I was 22; that was my first “real” interview; and I think I got lucky by having an interviewer who allowed me to go back and qualify my original answer.   But I think I did do a few things right.

 So my tips on the strengths/weaknesses question:

1. Anticipate this question, and write down your strengths and weaknesses before the interview.  Maybe think of three each. 
2. Ask the interviewer to clarify the question.  Depending on the type of interview, this question may be getting at general competencies, technical skills, teamwork situations, etc.  Always make sure you understand the question before answering.   
3. Be prepared to explain why you believe your assertion and provide specific examples which illustrate this strength or weakness in action.
4. If discussing a strength, explain how you’ve used your strength to help others perform better and improve the quality of work you were producing.  If discussing a weakness, be prepared to talk about lessons you’ve learned and your plan for improvement.

Above all else, remember this:  Everyone has strengths and weaknesses, and interviewers know you are not perfect.  They are not trying to expose your flaws, but rather they are trying to determine what unique attributes you bring to the table and, mostly importantly, how you identify and adjust for your shortcomings. 

Be yourself … and prepare for this question. :)