We All Start Out The Same Way
When you look at some of the top performers in our industry you quickly think that you’ll never be able to charge what they charge. And it’s quite understandable. I mean, if we look at Brennan Dunn. He charges up to $20,000 per week, that’s intimidating! But then again he’s bringing value to his clients, a lot of value.
That’s why I wanted to reach out to some the people that I look up to and ask them about how the started out with their pricing strategy. The point of this article is to show you that even the top performers started out just like you, by undervaluing themselves. They started with an extremely low rate, probably just like you. We’re talking anywhere from just above $8 an hour! Rightfully some started at around $100, but they sure as hell did not start with $20,000 a week!
They’ve spent years raising their price, fine tuning, testing, failing, doing it all over again, but most importantly not giving up.
Luckily for you they share some great advice, so that you don’t have to spend years trying to figure it out on your own.
Read more here.
Zachary Lukasiewicz via linkedin.
I think this varies from recruiter to recruiter and also depends on the role for which you’re applying. For one, no one reads stacks of resumes anymore. Recruiters hate paper. They do everything online. But I’ll highlight briefly how recruiters absorb a resume. I should preface this by saying that I am not a recruiter. However, since starting with Staffing Robot, I can say that I’ve learned how recruiters operate, and what they tend to look for in a candidate:
Most recent role – this is generally trying to figure out what this person’s current status is and why they might even be interested in a new role. Are they laid off? Did they get fired? Have they only been in their role for a few months? Is their most recent experience relevant to the position for which I’m hiring?
Company recognition – Not even gonna lie, it’s easy to be a company snob. It’s not even that recruiters think certain companies are better than others (although some are). It’s purely a matter of how quickly they can assign a frame of reference. This is often more difficult to do when a candidate has only worked for obscure companies. When they can’t assign company recognition, it just means they have to read the resume a little deeper, which usually isn’t an issue, unless it’s poorly formatted and wrought with spelling errors in which case…you lost their interest.
Overall experience – Is there a career progression? Do they have increasing levels of responsibility? Do the titles make sense? Do the responsibilities listed therein match what they’re looking for.
Gaps – They don’t mind gaps so long as there’s a sufficient explanation. Oh you took 3 years off to raise your children? Fine by me, and might I add, I bow down. You tried your hand at starting your own company and failed miserably? Very impressive! Gap sufficiently explained. Whatever it is, just say it. It’s the absence of an explanation that makes me wonder.
Personal web presence — This includes personal domains, Twitter handle, GitHub contributions, dribbble account or anything a candidate has chosen to list. 2 out of 3 times, they almost always click through to a candidate’s website or twitter account. It can be a recruiter’s favorite parts of recruiting. Random aside: If a recruiter is like me, they care less about what people say on Twitter and more about who is following you and who you follow. So much insight gained by seeing who values your thoughts.
General logistics — Location, Eligibility to work in the US
Overall organization — This includes spelling, grammar, ease of use, ability to clearly present ideas.
Total time it takes me to do all of above: < 30 seconds*
2 out of 3 times, they almost always click through to a candidate’s website or twitter account.
Things recruites wish more people would do:
Bring personality into the resume — Recruiters are staring at these missives all day long. Throw a joke in there somewhere for goodness sake. Talk about how much you love Nutella. If you’re a rockstar, throw some cheeky self-deprecation in there if you can do so elegantly. It’s important to keep the work experience details as professional as possible, but trust me, there are ways to have fun with it. I love an easter egg buried in a resume…figureatively speaking.
Include URLs for other web presences — enough said. And within your comfortability of course. They will get it.
List key personal projects — This should be asked in almost every phone interview. “What kind of stuff are you working on in your free time?” This should be inspiring! Also shows that you have passion for your field beyond your 9-5 (ha, ha, like those even exist anymore).
Use color and lovely typography
No more tab switching! New updates to our portfolio creator allow you to see the portfolio as you build it.
When you import project from GitHub or wherever it’ll show up in your portfolio instantly. The creator and preview stay in sync so navigating on either side will always show you the correct creation or preview page! This is seriously awesome stuff. Did we mention it works with custom templates?
Whoa, it’s been a crazy few weeks here at DevPort! Launch has been going great and y’all have been sending in tons of awesome feedback. One of of the most requested features was tighter integration with other services like Twitter.
Well, check it out. Now you can add your Twitter profile to your portfolio. DevPort will scrape your full name, location, avatar, and about description from Twitter and throw it right into your portfolio.
Check it out.
Websites are constantly updating their design. The technology that Front-End Web Developers use changes just as rapidly. Building a portfolio of websites gives you the chance to prove that you can create modern experiences with the latest and greatest tools.
Via Become a Front-End Web Developer, A Beginner’s Guide
When the word front-end comes up, it mostly refers to how you are designing the User interface to give the best possible user experience to the users.
For a starter I would say try doing some websites that show your skills on building, unique if possible, designs. Take a look at these examples:Adham Dannaway | UI Designer & Front End Developer
Now if you head over to Porfolio:
Design portfolio of Adham Dannaway
It contains a project of each:
Designing UI elements
Web application style products
Designing widgets such as map/chat box/ dropdowns and such
It doesn’t really change that much if you work was accepted by customers, unless it’s a big name that everyone can look up on Internet and can recognize. However, it certainly is a good thing if you show you designed for real projects, not just random work.
If you scale over to Front-end engineering, that includes a lot of other things than just design. It requires showing what kind of Frameworks you have worked with and how much real world projects you have actually taken to production.Check out more portfolio to see what to include:
Portfolio – Ian Lunn – Front End Developer 40 brilliant design portfolios to inspire you
And if you are actively looking for a job as a student graduating,
look into what companies certainly need. Don’t just pile up work, do things that people want. Here is an interview prep for Front-end devs as well:
A portfolio site is the complement to a resume or LinkedIn profile for web development professionals. Here are some tips on creating a winning portfolio site:
Keep it simple: Your portfolio site can do the job with just some background information about you and five to seven pieces of work you’re proud of. No need to overwhelm people.
Add to your site over time: Every time you finish a project, add it to your site right away. When visitors to your portfolio site can see your professional growth and development over a period of years, they can consider you for senior positions on large projects and other desirable postings.
Never apologize: Explanation is fine — “We were on a tight deadline, so this was done in one hour.” But don’t add, “So that’s why it’s lousy,” or “This isn’t my best work.” Put up only the work that makes you proud, even if part of the reason you’re proud of it is that you beat a tight deadline or other constraints.
Use a “real” domain name: Register a “real” domain name, such aswww.firstnamelastname.com. If your name is taken already, include your middle name, add “sf” or similar letters indicating your city to the end of your domain name, and so on. You wouldn’t do less for a client, so make the extra effort for yourself.
Use fake work for confidential projects: If you work on a confidential project, such as an intranet site that’s not explicitly exposed to the public, resist the temptation to put up a screen grab anyway. Instead, create a quick-and-dirty anonymized version, with all identifying information removed.
Include paid work, unpaid work, and fun projects: A portfolio site is perfect for getting some mileage from unpaid work and fun projects. Get hands-on time with new or different tools than you use in your day job and show off the results. This might be all you have at the start of your career, but these “extras” should always be part of the mix.
Link to finished websites: Include links to websites that are up and running, or a screen grab if the site is defunct or has been redesigned since you were an active contributor. Explain your role in the look and feel of the site.
Add a page of influencers: Include a page listing some of your major influences, including the portfolio sites of friends whose work you admire, plus gurus, mentors, and schools. This kind of generosity toward others reflects well on you, and it gives the curious something to do without your having to add a ton of content.
User-test your site on friends: Watch a friend click through your site and capture their comments as they use it. Then fix any problems and showcase the good stuff.
Via Getting a Web Development Job For Dummies
Watching the first DevPort users create their portfolios with DevPort, it was clear that they could use a little instruction. While I work on proper onboarding, here’s a full featured walkthrough of DevPort in video format.
The walkthrough includes:
Login with GitHub
Create GitHub project
Create App Store project
Create Website project
Create Blog Post project
Fill out profile
Deploying your own template
Let me know if anything is confusing, or there is something I didn’t cover. Later videos will explain more about deploying your own template on our Pro accounts.
Welcome to the first of a series called #devportspotlight where we highlight some of the awesome people using DevPort. Today’s spotlight is on Adam Talcott, who is the co-founder at Vilynx, founder of Atomic Powered and creator of QuakeInfo. He’s a computer engineer, mobile app developer and dad of two.
Computer professional with experience in software and hardware engineering. Design, develop and publish mobile applications for Apple iOS (iPhone, iPod touch and iPad) and Google Android, among other platforms. Extensive experience in processor development (architecture, microarchitecture and verification), performance modeling, and performance analysis.
His portfolio is full of feature filled apps, including an app to store your videos on the cloud, one to get notified of earthquakes, and even an app that acts as a virtual napkin for ideas!
Check out Adam’s full portfolio and get in touch with him here.
Awww yeah. Welcome to the DevPort blog.
DevPort is a portfolio tool built just for developers. It imports your work from places it already exists online into a sweet portfolio.
DevPort imports images, screenshots, text, and reademes from:
More info, screenshots, and videos to come!