4 ms·

I find that most jobs for small companies are unspecialised Jack of all trades. The smaller the dev team, the more you will be pitching in with product design a

I find that most jobs for small companies are unspecialised Jack of all trades. The smaller the dev team, the more you will be pitching in with product design and dev ops etc. I'm not sure how you can filter for such jobs, given that job descriptions are always vague - but maybe for each job description see if you can find out the company and then research if they are a small startup for small business, or a large company with a culture of small teams that do everything for themselves for one product (rather than a team for architecture, a team for python, a front end team etc..)

deleted 6y ago
[deleted]
wolco2 6y ago
Angellist might be a good place to start.
etothepii 6y ago
I don't think it's just small companies, it's any team that doesn't have a focus on technology. The power of computers is so vast that a moderately competent technologist can deliver enormous business value if they really get to understand the business problems a non technology team is trying to solve. This could be anything from a legal team auto billing a six minute unit for every email received to using python to combine excel workbooks. This is why we're building https://peerwyse.com https://peerwyse.com. We think finding people with good salaries from your LinkedIn network who you think of as your "skill-set peers" will identify opportunities in their industry that traditional job-title based searches can't reveal.
- andrewf 6y ago
  +1 to the focus on "team" instead of "company". Inside a large company, the largest and most prestigious initiatives will be well-staffed with specialists, and a bunch of management types to coordinate them. But even if the company has a tech focus, you'll also find teams of network administrators, billing folks, supply chain people etc who are struggling to have their needs met. Typically their story is "we can't get out of our manual processes quickly enough", and they will be worried about a high manual error rate and/or scary headcount projections. These teams don't have a product manager or UX designer because (1) they don't need 40 hours/wk (2) those folks will gravitate towards public-facing products. They don't have a deep bench of backend specialists and frontend specialists. They also struggle to get support from centralized teams, because they're a lower priority or they just don't know how to ask. This creates opportunities to unblock the team by jumping in and helping with data/analytics, deployment, testing... all the stuff you might expect to be "cut a ticket to the team which owns this" in a large company.

deleted 6y ago

[deleted]

wolco2 6y ago

Angellist might be a good place to start.

etothepii 6y ago

I don't think it's just small companies, it's any team that doesn't have a focus on technology. The power of computers is so vast that a moderately competent technologist can deliver enormous business value if they really get to understand the business problems a non technology team is trying to solve. This could be anything from a legal team auto billing a six minute unit for every email received to using python to combine excel workbooks. This is why we're building https://peerwyse.com https://peerwyse.com. We think finding people with good salaries from your LinkedIn network who you think of as your "skill-set peers" will identify opportunities in their industry that traditional job-title based searches can't reveal.

andrewf 6y ago
+1 to the focus on "team" instead of "company". Inside a large company, the largest and most prestigious initiatives will be well-staffed with specialists, and a bunch of management types to coordinate them. But even if the company has a tech focus, you'll also find teams of network administrators, billing folks, supply chain people etc who are struggling to have their needs met. Typically their story is "we can't get out of our manual processes quickly enough", and they will be worried about a high manual error rate and/or scary headcount projections. These teams don't have a product manager or UX designer because (1) they don't need 40 hours/wk (2) those folks will gravitate towards public-facing products. They don't have a deep bench of backend specialists and frontend specialists. They also struggle to get support from centralized teams, because they're a lower priority or they just don't know how to ask. This creates opportunities to unblock the team by jumping in and helping with data/analytics, deployment, testing... all the stuff you might expect to be "cut a ticket to the team which owns this" in a large company.