Tóm tắt công việc
We're looking for a Senior Software Engineer who can move fluidly across the stack - frontend and backend - and who uses AI-native tools (Claude Code, Cursor, Codex, and similar) as a part of how they build, not as an afterthought.
You don't need prior end-to-end full-stack experience to apply. If your background is primarily frontend or primarily backend but you're genuinely interested in growing into a fullstack role, we want to hear from you. What matters more than your past title is your mindset and your ability to learn fast, especially with AI as a force multiplier.
You will not just "convert Figma to code" or "code tickets." Your core challenges will include:
Craft delightful, intuitive interfaces that anticipate user needs across our product suite - email, forms, checkout, and workflow automation.
Build and operate high-scale backend systems handling billions of annual events, solving real challenges in speed, data processing, and stability.
Build AI-powered features - smarter writing assistance, auto-generated designs, intelligent workflows, and new AI products built from the ground up.
Design strong APIs and integrations with partners like Shopify, Zapier, and WooCommerce.
Own your work end to end - from understanding why a request exists, to deciding what should be built, to shipping how it's built, in production.
Work directly with Product Managers and
Designers to decide how features should work - not just how they're implemented.
We hire for mindset first, technology second.
1. Engineering Skills
Whichever side of the stack you're strongest in today, we expect depth there and genuine curiosity about the other side:
Frontend
Deep skills in TypeScript and React (Hooks, Context); you understand how React works under the hood (re-rendering, virtual DOM).
Comfortable with modern build tools (Vite, Turbo) and monorepos.
Strong foundation in performance optimization and code-splitting.
Backend
Strong computer science foundation and problem-solving skills.
Experience with SOA architecture (Golang/[protected info] preferred), MongoDB/PostgreSQL, and AWS services.
Comfortable designing systems that stay fast even as traffic scales 10x.
AI-Augmented Development
You use AI tools (Claude Code, Cursor, Codex, etc.) as a genuine engineering practice - not just autocomplete. You know what to delegate to AI and what requires your own judgment, and you remain fully responsible for the code you ship.
2. Builder Mindset & Product Thinking
This is what we screen for most carefully:
Why & What before How. When you receive a request, your first instinct is to ask why it needs to exist and what problem it actually solves - not to jump straight into implementation.
You build for the user, not just the ticket. Whether it's an external customer or an internal ops teammate, you think about whether what you're building actually helps them, and you're not satisfied shipping something no one asked for or no one uses.
You see the big picture. You think about downstream impact, maintainability, and business consequences - not just your feature or module in isolation.
You've built things because you saw they were needed - not only because you were assigned to. Personal projects, internal tools, or improvements you drove yourself are all strong signals here.
3. Ownership & Collaboration
High responsibility. You work independently. You don't wait for detailed instructions - you talk to the PM, understand the requirement, and deliver the solution.
Ships to production. You take things all the way, not just to prototype or demo stage.
Clear async communication. You can explain technical problems to non-technical stakeholders clearly and respectfully, and you document assumptions rather than blocking on answers.
Teamwork. You believe in code reviews and knowledge sharing, and you help the team get better every day.
Nice to Have
Experience shipping AI or conversational UI features that improved real user outcomes.
Experience with SaaS-specific problems (fair usage, noisy neighbor), large-scale databases (sharding, partitioning, no-downtime migration), Martech, or Fintech domains.
Experience building internal tools for non-technical teams (ops, CS, support).
Experience leading an engineering team or mentoring other engineers.