Senior Product Engineer

Senior Product Engineer - Detalhes da Vaga. ● Part Product Engineer on the core platform, part Forward Deployed Engineer working with ops, support, finance or marketing. ● This is a senior, hands-on full-stack role. ● We use AI to build products faster. ● AI product development is not the focus of the job, although some features may use LLMs when there is a good reason. ● Fully remote, EU or LATAM, with at least four hours of overlap with the team''s EU working day. ● About Us BÆRSkin Tactical Supply Co. ● combines rugged performance with everyday functionality to make the very best outdoor gear. ● We design apparel that reflects timeless values, resilience and practicality, so anyone can stay prepared and unstoppable, on the trail, in the city or wherever life takes them. ● More than a brand, BÆRSkin is a mindset. ● Our remote-first team spans borders but shares a single focus: building durable, dependable products. ● Our motto is "Built for the Brave". ● We are small and we punch well above our weight technically. ● The tech org is 10 people across software and data. ● Engineering has had zero turnover in four years. ● We have been shipping AI-written code to production since 2023. ● The Role This is an individual contributor role. ● Nobody reports to you and nobody will scope your work for you. ● You define the work and you build it. ● Engineering peers review your code and help when you ask. ● You own delivery for an agreed business problem. ● You agree the priority with the CTO and the business owner, then the scope and implementation decisions are yours. ● If a decision materially changes cost or risk, you take it back to the owner before you commit. ● If two teams want different things, the CTO settles it. ● You will often be the only technical person in the room. ● That is the point of the role. ● We are moving towards engineers owning areas of the business rather than running a service desk. ● We are not fully there yet. ● This role is the sharp end of getting us there. ● Reporting line: Direct to the CTO. ● Initial focus: One specific business problem, delivered in partnership with another business area. ● The title means little. ● We picked "Product Engineer" because it is the closest label for the work. ● If your CV says Full-Stack Engineer, Technical Product Manager, Solutions Engineer, Forward Deployed Engineer or founder, and you build things and get them over the line, apply. ● We hire builders and go-getters. ● We do not hire titles. ● The production engineering requirements below still apply. ● What Will You Do? Own problems, not tickets. ● Work directly with another business area to understand a specific problem. ● Use stakeholder input and data to define clear requirements and agree the outcome before you build. ● Make the trade-offs. ● Decide what to build, reuse or change in the process. ● Explain what you are giving up, cut unnecessary features and escalate only the decisions outside your remit. ● Use a bounded prototype when it answers a discovery question faster than a debate. ● Ship end-to-end. ● Build full-stack across database, backend and UI, from customer-facing features to internal tools and automation. ● Test and roll out safely, with monitoring and a recovery path appropriate to the risk. ● Protect access and customer data. ● Stay until it sticks. ● Follow through on adoption with the people using the result. ● Document the system and agree ongoing ownership so another engineer can support it. ● Measure it. ● Define success and a baseline before building. ● Measure the result and report it honestly, including when impact is below expectations. ● Ship with AI. ● Use AI tools daily and validate what they produce. ● You drive the tools, you read what they give you and you fix it before it ships. ● Keep secrets and customer data out of unapproved tools. ● When a feature uses an LLM, you handle its failure modes. ● Our Stack TypeScript, Next. ●Js, Vercel, PostgreSQL, Drizzle ORM, Bun, Kubernetes, GCP, AWS, PostHog, GitHub Actions, Linear and Notion. ● Our AI tooling includes Claude and Codex . ● You do not need to know every tool. ● Strong engineering fundamentals and the ability to learn matter more than matching the entire list. ● Skills & Qualifications At least five years building software products, including both defining what to build and building it. ● Essential Requirements from scratch. ● You can turn a vague business request into something buildable without waiting for a finished PRD. ● Scope judgement. ● You can explain what you cut, delayed or rejected, using the information available at the time. ● Production full-stack capability. ● You can build and operate a complete system, including relevant tests and failure handling. ● Modern TypeScript and a React framework in production. ● Next. ●Js is preferred. ● Relational databases. ● You can model a schema and write queries beyond basic CRUD. ● Stakeholder collaboration and commercial judgement. ● You can work directly with non-technical teams, explain trade-offs and connect technical choices to business outcomes. ● A working AI-assisted development practice. ● Walk us through a recent example, including what you had to check or fix. ● English at B2/C1 minimum, with the ability to lead stakeholder discussions and write clear technical notes. ● Four hours of overlap with the team''s EU working day. ● Desirable DTC, retail, e-commerce, gaming or subscription-commerce experience, particularly checkout, fulfilment or customer support tooling. ● Embedded delivery, solutions engineering or founder experience where you wore many hats. ● Composable / MACH architecture, or Kubernetes, GCP or AWS in production. ● Open source contributions or public technical writing. ● Portuguese, because most of the team is currently based in Brazil. ● How You Work Hands-on. ● You build things yourself. ● You can point to what you personally shipped in the last 90 days. ● Pragmatic. ● You know when good enough is good enough, and you can defend the corner you cut. ● Self-directed. ● "Here is the problem, figure it out" sounds good to you. ● Decisive. ● You make the scope call and own it, rather than escalating every trade-off. ● Commercially aware. ● You understand the product exists to serve the business. ● Direct. ● We say what we mean. ● No politics, no passive aggression. ● Coachable. ● You take feedback and something actually changes. ● How We Work Remote-first and async-first, with agreed overlap for collaboration. ● We measure outcomes, not hours. ● We keep process light. ● Decisions sit close to the work and the best-supported argument wins. ● Independence comes with peer review and access to help. ● Ask for it before a small problem becomes an expensive one. ● Feedback is direct. ● We expect people to explain their decisions and change their minds when the evidence changes. ● When things break, we run blameless post-mortems and fix the underlying problem. ● This Role Won''t Suit You If You need a PM, a designer and three meetings before you can start. ● You want to write the PRD and hand implementation to someone else. ● You want to be handed the PRD and just build it. ● You want a narrowly defined frontend-only or backend-only role. ● You struggle to tell a stakeholder no. ● Your experience is mostly large enterprise with big teams and narrow scope. ● AI is something you talk about but have not shipped with. ● You let Claude drive you. ● We want people who drive Claude. ● You use your brain to work smart. ● You do not dump a problem on AI and wait for something magical to happen. ● You rely on AI output you cannot explain, test or change yourself. ● Heavy process and ceremonies are core to how you work. ● What''s In It For You? Fully remote Competitive salary with regular performance reviews 26 days paid leave Parental leave Training budget Genuinely strong colleagues, and no layers between you and the decisions A product you can change. ● If something is wrong, you fix it What''s Next? Apply here with a CV. ● A cover letter is optional. ● If you write one, tell us about something you took from a vague ask to production, what you cut, and why. ● FAQ How long is the contract? Full-time permanent with a 6-month trial period. ● We are looking for long-term team members, not short-term contractors. ● What is the interview process? Screening call, 15-30 minutes. ● Location, overlap, availability and English. ● Product interview, 60 minutes. ● Technical interview, 60 minutes. ● Panel Interview, 90 minutes. ● . Requisitos para participar do processo. ● . O que oferecemos.