Company
Bland
Annual salary
$170k – $220k/yr
Location
San Francisco, CA
Listed
22d ago
- Experience:
- 4 to 9 years
- Workplace:
- Relocation: No
- Equity:
- Competitive
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
On-site in San Francisco, CA.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
Bland is hiring a Software Engineer to own network security across our infrastructure and to lead how we deploy Bland into our customers' environments.
Many of our customers operate in regulated industries and the public sector, and a growing number need Bland to run inside their own infrastructure. That includes bring-your-own-cloud deployments and fully air-gapped, on-premises installations on bare metal. Your first major project will be building and delivering those deployments. From there, you will own the security and networking of our platform across our commercial, FedRAMP, and customer-hosted environments.
You will also be our engineering point of contact for enterprise security. You will join security reviews and architecture discussions with customers and prospects, answer their questions directly, and turn their requirements into how we build.
You will report to the Head of Engineering and work closely with our Infrastructure team, led by our Principal Engineer.
What you'll do
- Design and deliver on-premises and bring-your-own-cloud deployments of the Bland platform, including air-gapped installations on bare metal.
- Own network security across our environments, including network architecture, segmentation, private connectivity, firewalls, TLS and mTLS, and encryption in transit and at rest.
- Build, harden, and maintain environments for security-sensitive enterprise and government customers, including our FedRAMP environment.
- Join enterprise security reviews and architecture calls with customers and prospects, and serve as the engineering point of contact for their security and networking requirements.
- Support our SIP and telephony infrastructure alongside its owner, and provide redundancy for its operation.
- Optimize compute usage across our Kubernetes and cloud workloads, including resource allocation, scheduling, and cost.
- Contribute to infrastructure reliability with the rest of the team and participate in on-call.
Common questions
How do I apply for the Software Engineer, Infrastructure (US) role at Bland? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this Bland role pay? +
The listing gives $170k – $220k/yr.
Is this role remote? +
The listing gives the location as San Francisco, CA. Relocation: No.
Software Engineer interview prep
Questions Software Engineer interviewers often ask. They aren't taken from this listing.
How do you approach designing a system when the requirements are still likely to change?
I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.
What's your process for debugging an issue that only reproduces in production, not locally?
I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.
How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?
I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.
How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?
I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →