Loading...
Answers
MenuWhat are important qualities that a startup developer should have?
This question has no further details.
Answers
Cross-functional, proactive, user focused: you do not want somebody who will stop if he does not have a wireframe to work from or who will not plan for common error messages just because that was not in the specs that were given to him. You need someone who loves the product you are building and not just someone who can write good code.
The ideal candidate should be able to look at the big picture. If the candidates are new, their prior projects should always be considered in hiring. I've hired many developers who promise the world, but do not deliver. The finger often gets pointed back at you, and sometimes, their right. Good developers are easy going and take the hits with you. Communication is also paramount.
It depends on the stage of the startup. If you're talking about a green field project, then it's super important for the developer to have strong analytical skills and somewhat of a business sense (if they're going to be taking requirements from non-technical sources and trying to develop something from scratch).
If the startup is a bit more mature, then finding someone who has the 'fire in the belly' and deeply believes in what the company is trying to achieve is one of the most powerful things you can hope for in a developer (assuming they also have the technical ability to perform).
Flexibility is always something sought after as well. Startups often pivot and change directions often, so startup developers need to have thick skin when a project they're working on doesn't pan out, or the company needs to pivot in a new direction. This is why I always look for developers who understand that business needs drive development, not vice versa.
Ahh a topic very close to my heart. Attitude is the number 1 attribute to look for. The developer needs be able to problem solve, be prepared to work long hours, is either single or has a partner that understands what it takes to succeed in a start up. Likes to be part of a team and either has business nouse or at least understands there are business imperatives not just coding ones. Ideally their ambition is to code or at most manage good coders and to be part of team that runs a successful business. Finally, good solid coding experience that is well designed, commented and documented. Oh one more thing. You need to get on with them as a start up partnership is fun, tumultuous and rewarding as a marriage.
1) a startup developer should be a good developer. Startup is not a place for an average developer.
2) a startup developer should have "get it done no matter" what attitude.
Well, I'm an app developer myself and worked with many startups (as developer for hire) and also run my own app agency, so this is what I believe:-
1. A startup developer should be aware of the real implication of his code and also the target user group; he must know the sensitivity of rolling quality builds quickly; and its direct impact on business.
2. He should be an "engineering" mind and not just "coder" who can't think beyond their technology stack. He should always be concerned about the next generation of technologies and be ready to take the challenge for staying on edge of competition.
3. A little entrepreneurial attitude (at least ownership, accountability, time management) is always important.
And that's it, rest can be managed or fine tuned if attitude and approach is right.
I've personally experimented with my developers and figured that if you just change the "approach" with which they take the work and give them little more sense of "ownership" (combined with offering tangible incentives of success) their whole efficiency goes to another level and also the outcome product becomes better.
Btw, anyone looking for a developer right now can contact me and I can get them in touch with real vetted developers (and not freelancing site kind of guys) on my responsibility and professional image.
It all starts with identifying a good developer when you see one. It can do wonders when accompanied by other developer strengths, though. Luckily, the presence of key strengths and qualities of a software engineer is super easy to verify with coding tests. But. If you come across a promising candidate who exhibits all the developer strengths but is still learning, consider hiring them for a junior position.
You can read more here: https://devskiller.com/qualities-great-developer/
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
Related Questions
-
How can a small offshore development company find companies/software sales people to sell their service in the US/UK?
My company does a lot of consulting with offshore firms who are looking for a way to generate new business, so I hear this question a lot. My first reaction is that you need to totally reverse your mindset when you talk about your own company. You mentioned that you have: a great software developers team, proven track record, passion, real value But, everyone says that. There a 10,000 companies that have those things, so a customer isn't going to notice it. You need to figure out what your company is best at (doesn't have to be technical) and present it as a solution to a specific problem that clients have. Maybe a speciality, or really good project management, really good communications, a special expertise or experience, a personality, experience with a certain type of client.. really anything.. But, there must be some thing that makes your company 'special' otherwise you will be lost in the mix. Don't worry about things like rates, or the fact that you have 'great' developers. Those are generic. Think about why a client would really choose you, and try to build on that! After you understand your company identity, it gets much easier to identify and engage marketing channels because you understand your target.DH
-
I have a great app idea, and I need help bringing it to life.
I'm not sure if this is how you imagine this world to work, but at least according to the order you wrote it "raising funds" was first. In reality it should actually be one of your final steps of the stage you are at right now. It may even come after a year or two! So you have this great app idea, and you're looking for a place to start... Don't! Don't start yet before you decide whether you have what it takes to get into a roller coaster that can ruin your life and make you miserable! Not trying to scare you but I think most people only hear about these great success stories. They have this dream of maybe, possibly, becoming the next big thing... Because they have the best idea for an app... You don't hear about the failures so often. And even if you do, you don't hear about what the founders of these failing startups had to go through. Truth is you are most likely gonna fail. And I'm saying that without even knowing what your idea is. There are so many barriers on your way that even a great product with a great team is likely to fail. Some people would say "I'm not afraid of failing", "It's good to fail cause you learn", "Failing will make me stronger for the next startup". That's somewhat true but it doesn't mean that failing is easy. As oppose to what people sometimes say - you do not want to fail! It's very painful!!! You have to understand what failing in a startup means. You can work your a$s for 2-3 years, have little to no salary, waste other people's money (most likely your friends and family first), lose friends, fight with your partners, your family, your spouse, devote 20 hours a day for your startup all this time, forget about the little and big things you used to enjoy in life, and only then, after debating 100 times whether you should quit or not, you finally decide that it's not gonna work and you've failed. Disappointing your family, your investors, yourself. Trust me it is painful. Are you sure you wanna do this to yourself? If yes, give me a call. I have the experience you need! From idea stage, to proof of concept, to running beta tests, getting millions of millions of users in ways you can't even imagine, creating features and experience that will make these millions of users completely addicted and viral, raise money in a smart way, hire the right people, find a great co-founder, succeed, fail, be persistent, and enjoy the ride! Good luck, RoyRM
-
How can I take an idea for a new app and turn it into a real product?
Here are some options: ___Free Options___ 1) Make apps without needing to spend a lot of time learning to code. Look into "MIT App Inventor" (http://appinventor.mit.edu/explore/). It's a very _easy_ way to make pretty complex apps using drag and drop coding. You can find youtube tutorials that will show you how to make your first app within 5 minutes. I've used MIT App Inventor to make prototype apps for many of my ideas, saving me tens of thousands of dollars if I paid a dev to do it instead. Learn to do "real" coding yourself. The main investment will be your time. There are plenty of free resources for learning coding on the web. I'd suggest learning "React Native", it's a relatively new way to code apps, which allows you to make one app that will run on both Android and iOS. 2) Find a software engineer cofounder. Go to Meetups, conferences, local hackerspaces / makerspaces. Hang out on relevant online forums (e.g. https://www.reddit.com/r/startups/ make sure to read their rules for posting before posting though). It won't be easy to find a tech cofounder, your idea will need to be amazing, and you yourself will need to be very passionate and capable in order to convince someone to partner up with you for sweat equity. ___Paid options___ 1) Use developers with less established reputations / portfolios (lower cost, higher risk) Be very wary of freelancers on sites like Upwork, Fiverr, etc. Here are some basic hiring rules: In your hiring script, make sure to ask for all applicants to give their account name for github/bitbucket and Trello. Don't hire agencies, only hire individuals. To get hired, ask them to do a simple task via Trello and submit the code via github/bitbucket. This task should only take them maybe 1 hour. Check the quality of what the applicants and if they deliver it in a timely manner. Keep the 1 or 2 people that do a good job. If you don't do this vetting these "low cost" developers may end up costing a lot in the longer run. 2) Use developers with more established reputations / portfolios (higher cost, lower risk) With this option your app will probably cost > $20k to develop, but it can be worth it if you have a single idea that you know you want to move forward with. I can introduce you to a very high quality developer in NY if you're at this stage. Let me know if you'd like any additional help more tailored to your specific app ideas, best, LeeLV
-
How do build a empowered and motivated engineering team?
I am assuming your question is more pertaining to empowering and motivating (rather than hiring). I can outline some of the practices I have seen really result in high motivation and sense of ownership among engineering teams: * Empathize - Your engineering team will work well and be more motivated if they see you as one of them rather than a person who doesn't understand their function. Show your geeky side to them, and show that you understand their thought process and drivers. * Pick their brain on big and small decisions (roadmap, usability, whatever it is) - Product teams value being heard. The more you position yourself as someone who is WANTS to listen, is keen to have their inputs, you will be surprised at how involved they can get, and also how you can actually tap into a lot of smart ideas/thoughts from them that you can develop on. * Take care to explain - show how you arrive at decisions. Share your research, competitive analysis, and even your thought process on arriving at a feature set or list of things for a release. Its stuff you would have worked on anyway - so no harm sharing with more eyes! * Share customer feedback - nothing motivates your engineers than a positive interaction with a customer. Get them to see customer feedback. Have them sit in and observe some of the usability studies. (B2B - have them see you do some demos or do a successful sales pitch) * Send out interesting articles, insights, business and tech articles with your comments/highlights to them on a regular basis (maybe twice a week?) - maybe even some analysis you did on competition or customer feedback * Engineers like working with people they feel are competent and complement the work they are doing to build a great product. So make sure they see how everyone else around them is also doing a good job and adding value and contributing to the success of the product. * Be transparent about the product/business - Make them feel they are responsible and involved in the business, not just technology. I've seen engineering teams happy about their annual goals having components relating to making revenues, keeping customers happy, or reducing costs. If they are enthused about the business as a whole, they will be more motivated with their engineering efforts * Have a mix of little experiments, R&D, attending to engineering debt, in addition to bug fixes and new features that each engineer gets to spend some time on (based on their interest) * Finally get to know each of your engineers personally, and be aware of what their priorities are. Each of us has different motivations in life, so there is no silver bullet to motivate people. When they know you care for them, they are more motivated :).SG
-
What's the best way to build a MVP web app that handles order management, purchasing, invoicing, supplier management and inventory?
The best way to build an MVP for any SaaS product is to create a landing page that looks like a real product. Here's an example of one I built. http://www.happiily.com In this case, it advertises the primary features of the product and invites people to sign-up. When they do, they are asked for information which qualifies the person and then sends me an email. I built this quickly and very inexpensively and started getting inbound leads from it shortly thereafter. I got on the phone with each person who signed-up and explained the features I wanted to build and was able to do a lot of customer learning based on that. Happy to talk to you in a call if you'd like to talk more about customer development with SaaS products.TW
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.