Even if you think your resume looks great, let a seasoned recruiter take a look. I’ll give you an honest assessment of whether your resume needs work or not for free! Then I’ll personally work on it after discussing your background with you over the phone. Email me at techruiter1@gmail.com for a free consultation.
In an IT service company the most important business function is that of sales. You can have the best ideas in the world, the best personnel, and the brightest management but if your sales team falls down the entire operation will fall down.
Having an effective sales strategy as well as the right person to implement can it mean the difference between a successful innovative operation and a dud. I have seen several companies with good potential fall flat when it comes to sales. The number of sales people notwithstanding, if the sales strategy is not effective and there is no drive behind implementing it the product or service will not be marketed effectively.
Sales and marketing come hand in hand and while large companies separate the two, in a small firm the function can be combined into one individual with a commensurate salary.
When choosing your team, a startup must be exceptionally judicious about who they hire. A misstep particularly in the sales department will thwart successful operation. The only way to resolve a situation like this is to reassess the sales approach and either replace the weak link or coach the fumbling sales team to success.
Inability or unwillingness to change the business process in the face of adversity will bring down a business despite the best efforts of management.
The Volere Requirements Process is a full lifecycle method for gathering project requirements.
Requirements Types
Functional requirements are the fundamental or essential subject matter of the product.
Nonfunctional requirements are the properties that the functions must have, such as performance and usability.
Project constraints are restrictions on the product due to the budget or the time available to build the product.
Design constraints impose restrictions on how the product must be designed.
Managing RFC’s(Request for Change). If you can’t lock in your stakeholders to some basic delivery guidlines you coudl be headed for a requirments gathering nightmare.
A detailed version of the Volere Process can be found here .
I model my resume on the resumes of consultants I work with. But in general a resume should be clear and should give a manager glancing over it a good idea of your technical capabilities. I’ve seen managers raving about 1 page resumes, but I don’t agree that a 1 pager does justice to someone’s experience.
Furthermore, there is always a mixed review on cover letters, I don’t really pay attention to them since they don’t say anything to me. Your resume should spell out what, where, and how. Chances are that if you do not have something in your resume a cover letter will not save you from the trash pile. I have also received quite a few resumes with the cover letter addressed to the wrong company. What do you think happens to that resume?
Use action words such as develop, lead, recruited, gathered, analyzed, managed. Do not write prose “I was responsible for blab la bla… “ boring and slow. You want your resume to be crisp and sharp.
Feel free to email me for any questions! Comments are welcome. You can take a look at my resume for an example.
The unified modeling languege is a standardized specification language for object modeling. UML is a general-purpose modeling language that includes a graphical notation used to create an abstract model of a system, referred to as a UML model. http://en.wikipedia.org/wiki/Unified_Modeling_Language
While RUP is
The Rational Unified Process (RUP) is an iterative software development process framework created by the Rational Software Corporation, a division of IBM since 2003.
RUP is not a single concrete prescriptive process, but rather an adaptable process framework, intended to be tailored by the development organizations and software project teams that will select the elements of the process that are appropriate for their needs. http://en.wikipedia.org/wiki/Rational_Unified_Process
If your prospective BSA cannot explain to you the difference between these two core BSA concepts, reload your search…
I came across an article by John Osher, the inventor of the electric toothbrush, where he discusses some common mistakes made by entrepreneurs. I’ve selected a couple of glaring mistakes and a link to his entire article.
Mistake 8: Bringing in unnecessary partners. “There are certain partners you need. For instance, you often need money, so you’re going to need money partners. But too many times, the guy with the idea takes on all his friends as partners. Many people don’t provide strategic advantages and don’t warrant ownership. But they’re all going to get 25 percent of the company. It’s totally unnecessary, and it’s a mistake. Before people are made partners, they have to earn it.”
Mistake 9: Hiring for convenience rather than skill requirements. “In my first business or two, I hired relatives. It was easy to do, but in many cases, they were the wrong people [for the job]. And it’s hard to fire people, especially if they’re relatives or friends. More time needs to be spent handpicking people based on skill requirements. You really need super-skilled people who can wear more than one hat. It just bogs you down when you hire people who can’t do the job.”
Mistake 10: Neglecting to manage the entire company as a whole. “You see this happen all the time. They’ll spend half their time doing something that represents 5 percent of their business. You have to have a view of your whole company. But too often, the person running it loses that view. They get involved in a part, and they don’t manage the whole. Whether I do this product or that product, whether I hire somebody, [I consider] how they [will] fit long term and short term in the big picture. Constantly try to see your big picture.”
The key to this answer is understanding that an ENTITY CLUSTER is actually a “virtual” entity type and that the entity cluster is formed by combining into a single abstract object multiple entities that are related to one another. This abstract entity object is not a single entity as documented in the final ERD.
When performance issues outweigh design considerations. Sometimes too much normalization can slow down performance.
If the candidate understands this concept it’s a good thing… if not, you have an issue.
Web 2.0 applications developed using standard Java™ Platform, Enterprise Edition 5 (Java EE)-based approaches face serious performance and scalability problems. The reason is that many principles that underlie the Java EE platform’s design — especially, the use of synchronous APIs — don’t apply to the requirements of Web 2.0 solutions. This article explains the disparity between the Java EE and Web 2.0 approaches, explores the benefits of asynchronous designs, and evaluates some solutions for developing asynchronous Web applications with the Java platform.
http://www.ibm.com/developerworks/web/library/wa-aj-web2jee/
Having a blog in the world of Web 2.0 recruiting is probably one of those things that will set you apart from other recruiters. Many technical recruiters describe themselves as “non-technical”, which always amuses me a little. I like to think of myself as a business analyst/sourcer. Functional understanding of client systems is just as important as finding the right candidate for the job.
I’ll be posting interview questions, my experiences, questions for other recruiters, and job opportunities.
