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
-
Which is the best hosted free bug tracking tool for a team size of up to 10 members?
Being a freelance developer for the last 10 years or so, I have seen and used almost every project management software you can think of, open-source and closed, and I have found that the "best bug tracking tool" completely depends on your process. I employ and direct teams in an Agile process that involves loose story-based requirements with point-based estimates, two-week cycles of iterative development, planning and retrospective sessions, and look-ahead and show-and-tell meetings with the stakeholders. It's important to me, then, that my tools have a method of capturing all those pieces with as much detail as I need but no more. On projects, I've successfully used Pivotal Tracker, Unfuddle, Redmine, Codebase HQ, Basecamp, Trello, and many others. I usually recommend people to Trello for light, agile management; it's essentially a digitized version of sticky notes and swim lanes. If your team actually needs a full-featured ticketing system, see Redmine (Rails), Trac (Python), or Mantis (PHP), depending on your language preference. Hosting a version of these yourself is fairly trivial, and numerous options exist for cheap or free hosted versions. For something in the middle, Github Issues is a good fit and the open-source clone GitLab.org replicates most of those features nicely. However, if you're looking for a hosted version, you're probably looking to offload that tricky "backup" thingy, and in that case, how important is your data? How proprietary? What's your business model? If you're working on an open-source project, Github will give your team a free account with private repos, issues, wikis, and the like. If you're okay with your project being "readable by all", public projects on Pivotal are still free. I'm mostly a consultant these days, leading small groups of junior or intermediate developers into a more productive, more mature, fully operational teams of senior software developers. One of the first things I teach folks is how to use a project management system... and why! It'll save your bacon if it's simple, effective, and reliable. With a few minutes of discussion about your project, I can probably help you select the right tool and service for your team. Let me know if I can help with that. Best of luck!DR
-
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
-
How should the dynamic between a ux designer and a developer who are working together look like?
It depends a lot of in the skill sets and experience of both people but in most cases the ux designer should be controlling the developer pretty heavily in order to make sure his ideas come through properly. The UX designer may just need to work on his approach so people don't feel bossed around and more like they are working together. In an ideal world, there would be a project manager who makes sure everything is communicated well and keeps the dynamic feeling great.JM
-
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 I run a closed beta test for my mobile application? Development will be finished in 3 weeks.
You should try to engage people using social networks, it is easier to spread than email. The conversion rate on emails are low but is still a valid tool for that. Send and email with a simple and objective message that will make people want to try. The best way to have feedback from users is to watch them use the app. You should put them on the hands of everybody that you can and without any instrucions and just watch, don´t even say that the app is yours. Try to do it a lot. If you want feedback from others, you can include the feedback form inside the app and suggest users to answer occasionally. I would also strongly recommend to use a tool as Flurry Analytics. Is the best way to get data from how is the use of the application. Pay attention to those data and be open to change your app a lot, you may need more features or cut some off to make it easier to use. If you need more help please contact me.BS
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.