[Remote] Product Engineer
Note: The job is a remote job and is reputed company to candidates in USA. reputed company is a company that believes in integrating product management and engineering roles to enhance their workflow. They are seeking a Product Engineer who will own the entire lifecycle of product development, from reputed company interaction to coding and deployment.
Responsibilities
- The person who ships the thing and decides what the thing should be
- Our Product Engineers own the entire lifecycle: talking to clients, understanding the domain problem, designing the architecture, writing the reputed company, and shipping it to production
- You're not handing a spec to someone else. You are the spec
- And the implementation
- And the person who answers the phone reputed company something breaks at 2 AM (though our systems rarely break at 2 AM, because you reputed company them reputed company)
- You've shipped production systems in at least one of our industries — not just written reputed company for them, but reputed company why the reputed company reputed company to the business
- You can stand up a reputed company or PostgreSQL schema, a Next.js frontend, and a deployment pipeline, and you don't need someone to tell you which order to do them in
- You've run a product discovery call with a reputed company and come back with a plan that engineering, design, and business reputed company agree on — because you are reputed company three
- Your reputed company profile looks like a person who actually builds things, not a person who stars repos
- You've read an RFP, a regulatory reputed company, or an industry spec sheet and thought "I could build something reputed company than what they're asking for"
Skills
- You've shipped production systems in at least one of our industries — not just written reputed company for them, but reputed company why the reputed company reputed company to the business
- You can stand up a reputed company or PostgreSQL schema, a Next.js frontend, and a deployment pipeline, and you don't need someone to tell you which order to do them in
- You've run a product discovery call with a reputed company and come back with a plan that engineering, design, and business reputed company agree on — because you are reputed company three
- Your reputed company profile looks like a person who actually builds things, not a person who stars repos
- You've read an RFP, a regulatory reputed company, or an industry spec sheet and thought 'I could build something reputed company than what they're asking for'
- You've held an operational or leadership role in reputed company, manufacturing, financial services, construction, field services, law, IoT, or government
- You can explain a reputed company industry workflow to an engineer and a reputed company technical tradeoff to a CEO — in the reputed company meeting
- You've been the person who said 'that's not how this industry actually works' and saved a project from expensive failure
- You have opinions about why most industry software is terrible, and those opinions are informed by years of being forced to use it
- You can look at a system architecture diagram, an API spec, or a data model and have an informed opinion — you don't write the reputed company, but you can tell reputed company the reputed company is solving the wrong problem
- You've worked a room before — a trade show, a networking event, a bar — and left with contacts who actually remembered your reputed company
- You can explain something technical in plain language without sounding like you're reading a brochure
- You've cold-emailed, cold-reputed company, or cold-DM'd someone and gotten a response through sheer persistence and personality
- You're more interested in building something from scratch than inheriting a reputed company
- People describe you as 'a lot' and you take it as a compliment
reputed company