Erlang Developer at Statusneo · Gurugram · 4 - 14 years · ₹15L - ₹35L / yr · Profitable · Posted 12 Jun 2026

🔹 Role: Erlang Developer – Distributed Systems (Strict OTP Focus)
🔹 What You Will Do
- Design and build fault-tolerant distributed systems using Erlang/OTP
- Develop highly concurrent, real-time backend services
- Architect systems using:
- message passing
- actor model concurrency
- Build and maintain:
- supervision trees
- multi-node clusters
- Ensure:
- high availability (99.99% uptime)
- graceful failure recovery
- Debug:
- production issues in distributed environments
- Work on telecom / messaging / real-time platforms
🔹 Mandatory Skills (NON-NEGOTIABLE)
✅ Core (Must Have)
- Erlang (Recent & Production Experience)
- OTP framework
- GenServer
- Supervisor
- FSM
- Distributed Erlang
- clustering
- node communication
✅ Systems Knowledge
- Distributed systems design
- Actor model / message passing
- Fault tolerance patterns
✅ Erlang Ecosystem (Strong Indicators)
- Mnesia / ETS
- Riak
- Cowboy / Inets
- Rebar3 / Relx
✅ Platform & Infra
- Linux (debugging, system behavior)
- Networking (TCP, SNMP, SIP, HTTP)
- Messaging systems (Kafka / RabbitMQ)
- Databases:
- PostgreSQL / Mnesia
🔹 Experience Requirement
- 4–10 years backend experience
- 3+ years hands-on Erlang (recent)
- Production system ownership

About Statusneo
About
Experts in CLOUD NATIVE TECHNOLOGY CONSULTING & SOLUTIONS. We build, maintain & monitor highly scalable, modular applications that leverage elastic compute, storage and network of leading cloud platforms. Backed by Digital Leadership of the Big3 in strategy consulting in the US, we partner with fortune businesses across the globe and lead their business technology transformation.
Connect with the team
Similar jobs (10)

Apply and complete the screening questions on Just Interview:
https://app.justinterview.ai/apply/10004915?src=cutshort
Company: Lucid Growth Media
Website: https://lucidgrowthmedia.com/
Department: Engineering
Employment type: Full-time
Work mode: On-site
Job location: Shyamnagar, Jaipur, Rajasthan
Minimum experience: 4 years of professional experience
Maximum experience: 6 years of professional experience
Prior on-site development-team experience: At least 2 years
Monthly take-home salary: ₹60,000–₹80,000 — up to ₹80,000, based on demonstrated capability and relevant experience. The offer will include a salary breakdown.
Working schedule: Monday to Saturday; second and fourth Saturdays off. Sundays off.
Shift timing: 9:00 AM–6:00 PM (9-hour shift)
Application deadline: 30 September 2026
Skills: Node.js, TypeScript, Rust, asynchronous processing, REST APIs, database design, performance debugging, Git review and application security.
Job description
Join a small engineering team improving existing software and building new capabilities. You will own backend reliability, data correctness and asynchronous processing, and guide technical decisions across application and automation engineers.
This is a hands-on position involving production debugging, measured performance improvements, safe changes to existing code and release ownership. Company-provided AI coding tools support the work; you remain responsible for understanding and verifying what ships.
Responsibilities
- Develop and improve TypeScript/Node.js APIs and Rust services, including concurrency, failure handling and durable processing.
- Diagnose slow queries and API paths; improve schemas, indexes, caching and background jobs based on evidence.
- Define reliable service contracts, event identities, retries and reconciliation across connected components.
- Protect data access, credentials and permissions; plan migrations, staged releases and recovery.
- Review changes, document decisions and help engineers resolve technical blockers.
- Break work into tracked tasks with acceptance criteria, obtain the required approval and provide test/release evidence at completion.
Required skills and experience
- Substantial production Node.js/TypeScript experience and Rust experience you can explain through systems you personally changed or operated.
- Practical asynchronous Rust, ownership/error handling, network integration, persistence and debugging skills.
- Strong database fundamentals, including query analysis, transactions or consistency trade-offs, and safe migration practices.
- Experience with API authentication, automated tests, Git review, logging and controlled deployment.
- Clear written English for task plans, technical decisions, incident notes and constructive review discussions.
- Evidence of taking responsibility for a problem, responding to feedback and verifying the corrected result.
Experience with MCP/tool integrations, containerised services or performance profiling is useful. Depth in the core responsibilities matters more than a long list of frameworks.
How we work and hire
Work follows documented tasks, approval, implementation, review and verification. We value early escalation of blockers and honest reporting of results.
Selection includes a short AI-assisted initial interview, an approximately 60–90-minute practical using synthetic material, and an on-site technical discussion. Final hiring decisions include human review.
We are looking for an experienced Developer with experience in compiled languages and ready to work in Golang. You will be responsible for the Development of distributed services GUI and terminal application in Golang. Candidates should have strong understanding of Algorithms, Memory Management and Networking
Required Experience & Skills:
- C/C++/C#/Go/Rust.
- Networking, Database, Linux, Docker.
- Multiprocessing, Multithreading, Distributed computing, Thread synchronization techniques.
- Algorithms and data structures.
- Communication protocols, gRPC, MQTT, REST, Modbus, OPC...
- GUI Programming
- Testing, Debugging and performance optimization.
- REST APIs, MySQL, Redis
- Proficiency with Git for version control and collaborative development workflows.

Who we are: My AI Client is building the foundational platform for the "agentic economy," moving beyond simple chatbots to create an ecosystem for autonomous AI agents and they aim to provide tools for developers to launch, manage, and monetize AI agents as "digital coworkers."
The Challenge
The current AI stack is fragmented, leading to issues with multimodal data, silent webhook failures, unpredictable token usage, and nascent agent-to-agent collaboration. My AI Client is building a unified, robust backend to resolve these issues for the developer community.
Your Mission
As a foundational member of the backend team, you will architect core systems, focusing on:
- Agent Nervous System: Designing agent-to-agent messaging, lifecycle management, and high-concurrency, low-latency communication.
- Multimodal Chaos Taming: Engineering systems to process and understand real-time images, audio, video, and text.
- Bulletproof Systems: Developing secure, observable webhook systems with robust billing, metering, and real-time payment pipelines.
What You'll Bring
- My AI Client seeks an experienced engineer comfortable with complex systems and ambiguity.
Core Experience:
● Typically 3 to 5 years of experience in backend engineering roles.
● Expertise in Python, especially with async frameworks like FastAPI.
● Strong command of Docker and cloud deployment (AWS, Cloud Run, or similar).
● Proven experience designing and building microservice or agent-based architectures.
Specialized Experience (Ideal):
- Real-Time Systems: Experience with real-time media transmission like WebRTC, WebSockets and ways to process them.
- Scalable Systems: Experience in building scalable, fault-tolerant systems with a strong understanding of observability, monitoring, and alerting best practices.
- Reliable Webhooks: Knowledge of scalable webhook infrastructure with retry logic, backoffs, and security.
- Data Processing: Experience with multimodal data (e.g., OCR, audio transcription, video chunking with FFmpeg/OpenCV).
- Payments & Metering: Familiarity with usage-based billing systems or token-based ledgers.
Your Impact
- The systems designed by this role will form the foundation for:
- Thousands of AI agents for major partners across chat, video, and APIs.
- A new creator economy enabling developers to earn revenue through agents.
- The overall speed, security, and scalability of my client’s AI platform.
Why Join Us?
- Opportunity to solve hard problems with clean, scalable code.
- Small, fast-paced team with high ownership and zero micromanagement.
- Belief in platform engineering as a craft and care for developer experience.
- Conviction that AI agents are the future, and a desire to build their powering platform.
- Dynamic, collaborative in-office work environment in Bengaluru in a Hybrid setup (weekly 2 days from office)
- Meaningful equity in a growing, well-backed company.
- Direct work with founders and engineers from top AI companies.
- A real voice in architectural and product decisions.
- Opportunity to solve cutting-edge problems with no legacy code.
Ready to Build the Future?
My AI Client is building the core platform for the next software paradigm. Interested candidates are encouraged to apply with their GitHub, resume, or anything that showcases their thinking.

Golang Developer
Experience: 6-8 years
Employment Type: Permanent, Full-time
Desired Skill: Golang,Python, GRPC, RestAPIs, AWS
Work Mode: Pune, India
Availability: Immediate Joiners
Must have skills:
● 6+years of Software Development experience
● 5+years of GoLang programming; Prefers additional proficiency in Python
● Knowledgeable in writing REST APIs
● Comfortable programming in production grade systems
● Experience with building HTTP based services
● Strong background of optimizing performance
● Familiarity with event-driven systems
● Experience dealing with highly concurrent, distributed architectures/systems.
Good to have skills:
- Exposure to relational databases
- Experience with Cloud Providers such as AWS is an advantage; cloud privileged access (CIEM, IAM roles, ephemeral credentials)
- Experience using Terraform to manage infrastructure as code would be an advantage
- Hands-on experience building or extending Privileged Access Management (PAM) capabilities — credential vaulting, secrets management, password rotation, just-in-time / time-bound privileged access
- Working knowledge of privileged session management and session recording — session proxying/brokering, keystroke and video capture, session replay, live monitoring and termination, tamper-evident audit trails
- Familiarity with remote access protocols and gateways — SSH, RDP, HTTPS/web-based sessions; protocol proxying and man-in-the-middle session interception
About the Role
We are hiring a Backend Engineer to build and operate the services that power a leading technology marketplace being relaunched under new ownership.
You will work behind the GraphQL federation, inside the ~40 microservices that own billing, subscriptions, the catalog, RBAC, the proxy's control plane, and the Analytics/Quota services. The runtime is Node.js/TypeScript on AWS EKS, with Aurora MySQL / Postgres and DynamoDB for state, Redis / Elasticache / Couchbase for caching, Kafka (MSK) and Kinesis as the event backbone, and ClickHouse for real-time analytics reads. Every consumer-to-provider call passes through the proxy your services configure, and every dollar of marketplace revenue flows through the commerce code your services own.
Roles and Responsibilities
· Build and operate services — Design, ship, and run Node.js/TypeScript services that sit behind the GraphQL federation. Own a slice of the ~40-service estate end-to-end: API design, schema, persistence, tests, deployment, on-call.
· GraphQL federation subgraphs — Add types, resolvers, and capabilities to the federated Platform API. Keep subgraph boundaries clean; respect RBAC at the federation enforcement layer.
· Commerce backbone — Build the subscription, invoicing, overage, dispute, and payout flows that integrate with Stripe and PayPal webhooks and the billing state machine. Make sure metering, billing, and payouts stay accurate, auditable, and replayable.
· Proxy control plane — Build the management APIs and background workers that configure the runtime proxy: API keys, plans, rate-limit policies, quota caches, abuse signals.
· Event-driven systems — Produce and consume Kafka and Kinesis events safely: schema evolution, idempotency, retries, dead-letter handling. Operate Lambda consumers where they're the right tool.
· Data services — Help own the Node.js Analytics Service and Quota Service that front ClickHouse and Snowflake. Keep latency low, queries cheap, and authorisation correct.
· Performance and reliability — Diagnose hot paths, tune queries, add caches where they matter, and remove caches that have become liabilities. Write the SLOs and the alerts that defend them.
· Security isolation — Implement OAuth2 / JWT / mTLS where they belong; respect least-privilege; design APIs that fail closed.
· On-call and incident response — Take part in the rotation. Lead investigations across services when something rooted in your area breaks.
· LLM-assisted engineering — Use LLM-based coding and agentic tooling to evolve how features are designed, reviewed, and tested.
What Success Looks Like
• Services you own meet their SLOs, deploy multiple times a day, and rarely wake anyone up.
• Billing, subscription, overage, and payout flows you ship are accurate to the cent, replayable, and trusted by both providers and consumers.
• GraphQL subgraphs you maintain stay fast, well-typed, and pleasant to extend.
• Event pipelines you produce and consume are idempotent, observable, and survive replay and back-pressure.
• The first generation of agent-native primitives you help build land in production and start carrying real agent traffic.
What You Bring
• 5–8 years of backend engineering experience, with non-trivial work on production services that real customers depended on.
• Strong TypeScript / Node.js in a production service environment; comfort with async patterns, streams, and back-pressure.
• Solid API design — REST and GraphQL (ideally federation: Apollo Federation, Mercurius, or similar). Schema design, persisted queries, performance tuning.
• Production fluency with SQL — MySQL and/or Postgres. Bonus for Redis or ClickHouse.
• Experience with event-driven systems — Kafka or similar. You understand idempotency, exactly-once myths, and consumer lag.
• Hands-on AWS (EKS, MSK, Kinesis, DynamoDB, Lambda, DMS) and Kubernetes. Comfortable reading and writing Terraform.
• Modern engineering practice: observability, feature flags, CI/CD, and safe rollouts.
• Care for correctness on the money path — you have shipped billing, metering, or payment code before and have the scars to show for it.
• Bonus: experience with API gateways, rate limiting, quota enforcement, usage metering, agent protocols (MCP, A2A, x402), or LLM-based developer tooling.
• You write small, reviewable PRs. You add the test before you fix the bug. You would rather ship a smaller thing well than a bigger thing badly.
We are looking for a Backend Engineer (SDE 2) to build scalable backend systems for EV charging infrastructure and energy management platforms. The role focuses on developing high-performance APIs, event-driven systems, and data pipelines that process EV telemetry, charging sessions, and energy analytics.
What You'll Own
- Design and develop scalable backend services and RESTful/WebSocket APIs.
- Build microservices using Go.
- Design and optimize databases for high-volume telemetry and charging-session data.
- Build event-driven systems and data pipelines using Kafka or similar messaging systems.
- Work on real-time and batch processing workflows for telemetry, energy metrics, and analytics.
- Improve application reliability, performance, monitoring, and observability.
- Deploy and operate services using Docker and Kubernetes.
- Participate in system design, architecture discussions, code reviews, testing, and technical documentation.
- Mentor and support junior engineers when required.
Required Qualifications
- 3 - 5+ years of backend development experience building scalable APIs and microservices.
- Strong proficiency in Golang.
- Strong understanding of PostgreSQL, MongoDB, or other relational/NoSQL databases.
- Experience with query optimization, indexing, schema design, partitioning, or replication.
- Experience building event-driven or distributed systems using Kafka or similar messaging systems.
- Familiarity with GCP or other cloud platforms.
- Experience with Docker and Kubernetes.
- Experience with monitoring and observability tools such as Grafana, Kibana, or ELK.
- Strong understanding of system design, scalability, and performance optimization.
- Experience writing clean, maintainable, testable code with unit and integration tests.
Nice to Have
- Experience working with EV charging, energy management, mobility, or IoT platforms.
- Experience processing high-volume telemetry or time-series data.
- Experience with real-time data processing and analytics pipelines.
- Experience with WebSockets or other real-time communication protocols.
- Experience with CI/CD and production infrastructure.
- Experience working with distributed systems at scale.
Why Join Us
- Build backend infrastructure powering EV charging and energy platforms.
- Work on distributed systems, real-time data, and high-volume telemetry.
- Solve challenging problems around scalability, reliability, and performance.
- Take meaningful ownership of production systems and technical decisions.
Why this role exists
Most systems work at a low scale.
Very few survive real production load, complex workflows, and enterprise edge cases.
We are building a platform that must:
- Scale from 500K → 20M+ interactions/month
- Handle complex insurance workflows reliably
- Become easier to deploy as it grows, not harder
- This role exists to build the backend foundation that makes this possible.
What you’ll do
You will not just write services.
You will design and own core platform systems.
1. Scale the platform without breaking architecture
- Scale from 50K → 4M+ interactions/month
- Ensure:
- High availability
- Low latency
- Fault tolerance
- Avoid large rewrites — build systems that evolve cleanly
2. Build the workflow automation (WA) engine
- Design a flexible system with:
- States
- Stages
- Cohorts
- Dynamic workflows
- Ensure workflows:
- Handle edge cases reliably
- Can be configured easily
- Move from:
- Hardcoded flows → configurable execution engine
3. Build the insurance-specific data layer
- Design data models for:
- Policy states
- Claim workflows
- Consent tracking
- Ensure the system works across:
- Multiple insurers
- Multiple use cases
- Build a platform-first data layer, not use-case-specific hacks
4. Make deployment and setup simple
- Ensure workflows and data models are:
- Easy to configure
- Easy to launch
- Reduce friction for:
- Product teams
- Deployment teams
5. Create a compounding data advantage
- Build a data layer that:
- Improves with every deployment
- Captures structured signals
- Ensure data becomes a long-term edge, not just storage
6. Own production reliability
- Participate in on-call rotation across 3 engineers
- Ensure:
- Incidents are handled quickly
- Root causes are fixed permanently
- Build systems where reliability is shared, not individual
What success looks like
- Platform scales to 2M+ interactions/month smoothly
- Workflow engine supports complex, dynamic use cases
- Data layer enables fast deployment across accounts
- Edge cases are handled without constant firefighting
- System becomes easier to use as it grows
- Production issues are rare and predictable
Who you are
- You have built:
- Scalable systems
- Distributed services
- You think in:
- Systems
- Data models
- Trade-offs
- You are comfortable owning:
- Architecture
- Production systems
What will make you stand out
- Experience building:
- Workflow engines
- State machines
- Data-heavy platforms
- Strong understanding of:
- System design
- Distributed systems
- Failure handling
- Experience working in:
- High-scale production environments
Why join
- You will build the core backend of an AI platform
- Your work directly impacts:
- Scale
- Reliability
- Product capability
- You will design systems that move from:
- Use-case specific → platform-level infrastructure
What this role is not
- Not just API development
- Not limited to feature-level work
- Not disconnected from production realities
What this role is
- A system architect
- A builder of scalable platforms
- A driver of long-term technical advantage
One question to self-evaluate
Can you design backend systems that scale, handle edge cases, and become easier to use as they grow?
We are hiring high-caliber engineers with 3+ years of experience to build low-latency, high-throughput trading infrastructure in Rust, working directly under senior systems architects. This is a hands-on coding role on performance-critical systems — you will write, test, and ship the core code.
Responsibilities
- Develop and maintain high-performance backend services in Rust under the guidance of senior engineers
- Implement components of distributed, fault-tolerant systems handling high transaction volumes
- Write extensive unit, property-based, and simulation tests for correctness-critical code - Profile and optimize code for latency, throughput, and memory efficiency - Participate in design discussions and rigorous code reviews
- Debug and resolve issues in Linux-based production environments
Required Qualifications
- B.Tech/M.Tech in Computer Science from an IIT or NIT (mandatory) - 3+ years of professional software development experience in Rust, C++, or Java/Go with systems-level work; strong Rust proficiency or demonstrated ability to attain it fast - Understanding of financial markets and trading systems — order books, order types, matching concepts, spot and derivatives (futures/options) basics; hands-on experience with trading, broking, or market data systems is a strong plus - Excellent computer science fundamentals — data structures, algorithms, operating systems, networking, concurrency
- Solid grasp of multithreading and memory management; exposure to performance profiling and benchmarking
- Understanding of distributed systems concepts — replication, consistency, message queues (Kafka/NATS or similar)
- Experience with Linux, Git, and modern development workflows
- Strong problem-solving ability and hunger to work on hard systems problems
Preferred
- Competitive programming background (Codeforces/ICPC/CodeChef ratings welcome on the CV)
- Personal or open-source Rust projects
- Exposure to low-latency techniques — lock-free structures, zero-allocation design, binary protocols (SBE/Protobuf/FlatBuffers)
- NISM certifications, trading experience (personal F&O/options trading counts), or coursework in financial engineering
- Exposure to consensus algorithms (Raft), event sourcing, or deterministic testing
Growth Path
You will be mentored directly by senior systems engineers with deep exchange-infrastructure experience, with a defined progression to senior engineer ownership of subsystems within 18–24 months. This team is being built as a center of excellence in low-latency systems engineering in India.
Selection Process
- Resume shortlisting (college + evidence of strong engineering: projects, CP ratings, internships)
- Online DSA + systems assessment
- Live coding round (Rust/C++, performance-oriented problem)
- Systems and trading-concepts discussion round
- Culture and ownership round with the senior engineer you will report to
Compensation: top of market for the experience band, benchmarked against product companies, not services.
About the Role
We're looking for engineers who can independently design and build reliable backend services. Beyond writing code, you should be comfortable thinking about performance, data consistency, reliability, and maintainability.
Responsibilities
● Design and implement backend services.
● Translate business requirements into technical solutions.
● Design efficient database schemas.
● Build reliable asynchronous workflows.
● Debug production issues independently.
● Review code and mentor junior engineers.
● Improve application performance and reliability.
● Contribute to technical design discussions.
Must Have Strong Programming Skills
● Proficiency in at least one backend language.
● Strong Object-Oriented Design.
● Good understanding of design principles.
● REST API design.
● Writing maintainable, testable code.
Database Knowledge Comfortable with:
● Database design
● Query optimization
● Transactions
● Indexing strategies
● Locking (high-level understanding)
● Isolation levels (basic understanding)
● Data modelling Concurrency
Working knowledge of:
● Race conditions
● Concurrent updates
● Idempotency (basic understanding)
● Optimistic vs pessimistic locking (conceptual)
● Thread safety (language dependent)
Asynchronous Systems Experience with:
● Background jobs
● Queues
● Retry mechanisms
● Scheduled jobs
● Event-driven workflows (nice to have)
Problem Solving Should be comfortable:
● Debugging production issues.
● Reading logs.
● Identifying bottlenecks.
● Breaking large features into smaller tasks.
● Evaluating trade-offs before implementation.
Good to Have Experience with:
● Redis
● RabbitMQ / Kafka / BullMQ or similar
● Docker
● Kubernetes
● AWS
● CI/CD
● Monitoring & Logging tools
What We Look For Successful engineers here typically:
● Think before coding.
● Write maintainable solutions.
● Understand why a design works, not just how.
● Consider edge cases.
● Take ownership of production issues.
● Help improve the engineering practices of the team.
Interview Focus
● Programming fundamentals
● Database design
● SQL
● Concurrency scenarios
● API design
● Production debugging
● Problem-solving exercise
● Code review discussion
About the Role
We are hiring a Backend Engineer to build and operate the services that power a leading technology marketplace being relaunched under new ownership.
You will work behind the GraphQL federation, inside the ~40 microservices that own billing, subscriptions, the catalog, RBAC, the proxy's control plane, and the Analytics/Quota services. The runtime is Node.js/TypeScript on AWS EKS, with Aurora MySQL / Postgres and DynamoDB for state, Redis / Elasticache / Couchbase for caching, Kafka (MSK) and Kinesis as the event backbone, and ClickHouse for real-time analytics reads. Every consumer-to-provider call passes through the proxy your services configure, and every dollar of marketplace revenue flows through the commerce code your services own.
Roles and Responsibilities
- · Build and operate services — Design, ship, and run Node.js/TypeScript services that sit behind the GraphQL federation. Own a slice of the ~40-service estate end-to-end: API design, schema, persistence, tests, deployment, on-call.
- GraphQL federation subgraphs — Add types, resolvers, and capabilities to the federated Platform API. Keep subgraph boundaries clean; respect RBAC at the federation enforcement layer.
- Commerce backbone — Build the subscription, invoicing, overage, dispute, and payout flows that integrate with Stripe and PayPal webhooks and the billing state machine. Make sure metering, billing, and payouts stay accurate, auditable, and replayable.
- Proxy control plane — Build the management APIs and background workers that configure the runtime proxy: API keys, plans, rate-limit policies, quota caches, abuse signals.
- Event-driven systems — Produce and consume Kafka and Kinesis events safely: schema evolution, idempotency, retries, dead-letter handling. Operate Lambda consumers where they're the right tool.
- Data services — Help own the Node.js Analytics Service and Quota Service that front ClickHouse and Snowflake. Keep latency low, queries cheap, and authorisation correct.
- Performance and reliability — Diagnose hot paths, tune queries, add caches where they matter, and remove caches that have become liabilities. Write the SLOs and the alerts that defend them.
- Security isolation — Implement OAuth2 / JWT / mTLS where they belong; respect least-privilege; design APIs that fail closed.
- On-call and incident response — Take part in the rotation. Lead investigations across services when something rooted in your area breaks.
- LLM-assisted engineering — Use LLM-based coding and agentic tooling to evolve how features are designed, reviewed, and tested.
What Success Looks Like
• Services you own meet their SLOs, deploy multiple times a day, and rarely wake anyone up.
• Billing, subscription, overage, and payout flows you ship are accurate to the cent, replayable, and trusted by both providers and consumers.
• GraphQL subgraphs you maintain stay fast, well-typed, and pleasant to extend.
• Event pipelines you produce and consume are idempotent, observable, and survive replay and back-pressure.
• The first generation of agent-native primitives you help build land in production and start carrying real agent traffic.
What You Bring
• 5–8 years of backend engineering experience, with non-trivial work on production services that real customers depended on.
• Strong TypeScript / Node.js in a production service environment; comfort with async patterns, streams, and back-pressure.
• Solid API design — REST and GraphQL (ideally federation: Apollo Federation, Mercurius, or similar). Schema design, persisted queries, performance tuning.
• Production fluency with SQL — MySQL and/or Postgres. Bonus for Redis or ClickHouse.
• Experience with event-driven systems — Kafka or similar. You understand idempotency, exactly-once myths, and consumer lag.
• Hands-on AWS (EKS, MSK, Kinesis, DynamoDB, Lambda, DMS) and Kubernetes. Comfortable reading and writing Terraform.
• Modern engineering practice: observability, feature flags, CI/CD, and safe rollouts.
• Care for correctness on the money path — you have shipped billing, metering, or payment code before and have the scars to show for it.
• Bonus: experience with API gateways, rate limiting, quota enforcement, usage metering, agent protocols (MCP, A2A, x402), or LLM-based developer tooling.
• You write small, reviewable PRs. You add the test before you fix the bug. You would rather ship a smaller thing well than a bigger thing badly.











