Software Engineer - Pirate & Architect

ppWe’re not looking for a software engineer who works through tickets. We’re looking for someone who can identify, board, and take over a merchant vessel in record time, and who leaves behind a ship where every knot is flawless. AI now handles much of the design, prototyping, and coding. What matters is building fast without leaving chaos behind. Concretely: /p ul liDesign thinking — you understand the actual problem before writing a single line of code /li liRapid prototyping with AI — you don’t treat modern AI tools as a novelty but as a core part of your workflow, going from idea to working prototype in hours instead of weeks /li liAgentic coding with a firm hand — you let agents code for you, but you keep them on a short leash: strict architecture guidelines, clean design patterns, no sprawl /li liSpeed with foresight — you build fast, but you’re already thinking two releases ahead. Every important design decision is documented and traceable, even when you built at sprint speed /li /ul h3As an Architect /h3 pOnce the vessel is taken, you take command. Now structure matters more than speed. /p ul liSoftware feature blueprinting — the plan exists before the building starts /li liSystems engineering — you think in systems, not isolated components /li liSoftware engineering design patterns — core toolkit, not bonus knowledge /li liArchitecture design — you make and own the big decisions, and you know when a microservice earns its keep and when it's just overhead /li liCloud-native product architecture — you design products for the cloud, not applications that happen to run there /li liCode reviews — held to a high standard, but constructive /li liExtreme attention to structure — loose ends are not a minor offense to you /li liBroad foundation across databases, data structures, storage, cloud functions, and infrastructure as code — you choose deliberately, not out of habit /li /ul h3As a Pirate /h3 pWe’re not looking for a software engineer who works through tickets. We’re looking for someone who can identify, board, and take over a merchant vessel in record time, and who leaves behind a ship where every knot is flawless. AI now handles much of the design, prototyping, and coding. What matters is building fast without leaving chaos behind. Concretely: /p ul liDesign thinking — you understand the actual problem before writing a single line of code /li liRapid prototyping with AI — you don’t treat modern AI tools as a novelty but as a core part of your workflow, going from idea to working prototype in hours instead of weeks /li liAgentic coding with a firm hand — you let agents code for you, but you keep them on a short leash: strict architecture guidelines, clean design patterns, no sprawl /li liSpeed with foresight — you build fast, but you’re already thinking two releases ahead. Every important design decision is documented and traceable, even when you built at sprint speed /li /ul h3As an Architect /h3 pOnce the vessel is taken, you take command. Now structure matters more than speed. /p ul liSoftware feature blueprinting — the plan exists before the building starts /li liSystems engineering — you think in systems, not isolated components /li liSoftware engineering design patterns — core toolkit, not bonus knowledge /li liArchitecture design — you make and own the big decisions, and you know when a microservice earns its keep and when it's just overhead /li liCloud-native product architecture — you design products for the cloud, not applications that happen to run there /li liCode reviews — held to a high standard, but constructive /li liExtreme attention to structure — loose ends are not a minor offense to you /li liBroad foundation across databases, data structures, storage, cloud functions, and infrastructure as code — you choose deliberately, not out of habit /li /ul h3Tasks /h3 pThe work itself, concretely: /p ul liBuilding and maintaining AI agentic workflows — on industry-standard frameworks, with the same architectural discipline you would apply to any other production system /li liBuilding and maintaining data processing pipelines — ingestion, transformation and enrichment of customer data: reliable, observable, and safe to reprocess /li liShipping features end to end — the bReact /b screen, the bPython /b service behind it, and the bAWS /b infrastructure it runs on /li liMaking quality measurable — evaluation sets, tracing, and budgets for latency and cost, so a regression is caught by us and not by a customer /li liIntegrating with our customers’ systems — real business data from real enterprise landscapes, rarely clean and never twice the same /li /ul h3Requirements /h3 ul liMultiple years of experience as a software engineer, ideally with ownership of architecture decisions /li liPractical, current experience with AI-assisted development (not just “tried it once”) /li liUnderstanding of cloud native architecture, ideally on AWS /liliEnd-to-end reach — ideally you are at home in the frontend, the backend and the infrastructure, and can take a feature all the way to production without handing it over at every boundary /li liThe rare combination: high speed AND high structural discipline /li liStrong communication skills to explain and defend architecture decisions — including to agents that “wanted to solve it differently” /li /ul h3Benefits /h3 pShape and own the technical architecture as the company scales /p pWork within a modern, AI-driven engineering setup /p pHigh level of autonomy and real impact from day one /p pDynamic, entrepreneurial environment with room to grow /p pbNo cover letter needed. Just show us you can board and clean up. /b /p /p #J-18808-Ljbffr