Skip to main content

Boom

Software Engineer

Austin Texas$120k–$200kfulltimemidAdded today

About this role

Boom is hiring Software Engineers at multiple levels to build rental financial services for renters and property managers. You'll own full-stack products spanning tenant screening, rent reporting, CRM tools, and AI agents, working closely with leadership in Austin to ship features that impact millions of renters.

What you'll do

  • Design and build user-facing products and backend systems powering the rental platform
  • Own services in production including observability, on-call rotation, and incident debugging
  • Contribute to and evolve core backend architecture with focus on scalability and performance
  • Collaborate with product, operations, and leadership to align technical solutions with business needs
  • Drive engineering practices through code review, testing, and documentation
  • Work across focus areas: tenant screening, rent reporting, CRM, or AI/agents based on roadmap priorities

What they're looking for

  • Backend web development (3+ years professional experience)
  • Full-stack development across frontend and backend
  • Systems design and scalability
  • Production observability and incident response
  • API design and integrations
  • AI/LLM engineering (for agents track)
  • Code review and testing practices
  • SQL and database design
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Boom

Boom builds a financial services platform serving renters and property managers, offering rental-related financial products and tools. The company is hiring QA Engineers, AI Engineers, and Security Engineers to scale product quality, develop AI-powered customer and internal tools, and establish security practices across their platform.

View all jobs at Boom

Likely interview questions

  • Tell us about a backend system you've built that had to scale—what were the bottlenecks and how did you address them?
  • How do you approach owning a service in production, and can you walk us through a recent incident you debugged?