‘Product engineers’ vs ‘Software engineers’ in startups
61–70 of 128 posts
Re: ‘Product engineers’ vs ‘Software engineers’ in startups
#62Great article. Here are some examples of how you know if you have a software engineer or product engineer at your startup (real experiences from me): CEO: We need to add a product search to our website so customers can easier find the products which they like. SE: Ok - and walks off and builds a search box into website. PE: Ok - walks off and builds a search box into the website. Also logs all search queries with zer…
> PE: Ok - walks off and builds a search box into the website. Also logs all search queries with zero results into a big table to give the startup a better insight into products which customers want, but couldn't find. This one confused me. Shouldn't you be logging as much as possible anyway? There's going to be so many things you can't predict ahead of time with this kind of stuff.
Logging, auditing, anything that isnt immediately available to solve the next problem is often disregarded until "wow it would have been nice to know..."
Re: ‘Product engineers’ vs ‘Software engineers’ in startups
#63Earlier quoted context omitted.
So a 'product engineer' is a 'good software engineer'? Unless you are a drone you should always ask the questions of why something needs to be done before implementing it. The engineering part of software development has to be done before you start typing on a keyboard.
The product engineer is just a software engineer with more experience is the main take away here.
Re: ‘Product engineers’ vs ‘Software engineers’ in startups
#64Shouldn't all 'software engineers' be 'product engineers'? I don't really get his point, all he's describing is what any good engineer should be doing anyway.
A long long time ago, I started my first job out of college and that is what was expected of us. Seeking more information and questioning decisions made by those above you were part of the job, and you were expected to do it respectfully, productively and with no doubts about your intention to find the best solution regardless of whether you thought of it or not. You even had a mentor available to help you do that (because it is not something that comes naturally to most people).
In my completely unrepresentative sample data set, this is not what I see today.
I see engineers that are convinced they are right and refuse any guidance from the "olds", yet they consistently focus on relatively tiny components rather than the system as a whole. They think the customer is a simple construct rather than a complex entity of multiple people/departments all with their own motivations and needs.
I see managers and bosses that expect orders to be carried out without question, yet have no idea how any of the technology works or that there may be multiple ways of accomplishing something, whereby some options have complementary effects on other business functions.
Re: ‘Product engineers’ vs ‘Software engineers’ in startups
#65I worked at a startup as the first Dev, it was a shock for me having to now consider things like: * What company laptops to buy? * Assess the merits of AWS and GCP and make a decision. * Divine an architecture that will get the product to the customers ASAP but will last at least a year with growth before needing a major rethink. * Present to customers, board members and potential investors about the tech. Eventually…
What about London took its toll? I've been contemplating a switch from NYC to London. I know it will be a 30-50% pay cut, but I've been told by other's who have lived and worked in both that it is worth it for the better work/life balance.
1. Too. Many. People. You can barely book a restaurant or get a seat anywhere. 2. Nothing works. Trains, airports and mobile network reception. 3. Commuting. Rush hour is crowded, the tubes are disgusting, getting anywhere across town takes at least an hour so you rarely want to risk trekking somewhere unless you know it will be worthwhile/you can get in. 4. Renting / moving house is super stressful. Estate agents are constantly exploiting you.
A whole bunch of my friends raved about London a few years ago which is why I came out but I don't think it is what it used to be. That being said, there is a lot of opportunity here and you can earn well if you hustle. I'd suggest you look at starting out as a contractor.
I think there are better places to live and work in tech, in other European cities like Berlin, Stockholm and Amsterdam.
Re: ‘Product engineers’ vs ‘Software engineers’ in startups
#66Earlier quoted context omitted.
Londoner here. I've never worked in NYC but having been there for pleasure I can tell you things like commuting will be a lot easier (possibly even cheaper? Weekly tickets will set you back 35 quid if you commute from zone 1 and 2). My wife is American and recently quit her job with Delta (she's done both office jobs there and she's also flown as an FA). And based on her experience I can tell you you'll have a much b…
More typically you will be commuting from further out Zones 1 and 2 properties are SV levels of expensive - your looking at £4k to 5k year for a season ticket from an affordable area.
Re: ‘Product engineers’ vs ‘Software engineers’ in startups
#67Great article. Here are some examples of how you know if you have a software engineer or product engineer at your startup (real experiences from me): CEO: We need to add a product search to our website so customers can easier find the products which they like. SE: Ok - and walks off and builds a search box into website. PE: Ok - walks off and builds a search box into the website. Also logs all search queries with zer…
CEO: I want X....and Y, Z, and enhance A-F, all yesterday
SE: you outsourced me last month!?
PE: I can’t do anything without more specs
Or
CEO: I want X
SE, PE: 3 months later deliver X
Sales: Customer doesn’t want X, wants Y and Big Deal deadline is tomorrow
CEO: drop everything, R.I.P. out X and build Y and ship it tonight!
Re: ‘Product engineers’ vs ‘Software engineers’ in startups
#68Great article. Here are some examples of how you know if you have a software engineer or product engineer at your startup (real experiences from me): CEO: We need to add a product search to our website so customers can easier find the products which they like. SE: Ok - and walks off and builds a search box into website. PE: Ok - walks off and builds a search box into the website. Also logs all search queries with zer…
Re: ‘Product engineers’ vs ‘Software engineers’ in startups
#69Earlier quoted context omitted.
What about London took its toll? I've been contemplating a switch from NYC to London. I know it will be a 30-50% pay cut, but I've been told by other's who have lived and worked in both that it is worth it for the better work/life balance.
I'm German, but was working in the US, but gave up the higher pay to the better health care, and quality of life in Germany.
My experience as a healthy person in US is mixed. I rarely need things, but it is hard to navigate the complex insurance business when I do try to get things. I see many people, meanwhile, one accident or illness and it sets them back a long way financially.
Re: ‘Product engineers’ vs ‘Software engineers’ in startups
#70Would people please stop shitting on php. It's no better nor worse than let's say, ruby. It gets shit done. It is a valid tool very widely used in the wild.