Postgresql Jobs
72 jobs found
2 days ago
Here is the job description converted to clean, well-structured markdown format. --- ## Binance Accelerator Program - Product DA **Location:** Asia / Hong Kong / Taiwan, Taipei **Department:** Product & Design – Product **Program:** Binance Accelerator Program **Workplace Type:** Remote --- ### About Binance Binance is a leading global blockchain ecosystem behind the world’s largest cryptocurrency exchange by trading volume and registered users. We are trusted by 300+ million people in 100+ countries for our industry-leading security, user fund transparency, trading engine speed, deep liquidity, and an unmatched portfolio of digital-asset products. Binance offerings range from trading and finance to education, research, payments, institutional services, Web3 features, and more. We leverage the power of digital assets and blockchain to build an inclusive financial ecosystem to advance the freedom of money and improve financial access for people around the world. ### About Binance Accelerator Program The Binance Accelerator Program is a concise fixed-term program designed for Early Career Talent to have an immersive experience in the rapidly expanding Web3 space. You will be given the opportunity to experience life at Binance and understand what goes on behind the scenes of the world’s leading blockchain ecosystem. Alongside your job, there will also be a focus on networking and development, which will expand your professional network and build transferable skills to propel you forward in your career. Learn about BAP Program [HERE](#). ### Who May Apply - Current university students and recent graduates. --- ### Responsibilities - Manage follow-up communications with all stakeholders to ensure proposed actions and data-driven solutions are effectively implemented. - Monitor detailed reports and systematic tracking systems to track project and product progress for better transparency and productivity. - Evaluate product performance data by tracking core metrics including user growth, conversion, retention, and funnel health. Collaborate with internal stakeholders to address performance gaps and drive continuous improvement. - Support AB Test full-cycle execution: sample sizing, significance test, outlier processing, metric tracking, and result analysis. - Assist in developing and optimizing automation processes to improve operational efficiency, while ensuring compliance with security, privacy, and regulatory standards. - Use SQL to conduct data extraction, analysis, and modeling; build and maintain DWA intermediate tables and complex aggregation logic. - Translate business issues into measurable indicators, deliver clear analysis reports, and support data-driven decision making. ### Requirements - Currently pursuing a bachelor’s or master’s degree in a local university. - Data-centric mindset with the ability to analyze large-scale data and derive actionable insights. - Demonstrated understanding of and strong interest in the cryptocurrency / Web3 / fintech industry. - Strong proficiency in SQL preferred; able to write complex queries and perform data modeling. - Understanding of data warehouse layers (DWD / DWA / DWS) and AB Test fundamentals is a strong plus. - Strong communication skills, enabling effective engagement and follow-up with internal stakeholders. - Persistent, proactive, and keen attention to detail. - Adaptable, open-minded, and comfortable working in a fast-paced and remote working environment. - Hands-on, self-driven, and able to deliver structured analysis and clear presentations. --- ### Why Binance - Shape the future with the world’s leading blockchain ecosystem. - Collaborate with world-class talent in a user-centric global organization with a flat structure. - Tackle unique, fast-paced projects with autonomy in an innovative environment. - Thrive in a results-driven workplace with opportunities for career growth and continuous learning. - Competitive salary and company benefits. - Work-from-home arrangement (the arrangement may vary depending on the work nature of the business team). Binance is committed to being an equal opportunity employer. We believe that having a diverse workforce is fundamental to our success. *By submitting a job application, you confirm that you have read and agree to our [Candidate Privacy Notice](#).* --- **AI Disclaimer:** We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us. --- *When applying, mention the word **CANDYSHOP** to show you read the job post completely.*
LawnStarter
2 days ago
This is a remote role for candidates located in Porto Alegre, Brazil. About LawnStarter LawnStarter is the nation's leading on-demand marketplace for lawn care and outdoor services, with over $100M in annual bookings. We're expanding beyond lawn care to become the one-stop shop for all home services — operating across three brands (LawnStarter, Lawn Love, Home Gnome) on a single shared platform. About Engineering at LawnStarter We're restructuring engineering around initiative teams: a Product Engineer paired with a PM and a designer, with an Engineering Manager who covers a couple of initiatives and supports your growth. The engineer leads AI agents like a team, ships the work, and is accountable — with the rest of the triangle — for whether the initiative moves its metric. We're betting that 1–2 strong engineers running AI agents can outship the labor-team model that defined the last decade of software. That bet only works if the engineers we hire are wired for ownership and can ship to a marketplace with real customers and pros on both sides. The Role You're the engineering anchor of one initiative at a time. The initiative is a team effort — an iron triangle of you, your PM, and your designer — and you have key participation across the full lifecycle: shaping the problem, deciding the technical approach, leading the AI agents that implement most of the code, shipping to production, and answering for the outcome alongside the rest of the triangle. You're accountable for the outcome — not for the volume of code merged. If an agent can ship it safely, your job is to make sure the agent does it right and the metric moves. If the initiative needs hand-written code in a sensitive area, you write it yourself. What makes this role different: You lead AI agents, not humans. Claude Code, Cursor, Codex, and our internal agent stack are your team. You own the quality, safety, and velocity of what they produce. You own an outcome, not a ticket queue. Problem-framing through production through the metric review 2–4 weeks after launch. You partner horizontally with PM and design. No tech lead above you. No architect approval. No ticket grooming committee. The bar is staff, not senior. You make the call when the call needs to be made. If you're waiting to be told, this isn't the role. What You'll Own The technical approach — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make the call, document it, and revisit it if the data says you were wrong. Agent-led implementation quality — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code on your initiative. Most lines will be agent-authored. You're accountable for them. Cross-functional partnership — daily working contact with your PM (scope, tradeoffs) and your designer (UX decisions, in-tool prototyping with agents), and weekly check-ins with your EM (initiative health, blockers, growth). The initiative outcome — the specific metric the initiative was set up to move. In partnership with your PM, you present results 2–4 weeks post-launch and share the "did it work" answer. A high bar for what ships under your name — production correctness, security posture, performance, observability, and the experience for customers and pros. Agents accelerate you; they don't lower the bar. Problems to Solve Leading AI agents at staff-level qualityMost of the code on your initiative will be authored by AI agents. The work is making agents ship as if a senior engineer wrote it: prompts that encode our codebase conventions, evals that catch hallucinations before merge, tests that exercise the edges, observability that catches the regression in production before a customer reports it. How do you build the agent workflow that lets one engineer ship what used to take a team? Owning an outcome without a tech leadYou don't have a tech lead to approve your design or an architect to escalate to. You have an EM who covers a couple of initiatives and peers on adjacent ones. How do you make calls fast, document them clearly, and stay accountable to the outcome — without slowing down for hierarchy that no longer exists? Shipping outcomes, not featuresThe initiative will be measured by a metric — a conversion rate, a retention curve, a pro-funnel KPI, a unit economics shift. You're accountable for the number, not the feature. How do you scope to actually move it, decide what to not build, and have the discipline to follow up 2–4 weeks after launch even when the next initiative is calling? What Success Looks Like (Year 1) Initiative outcomes hit — You've shipped 3–4 initiatives end-to-end, and at least two clearly moved the metric they were set up to move (with the post-launch review to prove it). Agent workflow that travels — The prompts, evals, and review loop you built for your initiative are adopted by at least one other engineer on an adjacent initiative. Cycle time — Median time from problem-framing to first production rollout on your initiatives is meaningfully shorter than the pre-restructure baseline. Zero "agent-shipped that" incidents — No customer- or pro-facing regression traceable to agent-authored code that you missed in review. Visible leverage — Other engineers point to artifacts you left behind — runbooks, evals, agent workflows, post-launch write-ups — as references they use. Who You Are AI-native. Claude Code, Cursor, Codex, or equivalent are how you ship — daily, on production work. You have opinions about prompts, evals, agent loops, MCP servers, and review workflows, and you know when to let the agent run vs. write it yourself. This is unlikely to be a good fit if you describe AI coding as "something you're exploring" or prefer to write everything by hand. Already operating at lead level. You may currently be titled Senior, Staff, Lead, or Principal — but in practice you've been the person making the call, shipping the hard thing, and answering for whether it worked. This is unlikely to be a good fit if you've always had a tech lead breaking down the work for you. Outcome-driven, not output-driven. You measure your week in "did the metric move" and "did the experience get better," not in tickets closed. You read the post-launch dashboard and you own the answer. This is unlikely to be a good fit if you take pride in volume of code shipped or feel uncomfortable being measured on a number you don't fully control. A strong horizontal partner. You hold your own with a strong PM and a strong designer. You bring engineering judgment to product calls and product judgment to engineering calls. This is unlikely to be a good fit if you hide behind "that's product's decision" or default to RICE-scoring tickets handed down to you. Decisive and documented. Architecture decisions, data-model choices, rollout plans — you write them down, get fast input, and move. This is unlikely to be a good fit if you wait for consensus on questions that have a clear right answer, or if you make calls and never write them down. Raises the floor, not just the ceiling. Your impact compounds beyond your own initiative because you leave artifacts — agent workflows, evals, runbooks, post-launch reviews. This is unlikely to be a good fit if you're a lone wolf who ships brilliantly but leaves nothing reusable behind. Cares about customers and pros. This is a real-world marketplace with real people on both sides. This is unlikely to be a good fit if you're chasing pure engineering elegance over business and customer outcomes. This Role Is NOT A tech lead in an old-style team. No 4–5 engineers reporting up to you on technical direction. The team is you + PM + designer + EM, with AI agents doing most of the implementation. A management role today. People management is the EM's job in this role. That said, the path can grow into management for those who want it — it's an open door, not a closed one. A platform-only or architecture-only role. You're a Product Engineer. You ship features that move metrics, end-to-end. Platform work happens inside the initiative when it's needed for the outcome. A "let AI do everything" role. Agents handle implementation grunt work. You handle judgment, design, safety, and accountability. The bar is higher than the old senior bar, not lower. A research role. This is shipping to a marketplace with $100M+ in bookings. Customers and pros are using what you ship inside the same week. Tech You'll Touch AI agents — Claude Code, Cursor, Codex, internal agent stack, MCP servers, evals tooling Backend — PHP/Laravel Frontend — TypeScript/React/React Native (customer & pro apps, web and mobile) Data — Redshift, dbt, Segment, Airflow Infra — AWS, Datadog, Sentry, GitHub Actions Documentation & process — Brain (Claude Code skills + docs repo), Confluence, Jira You don't need every box checked. You need deep skill in at least one of our stacks plus credible production experience with AI coding agents. Benefits Competitive salary of USD $80,000–$100,000 annual base Work from anywhere High ownership and autonomy Fast-moving team that loves to build, learn, and grow
Confirmo
3 days ago
## **Data Engineer at Confirmo** **Confirmo** is a global stablecoin-first payment platform trusted by market leaders. Originally founded in Prague in 2014, we now run one of the most established infrastructures in the industry. We're a 60-person global team, and we're looking for a **Data Engineer** to help shape the foundation of how we work with data — you'd be joining as our second hire in this space, with plenty of room to make your mark. ### **Key Responsibilities** You're going to make sure people at Confirmo can make data-driven decisions. We don't expect you to be creating reports or running data analyses yourself — we expect you to enable pretty much everyone else to do so. As Confirmo's second data engineer, you'll achieve this by: - Understanding Confirmo's business model, deeply mastering our data model, and then significantly shaping it so it stays maintainable and representative. - Building trustworthy and robust data pipelines that deliver information from various internal and 3rd-party sources (our transactional systems, banks, PSPs, exchanges, blockchain(s), etc.). - Proposing tooling that's suitable, affordable, and adoptable for a scaleup of Confirmo's size and needs. - Our current workhorses are **PostgreSQL**, **Airflow**, **Python**, and **AWS** — but we're open to extending the stack with anything else that makes sense. ### **Your Profile** - A data engineering background and a taste for exploring and quickly adopting new technologies and approaches. - Demonstrated experience with both traditional (OLTP, OLAP) and horizontally scalable warehousing approaches (Data Lake, Data Mesh, built on **BigQuery**, **Spark**, **Snowflake**, or anything similar). You may have been a follower so far, adopting techniques at your previous company — but at Confirmo, we expect you to speak up, and possibly even lead the way, on this front. - Professional software engineering experience. **Python** is ideal, but any other major language used in data processing is almost as relevant. - Real, non-tutorial knowledge of data modelling and data warehousing principles. - Data infrastructure engineering experience, or the willingness to quickly pick it up. We don't have many dedicated infrastructure engineers, so we expect everyone — and definitely the data engineer — to become proficient in **Terraform** and other IaC-based infrastructure management techniques. - An interest in fintech and/or crypto technologies is a plus. ### **Location & Application** **Location:** Our office is in Prague, but the role can be remote across the Czech Republic or Slovakia. If you're interested in learning more, please submit your CV and our recruiter will get back to you promptly. When applying, mention the word **CANDYSHOP** to show you read the job post completely.
LawnStarter
3 days ago
This is a remote role for candidates located in Campinas, Brazil. About LawnStarter LawnStarter is the nation's leading on-demand marketplace for lawn care and outdoor services, with over $100M in annual bookings. We're expanding beyond lawn care to become the one-stop shop for all home services — operating across three brands (LawnStarter, Lawn Love, Home Gnome) on a single shared platform. About Engineering at LawnStarter We're restructuring engineering around initiative teams: a Product Engineer paired with a PM and a designer, with an Engineering Manager who covers a couple of initiatives and supports your growth. The engineer leads AI agents like a team, ships the work, and is accountable — with the rest of the triangle — for whether the initiative moves its metric. We're betting that 1–2 strong engineers running AI agents can outship the labor-team model that defined the last decade of software. That bet only works if the engineers we hire are wired for ownership and can ship to a marketplace with real customers and pros on both sides. The Role You're the engineering anchor of one initiative at a time. The initiative is a team effort — an iron triangle of you, your PM, and your designer — and you have key participation across the full lifecycle: shaping the problem, deciding the technical approach, leading the AI agents that implement most of the code, shipping to production, and answering for the outcome alongside the rest of the triangle. You're accountable for the outcome — not for the volume of code merged. If an agent can ship it safely, your job is to make sure the agent does it right and the metric moves. If the initiative needs hand-written code in a sensitive area, you write it yourself. What makes this role different: You lead AI agents, not humans. Claude Code, Cursor, Codex, and our internal agent stack are your team. You own the quality, safety, and velocity of what they produce. You own an outcome, not a ticket queue. Problem-framing through production through the metric review 2–4 weeks after launch. You partner horizontally with PM and design. No tech lead above you. No architect approval. No ticket grooming committee. The bar is staff, not senior. You make the call when the call needs to be made. If you're waiting to be told, this isn't the role. What You'll Own The technical approach — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make the call, document it, and revisit it if the data says you were wrong. Agent-led implementation quality — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code on your initiative. Most lines will be agent-authored. You're accountable for them. Cross-functional partnership — daily working contact with your PM (scope, tradeoffs) and your designer (UX decisions, in-tool prototyping with agents), and weekly check-ins with your EM (initiative health, blockers, growth). The initiative outcome — the specific metric the initiative was set up to move. In partnership with your PM, you present results 2–4 weeks post-launch and share the "did it work" answer. A high bar for what ships under your name — production correctness, security posture, performance, observability, and the experience for customers and pros. Agents accelerate you; they don't lower the bar. Problems to Solve Leading AI agents at staff-level qualityMost of the code on your initiative will be authored by AI agents. The work is making agents ship as if a senior engineer wrote it: prompts that encode our codebase conventions, evals that catch hallucinations before merge, tests that exercise the edges, observability that catches the regression in production before a customer reports it. How do you build the agent workflow that lets one engineer ship what used to take a team? Owning an outcome without a tech leadYou don't have a tech lead to approve your design or an architect to escalate to. You have an EM who covers a couple of initiatives and peers on adjacent ones. How do you make calls fast, document them clearly, and stay accountable to the outcome — without slowing down for hierarchy that no longer exists? Shipping outcomes, not featuresThe initiative will be measured by a metric — a conversion rate, a retention curve, a pro-funnel KPI, a unit economics shift. You're accountable for the number, not the feature. How do you scope to actually move it, decide what to not build, and have the discipline to follow up 2–4 weeks after launch even when the next initiative is calling? What Success Looks Like (Year 1) Initiative outcomes hit — You've shipped 3–4 initiatives end-to-end, and at least two clearly moved the metric they were set up to move (with the post-launch review to prove it). Agent workflow that travels — The prompts, evals, and review loop you built for your initiative are adopted by at least one other engineer on an adjacent initiative. Cycle time — Median time from problem-framing to first production rollout on your initiatives is meaningfully shorter than the pre-restructure baseline. Zero "agent-shipped that" incidents — No customer- or pro-facing regression traceable to agent-authored code that you missed in review. Visible leverage — Other engineers point to artifacts you left behind — runbooks, evals, agent workflows, post-launch write-ups — as references they use. Who You Are AI-native. Claude Code, Cursor, Codex, or equivalent are how you ship — daily, on production work. You have opinions about prompts, evals, agent loops, MCP servers, and review workflows, and you know when to let the agent run vs. write it yourself. This is unlikely to be a good fit if you describe AI coding as "something you're exploring" or prefer to write everything by hand. Already operating at lead level. You may currently be titled Senior, Staff, Lead, or Principal — but in practice you've been the person making the call, shipping the hard thing, and answering for whether it worked. This is unlikely to be a good fit if you've always had a tech lead breaking down the work for you. Outcome-driven, not output-driven. You measure your week in "did the metric move" and "did the experience get better," not in tickets closed. You read the post-launch dashboard and you own the answer. This is unlikely to be a good fit if you take pride in volume of code shipped or feel uncomfortable being measured on a number you don't fully control. A strong horizontal partner. You hold your own with a strong PM and a strong designer. You bring engineering judgment to product calls and product judgment to engineering calls. This is unlikely to be a good fit if you hide behind "that's product's decision" or default to RICE-scoring tickets handed down to you. Decisive and documented. Architecture decisions, data-model choices, rollout plans — you write them down, get fast input, and move. This is unlikely to be a good fit if you wait for consensus on questions that have a clear right answer, or if you make calls and never write them down. Raises the floor, not just the ceiling. Your impact compounds beyond your own initiative because you leave artifacts — agent workflows, evals, runbooks, post-launch reviews. This is unlikely to be a good fit if you're a lone wolf who ships brilliantly but leaves nothing reusable behind. Cares about customers and pros. This is a real-world marketplace with real people on both sides. This is unlikely to be a good fit if you're chasing pure engineering elegance over business and customer outcomes. This Role Is NOT A tech lead in an old-style team. No 4–5 engineers reporting up to you on technical direction. The team is you + PM + designer + EM, with AI agents doing most of the implementation. A management role today. People management is the EM's job in this role. That said, the path can grow into management for those who want it — it's an open door, not a closed one. A platform-only or architecture-only role. You're a Product Engineer. You ship features that move metrics, end-to-end. Platform work happens inside the initiative when it's needed for the outcome. A "let AI do everything" role. Agents handle implementation grunt work. You handle judgment, design, safety, and accountability. The bar is higher than the old senior bar, not lower. A research role. This is shipping to a marketplace with $100M+ in bookings. Customers and pros are using what you ship inside the same week. Tech You'll Touch AI agents — Claude Code, Cursor, Codex, internal agent stack, MCP servers, evals tooling Backend — PHP/Laravel Frontend — TypeScript/React/React Native (customer & pro apps, web and mobile) Data — Redshift, dbt, Segment, Airflow Infra — AWS, Datadog, Sentry, GitHub Actions Documentation & process — Brain (Claude Code skills + docs repo), Confluence, Jira You don't need every box checked. You need deep skill in at least one of our stacks plus credible production experience with AI coding agents. Benefits Competitive salary of USD $80,000–$100,000 annual base Work from anywhere High ownership and autonomy Fast-moving team that loves to build, learn, and grow
Chainalysis
4 days ago
## Staff Backend Engineer → Engineering Team Lead (Alterya Team) The engineering team at **Chainalysis** is inspired by solving the hardest technical challenges and creating products that build trust in cryptocurrencies. We’re a global organization with teams in Denmark, UK, Canada, and the USA who thrive on challenging work and collaborating with exceptionally talented teammates. Our industry changes every day, and our mission is to create user-facing products supported by a flexible and scalable data platform, allowing us to adapt to rapid changes and bring immense value to our customers. We are looking for a **Staff-level Backend Engineer** who is ready to transition into an **Engineering Team Lead** role within 3–6 months for our **Alterya team**. This team operates as an innovation hub in Tel Aviv at the intersection of AI, fraud prevention, and large-scale data intelligence, where you will eventually be responsible for the growth, delivery, and technical excellence for one of its core squads. As an **Engineering Team Lead**, you will be a pivotal leader in our mission. You will lead a high-performing team of engineers building and scaling the APIs and data layers that global institutions rely on to stop crime, manage risk, and fight fraud. ### In this job, you’ll: - **Lead & Mentor:** Drive a team of experienced software engineers, providing technical guidance, career coaching, and fostering a culture of high performance and continuous learning. - **Build & Scale Data Pipelines:** Own the architecture of our ETLs and data layers. You’ll be responsible for making systems run 100x faster and handling massive data volumes with precision. - **Lead Technical Excellence:** Once in the Lead role, you will mentor a team of senior engineers, driving code quality, performance-critical flows, and architectural standards. - **Drive the Roadmap:** Partner with Product Managers to translate complex fraud-prevention requirements into robust, production-grade technical solutions. - **Optimize Everything:** From PostgreSQL queries to Kubernetes-based deployments, you will look for ways to overhaul scalability and efficiency across the stack. ### We’re looking for candidates who have: - **Deep Python Expertise:** You are a Python expert who understands the nuances of the language, and knows your way around FastAPI and serving requests at scale. - **The Data Mindset:** You have a proven track record of building and optimizing Data Pipelines, ETLs, and Big Data systems. You know how to handle data at scale. - **AI-First Engineering Mindset:** You are an "AI-First" developer who leverages AI tools to accelerate development. You understand how to support, build, and deploy tooling that employs AI (LLMs, agents, etc.) throughout the organization and tech stack. - **Seniority with Ambition:** 6+ years of backend experience. You’ve likely led projects or mentored teams and are ready to officially step into a Team Lead role. - **Database Mastery:** Strong familiarity with PostgreSQL (performance tuning is a plus), Redis, and BigQuery. - **Solid Communicator:** You are a great communicator — highly effective at coordinating with leaders and fellow leads to solve complex problems across teams. - **Startup DNA:** You prefer a "get it done" environment. You want to feel the impact of your work and thrive in a high-growth, technical culture. - **High Standards:** You take pride in clean, scalable, and testable code. ### You might also have: - Experience in Fintech, Cyber-security, or Fraud detection domains. - Deep experience with GCP (Google Cloud Platform) and Kubernetes (GKE). ### Technologies we use: - **Primary:** Python, PostgreSQL, Redis, BigQuery. - **Infra:** Google Cloud (GCP), Kubernetes (GKE), ArgoCD. ### About Chainalysis Blockchain technology is powering a growing wave of innovation. Businesses and governments around the world are using blockchains to make banking more efficient, connect with their customers, and investigate criminal cases. As adoption of blockchain technology grows, more and more organizations seek access to all this ecosystem has to offer. That’s where Chainalysis comes in. We provide complete knowledge of what’s happening on blockchains through our data, services, and solutions. With Chainalysis, organizations can navigate blockchains safely and with confidence. ### You belong here. At Chainalysis, we believe that diversity of experience and thought makes us stronger. With both customers and employees around the world, we are committed to ensuring our team reflects the unique communities around us. We’re ensuring we keep learning by committing to continually revisit and reevaluate our diversity culture. We encourage applicants across any race, ethnicity, gender/gender expression, age, spirituality, ability, experience and more. If you need any accommodations to make our interview process more accessible to you due to a disability, don't hesitate to let us know. You can learn more here. We can’t wait to meet you. When applying, mention the word **CANDYSHOP** to show you read the job post completely.
Impossible Cloud
8 days ago
# Go to Market Engineer **Location:** Hamburg **Department:** Other **Commitment:** Full-time **Workplace Type:** On-site --- ## About Us **Impossible Cloud** is a fast-growing B2B cloud company headquartered in Hamburg, Germany. We have built a cloud object storage solution comparable to AWS S3, purpose-built and optimised for AI and compute workloads. Our commercial hyper-growth speaks for itself, powered by our channel-first go-to-market strategy. We are now expanding beyond storage: we are building a high-performance compute platform, offering an end-to-end solution from GPU infrastructure to full GPU platform software stack. In doing so, we are redefining the cloud ecosystem by bridging the gap between decentralised infrastructure (DePIN), mainstream B2B cloud use cases, and AI applications. Find out more about us here. > **Please note that we can only consider candidates who have a valid, unrestricted work permit for the EU.** --- ## Your Impact Impossible Cloud's go-to-market motion is built on automation, data, and speed. As our **Go to Market Engineer**, you own the technical infrastructure that makes it run: from the billing systems that convert free trials into paying customers, to the automation flows that connect our product, CRM, and payment stack. In this role you will actively own and develop new GTM motions. You identify and build demand generation strategies from scratch, run structured experiments across inbound, outbound, SEO, GEO, and emerging channels, and stay ahead of the tools and methodologies that will drive pipeline before the rest of the market catches up. --- ## What You Will Do - Own the self-serve revenue engine end-to-end, including the n8n → HubSpot → Stripe pipeline. You manage trial-to-paid conversion, dunning flows, payment retries, and overall billing reliability with clear ownership of revenue impact. - Build, maintain, and troubleshoot the broader GTM automation stack across n8n workflows, HubSpot routing, Webflow, lead capture, and partner infrastructure, ensuring leads are properly captured, attributed, and routed. - Improve the self-serve funnel by identifying conversion drop-offs, implementing fixes, and measuring results using Supabase, SQL, and event data. - Proactively identify gaps and edge cases across the revenue stack before they become problems, from silently failing automations to billing issues that hurt conversion. - Stay current with GTM engineering, automation tooling, and AI workflows, and apply new approaches where they create real business value. --- ## What You Bring to the Table ### Core Requirements - Hands-on experience building and maintaining production-grade automations using n8n, APIs, webhooks, HubSpot, and Stripe. - Strong understanding of usage-based billing and revenue operations, including trial conversion, dunning, failed payments, and Stripe billing workflows. - Solid backend and data fundamentals: comfortable with Supabase, SQL, and data models to understand system behaviour and troubleshoot issues independently. - Engineering mindset: you use GitHub, version your automations, and treat GTM infrastructure with the same discipline as production software. - AI-native working. ### Nice to Have - Experience with analytics and tracking tools such as GA4, GTM, Mixpanel, and attribution systems. - Familiarity with Webflow, conversion optimisation, landing pages, and lead-routing logic. - Exposure to technical SEO, GEO, or performance marketing. ### Always - You have taken ownership of complex systems end-to-end and can clearly explain the impact you delivered. We care about specifics and measurable outcomes. --- ## What We Offer - Competitive salary coupled with direct engagement in your success through an enticing ESOP. - Clear and transparent career progression scheme inspired by the best performing organisations, including fast track promotion opportunity for exceptional performance to support your growth ambitions. - Prime growth-stage company with proven revenue and a sharp edge in cloud — founded by serial entrepreneurs with multiple successful exits. - Experienced, passionate team working with cutting-edge cloud technology. - A vibrant office in a trendy location with free brain food and a canteen — plus a subsidized premium gym membership and monthly team meet-ups that bring the whole crew together! --- ## Our Culture We are committed to success. We embrace individuals from all backgrounds who share the goal of building a future European cloud champion, celebrated through a richly diverse team of 15+ nationalities and 10+ languages spoken. --- ## Our Hiring Process 1. **Apply:** Submit your CV or LinkedIn profile via the application form. 2. **First response:** We review every application carefully and get back to you within a few days. If your profile is a strong match, we'll invite you to an intro call via Google Meet. 3. **Get to know us:** We move quickly through two to four interview steps, including a meeting with our founders. 4. **Offer:** If it's a mutual fit, you'll receive a personal offer and feedback call, followed by a written offer document. --- *We may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us.* --- **When applying, mention the word CANDYSHOP to show you read the job post completely.**
LawnStarter
8 days ago
About LawnStarter LawnStarter is the nation's leading on-demand marketplace for lawn care and outdoor services, with over $100M in annual bookings. We're expanding beyond lawn care to become the one-stop shop for all home services — operating across three brands (LawnStarter, Lawn Love, Home Gnome) on a single shared platform. About Engineering at LawnStarter We're restructuring engineering around initiative teams: a Product Engineer paired with a PM and a designer, with an Engineering Manager who covers a couple of initiatives and supports your growth. The engineer leads AI agents like a team, ships the work, and is accountable — with the rest of the triangle — for whether the initiative moves its metric. We're betting that 1–2 strong engineers running AI agents can outship the labor-team model that defined the last decade of software. That bet only works if the engineers we hire are wired for ownership and can ship to a marketplace with real customers and pros on both sides. The Role You're the engineering anchor of one initiative at a time. The initiative is a team effort — an iron triangle of you, your PM, and your designer — and you have key participation across the full lifecycle: shaping the problem, deciding the technical approach, leading the AI agents that implement most of the code, shipping to production, and answering for the outcome alongside the rest of the triangle. You're accountable for the outcome — not for the volume of code merged. If an agent can ship it safely, your job is to make sure the agent does it right and the metric moves. If the initiative needs hand-written code in a sensitive area, you write it yourself. What makes this role different: You lead AI agents, not humans. Claude Code, Cursor, Codex, and our internal agent stack are your team. You own the quality, safety, and velocity of what they produce. You own an outcome, not a ticket queue. Problem-framing through production through the metric review 2–4 weeks after launch. You partner horizontally with PM and design. No tech lead above you. No architect approval. No ticket grooming committee. The bar is staff, not senior. You make the call when the call needs to be made. If you're waiting to be told, this isn't the role. What You'll Own The technical approach — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. You make the call, document it, and revisit it if the data says you were wrong. Agent-led implementation quality — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code on your initiative. Most lines will be agent-authored. You're accountable for them. Cross-functional partnership — daily working contact with your PM (scope, tradeoffs) and your designer (UX decisions, in-tool prototyping with agents), and weekly check-ins with your EM (initiative health, blockers, growth). The initiative outcome — the specific metric the initiative was set up to move. In partnership with your PM, you present results 2–4 weeks post-launch and share the "did it work" answer. A high bar for what ships under your name — production correctness, security posture, performance, observability, and the experience for customers and pros. Agents accelerate you; they don't lower the bar. Problems to Solve Leading AI agents at staff-level qualityMost of the code on your initiative will be authored by AI agents. The work is making agents ship as if a senior engineer wrote it: prompts that encode our codebase conventions, evals that catch hallucinations before merge, tests that exercise the edges, observability that catches the regression in production before a customer reports it. How do you build the agent workflow that lets one engineer ship what used to take a team? Owning an outcome without a tech leadYou don't have a tech lead to approve your design or an architect to escalate to. You have an EM who covers a couple of initiatives and peers on adjacent ones. How do you make calls fast, document them clearly, and stay accountable to the outcome — without slowing down for hierarchy that no longer exists? Shipping outcomes, not featuresThe initiative will be measured by a metric — a conversion rate, a retention curve, a pro-funnel KPI, a unit economics shift. You're accountable for the number, not the feature. How do you scope to actually move it, decide what to not build, and have the discipline to follow up 2–4 weeks after launch even when the next initiative is calling? What Success Looks Like (Year 1) Initiative outcomes hit — You've shipped 3–4 initiatives end-to-end, and at least two clearly moved the metric they were set up to move (with the post-launch review to prove it). Agent workflow that travels — The prompts, evals, and review loop you built for your initiative are adopted by at least one other engineer on an adjacent initiative. Cycle time — Median time from problem-framing to first production rollout on your initiatives is meaningfully shorter than the pre-restructure baseline. Zero "agent-shipped that" incidents — No customer- or pro-facing regression traceable to agent-authored code that you missed in review. Visible leverage — Other engineers point to artifacts you left behind — runbooks, evals, agent workflows, post-launch write-ups — as references they use. Who You Are AI-native. Claude Code, Cursor, Codex, or equivalent are how you ship — daily, on production work. You have opinions about prompts, evals, agent loops, MCP servers, and review workflows, and you know when to let the agent run vs. write it yourself. This is unlikely to be a good fit if you describe AI coding as "something you're exploring" or prefer to write everything by hand. Already operating at lead level. You may currently be titled Senior, Staff, Lead, or Principal — but in practice you've been the person making the call, shipping the hard thing, and answering for whether it worked. This is unlikely to be a good fit if you've always had a tech lead breaking down the work for you. Outcome-driven, not output-driven. You measure your week in "did the metric move" and "did the experience get better," not in tickets closed. You read the post-launch dashboard and you own the answer. This is unlikely to be a good fit if you take pride in volume of code shipped or feel uncomfortable being measured on a number you don't fully control. A strong horizontal partner. You hold your own with a strong PM and a strong designer. You bring engineering judgment to product calls and product judgment to engineering calls. This is unlikely to be a good fit if you hide behind "that's product's decision" or default to RICE-scoring tickets handed down to you. Decisive and documented. Architecture decisions, data-model choices, rollout plans — you write them down, get fast input, and move. This is unlikely to be a good fit if you wait for consensus on questions that have a clear right answer, or if you make calls and never write them down. Raises the floor, not just the ceiling. Your impact compounds beyond your own initiative because you leave artifacts — agent workflows, evals, runbooks, post-launch reviews. This is unlikely to be a good fit if you're a lone wolf who ships brilliantly but leaves nothing reusable behind. Cares about customers and pros. This is a real-world marketplace with real people on both sides. This is unlikely to be a good fit if you're chasing pure engineering elegance over business and customer outcomes. This Role Is NOT A tech lead in an old-style team. No 4–5 engineers reporting up to you on technical direction. The team is you + PM + designer + EM, with AI agents doing most of the implementation. A management role today. People management is the EM's job in this role. That said, the path can grow into management for those who want it — it's an open door, not a closed one. A platform-only or architecture-only role. You're a Product Engineer. You ship features that move metrics, end-to-end. Platform work happens inside the initiative when it's needed for the outcome. A "let AI do everything" role. Agents handle implementation grunt work. You handle judgment, design, safety, and accountability. The bar is higher than the old senior bar, not lower. A research role. This is shipping to a marketplace with $100M+ in bookings. Customers and pros are using what you ship inside the same week. Tech You'll Touch AI agents — Claude Code, Cursor, Codex, internal agent stack, MCP servers, evals tooling Backend — PHP/Laravel Frontend — TypeScript/React/React Native (customer & pro apps, web and mobile) Data — Redshift, dbt, Segment, Airflow Infra — AWS, Datadog, Sentry, GitHub Actions Documentation & process — Brain (Claude Code skills + docs repo), Confluence, Jira You don't need every box checked. You need deep skill in at least one of our stacks plus credible production experience with AI coding agents. Benefits Competitive salary of USD $80,000–$100,000 annual base Work from anywhere High ownership and autonomy Fast-moving team that loves to build, learn, and grow
Cryptio
9 days ago
## About Cryptio Cryptio is the leading **enterprise-grade financial data transformation and digital asset ERP platform** for accounting, financial reporting, tokenization compliance, and loan management solutions. It is a complete back and middle-office platform that delivers financial integrity and accountability for businesses in crypto. Its platform allows users to transform on-chain and off-chain crypto activity into auditable records for accounting, treasury, tax filings, license applications, loans activity, and regulatory reporting. Having recently announced our **$45m series B**, now couldn't be a better time to join! ## About the role We're hiring our first Applied AI Engineer to work directly with our Advisory Intelligence Product Engineer and the VP of Advisory Intelligence on net-new product. You'll have full-stack ownership from Postgres schema to React UI, and you'll collaborate directly with the VP on prompt architecture, workflow design, and product roadmap. The team is small on purpose. This is a high-autonomy seat with real room to grow. You'll experiment, ship, and shape the toolkit's direction. As the practice scales, the right person grows into a technical leader for the function. ## What you'll do The Advisory Intelligence toolkit covers the full accounting workflow: transaction-level close processes, chart of accounts benchmarking, policy generation, fit-gap analysis against institutional standards, and financial reporting outputs. Each tool combines deterministic logic (the parts where being wrong has financial consequences) with AI layers that draw on a structured library of real client engagements. You'll work across the suite with primary ownership on net-new builds. - Collaborate directly with the VP on prompt architecture, workflow design, and product roadmap. You're a builder who shapes what gets built. - Own full-stack feature delivery from Postgres schema through API layer through React UI - Build and maintain multi-step AI pipelines: prompt chaining, structured output parsing, confidence scoring, failure recovery, and audit-trail logging - Integrate third-party financial data APIs into production tool workflows - Build financial document ingestion: parse uploaded spreadsheets and structured reports into typed data models for downstream AI processing - Maintain and extend the deterministic pre-processing and heuristic layers that make AI output reliable enough for audit - Contribute to the AI output evaluation framework: structured test inputs, expected outputs, scoring rubrics - Work cross-functionally with finance practitioners, product, design, and leadership to scope what gets built and push back on specs that miss ## What you'll bring ### Core engineering - Production full-stack TypeScript: shipped real systems, not side projects - Strong Node.js backend: REST APIs, middleware auth, async pipelines with batching, concurrency limits, retries, timeouts - React and TypeScript for complex UI: state management with Zustand, schema validation with Zod, views that stay responsive at scale - Exposure to distributed systems and microservice architectures: you understand the failure modes (partial writes, retries, ordering, observability) even if you haven't owned a microservice deployment end-to-end ### Data and Postgres - Strong Postgres: data modeling for workflow and run-oriented schemas, indexing strategy, query troubleshooting at table scale - Experience designing versioned config and audit-trail schemas. Append-only matters in compliance contexts and you've built for it. ### How you operate - Strong communicator, written and verbal. You can explain a technical decision to a finance practitioner and a product spec back to engineering. - You take initiative. When the spec is wrong, you propose alternatives. When something's broken, you don't wait to be asked. - You work cross-functionally without friction. Finance, product, design, leadership are all on your week, not just other engineers. - Comfortable owning a feature from schema to UI without handoffs ## Bonus points - Hands-on production LLM work with AWS Bedrock, OpenAI, or the Anthropic SDK at real throughput - Multi-step prompt workflows: chaining, structured output extraction, confidence thresholds, graceful degradation - Debugged AI in production. You know where prompt issues end and infrastructure issues begin. - Next.js App Router experience: API routes, SSR in data-dense interfaces - Background job infrastructure for AI workflows (BullMQ, pg-boss, or similar) - Finance or accounting tooling experience. Familiarity with GAAP/IFRS, month-end close, or audit process is a real advantage. - AWS deployments, Docker, CI/CD pipeline ownership - Logging, monitoring, and production debugging in distributed systems - Parsing financial document formats (Excel, structured CSV, ERP exports) into typed pipelines ## Perks - 👩💻 Remote or Hybrid working - 🏝️ 25 days paid holiday plus bank holidays - 🙌 One additional day of annual leave each year, up to 30 total days - 🎂 Your birth off - 🧘 Mental health resources, wellbeing programs, and professional coaching - 🫶 Family-friendly policies - 💪 Fitness and wellness budget - 💻 MacBook Pro - 🖥️ $200 home office setup budget - 🎓 Training and development budget - *We have additional benefits depending on location* ## If this sounds like you, we would love to hear from you 🙌 *At Cryptio, we move fast and take ownership of outcomes. We learn from failures, celebrate wins, and let humility, curiosity, and a passion for crypto guide how we work. If you value collaboration and want to build with purpose, you'll feel right at home here.* When applying, mention the word CANDYSHOP to show you read the job post completely.
Localcoin
11 days ago
## **ABOUT US** **Localcoin**, founded in 2017 with headquarters in Toronto, is on a mission to simplify the process and experience of buying or selling digital currencies globally. We envision bringing digital currency to the mainstream financial market through partnerships with leading corporate and franchised retail spaces. With terminals across Canada and Australia, Localcoin is now the largest Bitcoin ATM provider in Canada. At its core, Localcoin believes that everyone should be able to own cryptocurrency and have a deep understanding of blockchain technology. As a member of our rapidly growing team, you'll join a talented, dynamic group of team members who will encourage you to learn, grow and thrive in your career every step of the way. If you're a self-starter looking to hone your skills in a startup environment that fosters innovation, transparency and team connectivity, we look forward to hearing from you! ## **THE ROLE** Localcoin seeks to inspire the future of digital currency globally as the largest bitcoin ATM network in Canada. We are looking for an individual who is passionate about learning new technologies to join our growing Engineering team as our **Java Back End Developer**. As a **Java Back-End Developer** at Localcoin, you will be responsible for developing and maintaining functional and stable back end applications for our company, ensuring system consistency and availability. Working alongside the Engineering team, you should have an unyielding desire to learn and broaden your horizon along with contributing towards daily deliverables. You should be a team player, familiar with the Agile framework of delivery. ## **WHAT YOU'LL BE DOING** - Work with our cryptocurrency ATM backend server which connects over 200 machines to the network - Create, improve, and maintain high availability systems for cryptocurrency ATM network and online products such as: Know Your Client (KYC) identification verification software and transaction monitoring systems - Add software integrations with various Blockchain based networks and providers - Implement new features on the cryptocurrency ATM network such as: new cryptocurrency offerings, marketing campaigns, user experience features and more - Make data available from specific internal systems to client systems through distributed cloud environment ## **WHAT WE'RE LOOKING FOR** - 5+ years in backend development and strong knowledge in Java 8 along with Maven or Gradle - In-depth experience with Spring framework, including Spring Boot, JPA, MVC and Spring Security for building RESTful services - Experience with functional testing, unit testing, code coverage and static code analysis tools such as Sonar - Experience with BDD and related tools - Strong proficiency in SQL, DDL, DML, relational database design and indexing in any well known SQL databases such as MySQL, Postgres, Oracle DB, MSSQL - Proficient in Git flow, Maven, NGINX and Docker ## **THIS IS NICE (Preferred Skills)** - Experience with any CI/CD platforms on the cloud - Expertise on Linux platforms and shell commands - Good understanding of cloud environments like AWS/GCP - Good understanding of Cloudflare platform - Expertise using Swagger and/or Postman tools - Experience with NodeJS and NPM management - Experience with AngularJS/Angular - Expertise on Python scripting - Good understanding about asymmetric/symmetric encryption with OpenSSL - Good understanding about database-migration tools such as Flyway - Experience with manual automation tools such as Integromat ## **WHAT YOU'LL LOVE ABOUT US** - Competitive Salary - Health & Wellness Benefits - Hybrid & Flexible Office Environment - Professional Development - Standups, Demos and Monthly Socials to keep us aligned and connected - And so much more! *Localcoin is committed to building a team that represents a variety of backgrounds, perspectives and skills. The more inclusive and diverse we are, the more our work will improve. If you're determined and great at what you do, come as you are.* *If you require accommodation at any stage throughout the recruitment process, please notify your talent team or send an email to careers@localcoinatm.com.* When applying, mention the word **CANDYSHOP** to show you read the job post completely.
Polymarket
11 days ago
## About **Polymarket** **Polymarket** is the world's largest prediction market platform. We enable individuals to express views on real-world events by trading on outcomes across politics, economics, sports, culture, and current affairs. Built as a peer-to-peer marketplace with no centralized "house," Polymarket aggregates diverse opinions into transparent, market-based probabilities that reflect collective expectations about the future. We're growing fast, both in terms of volume ($21B traded in 2025) and adoption as an alternative news source. Our ambition is to become a ubiquitous beacon of truth in global media and we need your help adding fuel to the fire. ## About the Role Polymarket is looking for a **Senior Backend Engineer** to work on Gamma, the core backend powering Polymarket's markets platform. Gamma processes every market creation, trade, and resolution on the platform: at scale, under load, with no margin for error. You'll ship features with direct product impact, push the boundaries of what the system can handle, and help define how ownership evolves as the platform grows. If you want your work to matter immediately and visibly, this is that role. ## What You'll Do - **Architect and implement Go-based services.** Design and build services capable of sustaining high request throughput with low latency at scale. - **Define and enforce engineering standards.** Own API versioning strategy, error handling conventions, and service health benchmarks across the backend. - **Uphold code quality.** Drive quality through code reviews, shared conventions, and technical documentation that the broader team can build on. - **Partner cross-functionally.** Collaborate with teams across product and infrastructure to align backend services with broader company goals. - **Own reliability.** Contribute to on-call rotations and drive reliability improvements informed by incident trends and system behavior. ## What We're Looking For - 5+ years of production Go experience: fluent in Go idioms, interfaces, and concurrency patterns - Strong API and microservices architecture experience: designing, implementing, and maintaining REST and GraphQL APIs at scale - Deep SQL expertise with PostgreSQL or MySQL, plus familiarity with non-relational stores including Redis and ClickHouse - Event-driven architecture experience: messaging systems like Redpanda or Kafka, real-time data pipelines, and gRPC service communication - Hands-on observability and monitoring experience with Prometheus, Grafana, or OpenTelemetry for tracing, metrics, and alerting - (Plus) 1+ years of production Rust experience - (Plus) Familiarity with prediction markets, trading platforms, or financial systems - (Plus) Experience with blockchain or Web3 systems, particularly EVM-based - (Plus) Prior experience in a fast-paced startup environment ## Benefits - Competitive salary & equity - Unlimited PTO - Full Health, Vision, & Dental coverage - 401k match - Hardware setup: new MacBook Pro, big display, & accessories *When applying, mention the word CANDYSHOP to show you read the job post completely.*