Tenna→
Senior DevOps Engineer at Tenna in Remote
ExperiencedRemoteRemote
Skills
awseksrdsaurorapostgresqlaws cdkjavascripttypescriptgithub actionsinfrastructure as codevpcsdnscontainer orchestrationincident responseroot cause analysisownershipcommunicationproblem solvingcuriositysound judgmentdocumentationcollaborationdistributed messagingcachingsearch
Job Description
Senior DevOps Engineer
Remote - Nationwide
Tenna – Development Team /
Full-time /
Remote
Submit your application
- Resume/CV ✱
File exceeds the maximum upload size of 100MB. Please try a smaller size.
- Full name✱
- Email✱
- Phone ✱
- Current locationNo location found. Try entering a different locationLoading
- Current company ✱
Links
- LinkedIn URL
- Twitter URL
- GitHub URL
- Portfolio URL
- Other website
Employment Application
- What is your full legal name?✱
- What is your current mailing address? (Please include city, county, state and ZIP code)✱
- Home Telephone✱
- Mobile Telephone✱
- Email Address✱
- Date available for work✱
- What type(s) of employment are you considering? (Full-Time, Part-Time, Contract, etc.)✱
- What is your minimum salary requirement?✱
- Are you subject to any type of agreement with a current or former employer that would restrict your ability to work at our company (e.g., non-complete, non-solicitation?)?✱
- What is the highest level of education that you have completed?✱Select...Some High SchoolHigh SchoolAssociates DegreeBachelors DegreeMasters DegreeDoctoral Degree
- Do you now or will you in the future require sponsorship to work in the United States?✱Select...YesNo
- How did you hear about this job opportunity?✱
- Please list (3) professional references
Senior DevOps Engineer Questions
- How many years have you worked in platform, infrastructure, DevOps, or SRE roles?✱
- Less than 3 years
- 3–4 years
- 5–8 years
- 9+ years
- Which best describes your most recent role?✱
- I supported production systems as part of a larger team, but didn't own them
- I've been a senior individual contributor owning production systems end to end
- I've worked mainly in development or QA rather than infrastructure/operations
- I've been in a lead or managerial role, mostly directing rather than hands-on
- How would you describe your hands-on experience running production infrastructure on AWS?✱
- Substantial — I've operated production AWS environments day to day
- Some — I've worked in AWS but alongside someone who owned it
- Little to no production cloud experience
- What's your hands-on experience operating container-orchestrated workloads in production (e.g., Kubernetes/EKS — deploying, scaling, upgrading, troubleshooting)?✱
- I've run and upgraded clusters and troubleshot workload issues in production
- I've deployed workloads onto clusters others managed
- I've used containers (e.g., Docker) but not orchestration in production
- No production container-orchestration experience
- Have you personally operated managed relational databases (e.g., RDS/Aurora, PostgreSQL) in production, including diagnosing performance problems?✱
- Some exposure, but not something I owned
- No
- Yes, as part of my regular responsibilities
- Have you owned on-call and led incident response, including root-cause analysis and postmortems?✱
- I've participated in on-call/incidents but not led
- No
- Yes, I've led incident response and postmortems
- How many years of hands-on Kubernetes experience do you have in production?✱
- Less than 1 year
- 5+ years
- 1-2 years
- 3-4 years
- This role requires up to 10% travel. Are you able to meet this requirement, with or without reasonable accommodation?✱
- Yes, I can travel as required
- No, I'm not able to travel
Submit application
Benefits
401k match
Paid Time Off
Volunteer Time Off
Dependent Care
Employee referral bonuses
Low-cost benefit packages