Software Development Engineer III | Full stack - Wallet
Free to start · No card · 5 credits the moment you sign up
Job description
About HighLevel
Our People
Our Impact
About the Role
Must-have skills:
Responsibilities
- Own end-to-end feature delivery for the Wallet, Billing & Taxes platform – from API design and backend implementation to necessary Vue.js frontend changes.
- Build and maintain highly stable, performant, and scalable backend services using Node.js, MongoDB, and distributed systems patterns.
- Identify and fix systemic issues (crashes, time-outs, race conditions, memory leaks, etc.) to improve overall platform reliability.
- Drive performance optimizations and cost-efficiency improvements (query tuning, caching strategies, indexing, reducing cloud spend).
- Actively reduce technical debt by refactoring critical parts of the codebase, improving test coverage, and eliminating anti-patterns.
- Implement and enforce security best practices (input validation, auth flows, secrets management, rate limiting, etc.) in every change.
- Enhance observability – add meaningful logs, metrics, alerts, and tracing to make issues easier to debug in production.
- Collaborate closely with QA from day one: review test cases, perform live demos during QA handover, and quickly address feedback.
- Contribute to internal tooling and automation that speeds up development and deployment cycles.
- Pair with other engineers, share knowledge, and help unblock teammates when needed.
- Participate in on-call rotation and resolve production incidents for the services you own.
- This is a hands-on IC role where you’ll write a lot of production code, ship frequently, and directly impact the stability and scalability of our Wallet platform.
Requirements
- 4–7 years of backend engineering experience with proven exposure to scale (high TPS, large datasets, or multi-tenant environments)
- Expert-level Node.js and a strong track record of writing clean, modular, reusable codeDeep expertise with MongoDB (complex schemas, aggregation pipelines, indexing, sharding)
- Solid production experience with Redis (caching, rate-limiting, pub/sub, distributed locks)Hands-on experience building and running microservices on Kubernetes (basic K8s knowledge is sufficient – deployments, services, configmaps, etc.)
- Strong hands-on experience with any major cloud provider (GCP, AWS, or Azure) – you know how to use managed services for containers, queues, caches, serverless, and databases effectively
- Comfortable contributing to the frontend using any modern UI framework (Vue.js, React, Angular – Vue.js experience is a plus but not mandatory)
- You’ve shipped and supported large-scale, mission-critical systems that stayed stable under heavy load. You love modular architecture, obsess over performance and cost on GCP, and can jump into the frontend when needed to ship complete features.
Preferred Experience
- Experience with AI Tools and contributions to open-source tools, internal platforms or engineering blogs
- NestJS or Express.js experience
- Elastic search for search/filtering use cases
- Exposure to any OLAP system (ClickHouse, Snowflake, BigQuery, etc.)
EEO Statement
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for HighLevel. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.