Form – DevReady

Name*

Full Name

Email*

Profile Picture*

Provide us with a business professional picture that includes only your face looking at the camera, from the shoulders up, and cropped tightly.

Drop files here or

Profile Summary*

Use your own words to define yourself as a professional software developer. This is your chance to create a great first impression with a client. Please limit your summary to 3 or 4 sentences.

*

Social Media	Url

Examples: LinkedIn and GitHub

Your Skills

Clients want to know what you know, to see if you are a solid match. Take the time to add all your skills and the years of experience. ~15 minutes to complete.

*

Skill Name	Years of Experience

Feature Experience

Every application and project you have worked on has notable features. Use this section to call out the top areas you have worked on throughout your career. A few feature examples are data ingestion, monorepos, search, authentication, platform migration, and microservices. Fill in 4 Feature Experiences.
Level: Expert, Extensive, Moderate

Feature Name 1*

Feature Level 1*

Feature Name 2*

Feature Level 2*

Feature Name 3*

Feature Level 3*

Feature Name 4*

Feature Level 4*

Cultural Experience

Your work has been within a certain domain, field of knowledge, or industry. Use this section to list the areas you have most worked in. A few cultural experience examples are insurance, banking, e-commerce, government, media, automotive, marketing, blockchain, Agile, and Scrum. Fill in 2 to 4 Cultural Experiences.
Level: Expert, Extensive, Moderate

Cultural Name 1*

Cultural Level 1*

Cultural Name 2*

Cultural Level 2*

Cultural Name 3

Cultural Level 3

Cultural Name 4

Cultural Level 4

Your Developer Personality

There's more to matching you with a client than just technology and skills. Help us understand the work environments, cultures, scenarios, and team dynamics that you prefer so we can get the right client fit for you. ~15 minutes to complete.

Using the following scale, please give your opinion on the statements below.
0: Strongly Disagree, 3: Disagree, 5: No Opinion, 7: Agree, 10: Strongly Agree

The best software is built when the architectural vision comes from one person rather than multiple people with many ideas.

You will only use libraries and frameworks in production software if the technology has had significant time to mature in the larger community.

Writing Unit tests is valuable, but it’s a luxury.

You love to lock the door, turn up the music and just crank out code.

The painful process of re-architecting an application with different technologies is usually not worth the benefits.

You usually focus your learning and research only on areas that are relevant to the project that you are currently working on.

The more documentation and comments you make, the better.

You will start using a technology you want to use in production software even if it’s only one year old or less.

You think that ideas get better when openly discussed and challenged by the group.

You’ll work with the lowest levels of programming such as C or C++ to improve performance.

You are a go-to resource for many in your company because you can provide a fairly deep level of knowledge about various areas of development that extend well beyond your current area of focus.

You are quick to go to the whiteboard to sketch out the problem and the possible solutions.

With technology moving so fast, you are always on the look-out for the next area where you will dig deep and make your mark.

You often ask questions and float your ideas with the team because you value outside eyes on the problem and solution.

You should spend significant time planning how the project will be executed so that when it’s time to start coding the big decisions will already be made.

You consider yourself a Jack of all Trades when it comes to what part of the tech stack in which you like to specialize.

You prefer to work in an open environment with high levels of open communication.

You often upgrade 3rd party libraries that you leverage in your software to the latest version as soon as they are available.

You prefer to discover problems as you build the application and learn how to solve them then instead of predicting what may go wrong.

You think time-tested tools and frameworks are much better than new tools and frameworks that have not yet stood the test of time.

You are always looking to broaden your skill set rather than focusing on two or three specific areas of skill.

If the lead developer can build the entire solution on their own, they should. More developers are only needed if they can't and need to delegate some tasks.

You don’t enjoy making product decisions. You would much rather be given a list of clear tasks so that you can go heads-down and knock them out.

You like to use new tools and libraries in production software even if the tools are not very mature and the community isn’t very large.

You don’t see much value in low level tasks like bit-shifting and pointer arithmetic.

Clearly defined rules and processes for a team’s SDLC are needed for projects to have successful outcomes.

A team approach often doesn’t produce as many breakthroughs as an individual going heads-down on a problem by himself.

You like to be knowledgeable and proficient in areas of software development and software production that is not part of your day-to-day responsibilities.

Developers should only innovate incrementally and should be very careful when considering large steps forward.

Software features should be completed and made good as possible before you release them vs releasing and then building upon.

While popular web frameworks and libraries can build powerful applications quickly, you think that many of them go too far in abstracting away the lower-level code processes.

You find that your code quality is much better when you collaborate closely.

Often, in order to meet deadlines or push projects forward, organizations should temporarily ignore deep technical issues.

You prefer to spend significant time early on in development making every performance optimization you can think of.

You don’t see the need to update your tools in the foreseeable future because they do everything that you need them to do.

Staying knowledgeable about the lower level and source code behind modern frameworks, libraries and languages is very important.

You don’t like to spend too much time planning for hypotheticals. You believe it’s better to cross those bridges as you come to them.

You consider your expertise focused on one specific area of the stack vs knowledge of the whole stack.

You believe that experimentation with the latest and greatest technologies often produces significant gains.

Many of the text book rules and processes in development methodologies like Agile can be a waste of time and not practical for real world / professional development.

You pride yourself in being able to jump in and write code in all areas of an application if called upon.

You prefer rapid prototyping of simple designs vs extensive planning to find a “perfect” design.

When possible, you prefer to be directly in control of lower-level systems such as memory management vs leaving that to the language, framework or library.

Trying to foresee and troubleshoot potential issues that may arise when developing an application is not a productive use of your time.

You find that productivity and innovation increase when you pair program or work in high collaboration with others.

Before you jump into coding a solution to a problem, you like to know your plan of attack.

You frequently look to learn the latest and greatest patterns and practices so that can be as efficient as possible on your projects.

You like to focus on one project at a time.

You prefer tools technologies that are easier / quicker to develop with vs ones that are more demanding but safer.

There’s really only one or two ideal ways to build most software and features.

You think it’s a waste of time to take a team approach when deciding the direction of development.

You believe in using tools that significantly increase the speed of development even if that means taking a performance hit as long as it isn’t a significant performance problem.

Sometimes, teams must compromise quality or skip processes to meet a deadline.

You prefer to specialize in one focused area of development and go deep in that area.

You believe that there must be a very compelling reason to use lower level programming languages like Objective C rather leveraging newer languages like Swift that boost development speed.

You try to plan for the problems you may face when building an application so that you can prepare for these challenges in advance.

You would generally trade a framework that gives you more development speed and efficiency over a framework that gives you more control over the code.

You are an early adopter of technology because you want to enhance your productivity as much as possible.

Your Location

Where you are located matters to clients. We need your city, state, and country in the field below.

Place	Latitude	Longitude

Example : Denver, Colorado, United States of America

Your Portfolio

Build out your individual work experience to show off your talent. Please include your 3 most recent positions that covers your last 5 years of work history. If you wish to include more positions, please limit the Position Description to 1 or 2 sentences each.

Position 1

Company Name*

Position Title*

Example: Senior Software Engineer

Position Timeline*

Example: 2012-2014

Position Description*

Please include a summary of your responsibilities in 1 or 2 sentences max. Below your position summary, include no more than 5 bullet points describing your skills and accomplishments.

Position Skills

Select the skills that you used during this position. If you are not able to find a skill on the list, please make sure it is listed under the Position Description above. Pick up to 3 categories and no more than 2 skills per category.

Features*

Every application and project you have worked on has notable features. Use this section to list the features for this experience. A few feature examples are data ingestion, monorepos, search, authentication, platform migration, and microservices. Fill in 1 to 3 Features.

Features 1 *

Features 2

Features 3

Position 2

Company Name*

Position Title*

Example: Senior Software Engineer

Position Timeline*

Example: 2012-2014

Position Description*

Please include a summary of your responsibilities in 1 or 2 sentences max. Below your position summary, include no more than 5 bullet points describing your skills and accomplishments.

Position Skills

Select the skills that you used during this position. If you are not able to find a skill on the list, please make sure it is listed under the Position Description above. Pick up to 3 categories and no more than 2 skills per category.

Features*

Every application and project you have worked on has notable features. Use this section to list the features for this experience. A few feature examples are data ingestion, monorepos, search, authentication, platform migration, and microservices. Fill in 1 to 3 Features.

Features 1 *

Features 2

Features 3

Comments

This field is for validation purposes and should be left unchanged.

Your Developer Profile

Your Skills

Feature Experience

Cultural Experience

Your Developer Personality

Your Location

Your Portfolio

Position 1

Position 2

Position 3

Resources

About

Let’s Get Started

Your Developer Profile

Your Skills

Feature Experience

Cultural Experience

Your Developer Personality

Your Location

Your Portfolio

Position 1

Position 2

Position 3