Sr. Software Engineer - Production
Yubico · Santa Clara, CA · 1 mo ago
HybridEngineering$170k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "Why Join Our Mission?" and description of company. The role description: "The Role Yubico is looking for a Sr. Software Engineer...". We need sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We must only include sections that have real specific content.
We need to extract content:
- About the role: Could be the paragraph describing the role: "Yubico is looking for a Sr. Software Engineer who is innovative and has a passion for building security solutions and software. You will join our Production and Fulfillment Services (PFS) team. The PFS team develops the software systems that control our YubiKey production, fulfillment, and manufacturing. They build integrated end-to-end solutions for production software to enhance and scale our capabilities and ease of use for our operators and supervisors."
- Responsibilities: The "Tasks & Responsibilities" bullet list: Design, propose, and refactor applications... etc. We need to list each bullet as .
- Requirements: Basic Qualifications list.
- Qualifications: Preferred Qualifications list.
- Skills: Bonus Skills? Could be "Bonus Skills" maybe considered Skills.
- Benefits: U.S. Benefits Designed For Your Overall Well-being list.
- Pay: Salary Pay Range: $170,000 USD - $210,000 USD.
- Schedule: Not mentioned. So we should not include Schedule section.
Also we need to include maybe "About the company"? Not required but could be "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those headings if content exists.
We must not repeat job title as heading. Not include Job ID etc.
We must remove boilerplate: EEO, legal, etc. So we need to strip out all that.
We need to preserve all substantive information; do not invent or summarize away detail.
Thus we need to output HTML fragment with sections for each relevant part.
Let's extract details precisely.
Company description: "Meet Yubico Yubico is a global leader in identity security and creator of the YubiKey, the original hardware-backed passkey. We are publicly traded on Nasdaq Stockholm; our global footprint includes headquarters in Stockholm, Sweden, Silicon Valley, California; and Singapore. Why Join Our Mission? At Yubico, We Are Guided By a Shared Belief That Your Work Matters. We Operate Under a Cultural Philosophy Of Speed With Integrity, Pushing The Boundaries Of Technology To Secure The AI Frontier—protecting Both Human And Agentic AI Interactions—and Leading The Transition To Post-quantum Cryptography. In Everything We Do, We Live By Our Core Values Battle Friction: We constantly look for new ways to simplify our products, our work, and the user experience.Inspire Higher: We think big, champion the open internet, and strive to do the right thing even when it is difficult.One Team: We are open, responsive, and collaborative, overcoming challenges and celebrating our successes together. Aligned with our commitment to open standards, we foster a thriving builder ecosystem through the Yubico Developer Program, offering free open-source repositories, libraries, and SDKs to help developers rapidly integrate strong hardware authentication into any application. Through close collaborations with technical partners like Google, Microsoft, and Amazon, as well as newer frontiers like OpenAI, we continue to shape a safer digital world while donating security keys to protect vulnerable communities, journalists, and humanitarian groups worldwide through our Secure it Forward program."
That's a lot of prose; we can put under "About the role"? Actually that's more about company. But the instruction only gave example headings; we could still include "About the role" for role description, and maybe "About the company" not in list. But we could include "About the role" for the role description, and maybe we could also include a section "About Yubico"? Not in allowed headings but we could still include? The instruction says use
. Some are long sentences; we keep them.
Pay: "Salary Pay Range: $170,000 USD - $210,000 USD"
Now About the role paragraph: Should we include the company overview? The role description paragraph is: "Yubico is looking for a Sr. Software Engineer who is innovative and has a passion for building security solutions and software. You will join our Production and Fulfillment Services (PFS) team. The PFS team develops the software systems that control our YubiKey production, fulfillment, and manufacturing. They build integrated end-to-end solutions for production software to enhance and scale our capabilities and ease of use for our operators and supervisors."
We could also include a brief about Yubico? Might be considered part of "About the role"? The instruction says "About the role" heading for section headings. So we can put that paragraph there. The company overview could be considered filler? It's substantive but not about role. However we could still include it under About the role as it's still relevant to the job posting. But to be safe, we could include both paragraphs: first the company overview, then the role description. That would still be under About the role.
Thus About the role will contain two paragraphs: first the company overview (Meet Yubico ... Secure it Forward program.) and second the role description.
We must ensure we don't include any boilerplate like "We are an equal opportunity employer" etc. We removed those.
Now produce HTML.
We must not include or . Just the fragment.
Let's construct:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those headings if content exists.
We must not repeat job title as heading. Not include Job ID etc.
We must remove boilerplate: EEO, legal, etc. So we need to strip out all that.
We need to preserve all substantive information; do not invent or summarize away detail.
Thus we need to output HTML fragment with sections for each relevant part.
Let's extract details precisely.
Company description: "Meet Yubico Yubico is a global leader in identity security and creator of the YubiKey, the original hardware-backed passkey. We are publicly traded on Nasdaq Stockholm; our global footprint includes headquarters in Stockholm, Sweden, Silicon Valley, California; and Singapore. Why Join Our Mission? At Yubico, We Are Guided By a Shared Belief That Your Work Matters. We Operate Under a Cultural Philosophy Of Speed With Integrity, Pushing The Boundaries Of Technology To Secure The AI Frontier—protecting Both Human And Agentic AI Interactions—and Leading The Transition To Post-quantum Cryptography. In Everything We Do, We Live By Our Core Values Battle Friction: We constantly look for new ways to simplify our products, our work, and the user experience.Inspire Higher: We think big, champion the open internet, and strive to do the right thing even when it is difficult.One Team: We are open, responsive, and collaborative, overcoming challenges and celebrating our successes together. Aligned with our commitment to open standards, we foster a thriving builder ecosystem through the Yubico Developer Program, offering free open-source repositories, libraries, and SDKs to help developers rapidly integrate strong hardware authentication into any application. Through close collaborations with technical partners like Google, Microsoft, and Amazon, as well as newer frontiers like OpenAI, we continue to shape a safer digital world while donating security keys to protect vulnerable communities, journalists, and humanitarian groups worldwide through our Secure it Forward program."
That's a lot of prose; we can put under "About the role"? Actually that's more about company. But the instruction only gave example headings; we could still include "About the role" for role description, and maybe "About the company" not in list. But we could include "About the role" for the role description, and maybe we could also include a section "About Yubico"? Not in allowed headings but we could still include? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those. The company overview could be placed under "About the role"? Might be odd but acceptable. However we could also include a separate "About Yubico" but not in list; risk of being considered filler? Better to follow examples.
Thus we will have sections:
About the role
with paragraph(s) describing role.
Responsibilities
with - ...
Requirements
with - ...
for Basic Qualifications.
Qualifications
with - ...
for Preferred Qualifications.
Skills
with - ...
for Bonus Skills.
Benefits
with - ...
for U.S. Benefits.
Pay
with
About the role
with paragraph(s) describing role.Responsibilities
with- ...
Requirements
with- ...
Qualifications
with- ...
Skills
with- ...
Benefits
with- ...
Pay
withSalary Pay Range: $170,000 USD - $210,000 USD
No Schedule. We must ensure we preserve all substantive information from those sections. Let's extract each bullet. Responsibilities bullets: - Design, propose, and refactor applications and integrations that enable Windows desktop operators to leverage the full capabilities of our custom production equipment. - Experiment, create prototypes and refine your work based on user feedback, industry standards, and business needs. - Work collaboratively across functions with our Product Managers, Production, Hardware, and UX designers to bring the most user-friendly and streamlined software for our operations. - Hone your skills in designing and developing compelling user experiences using native and cross-platform technologies. - Expand your technical knowledge of the various security technologies and protocols that YubiKeys supports (e.g, FIDO2 / WebAuthn, FIDO U2F, PIV, etc.). We need to keep exactly as given. Basic Qualifications bullets: - Bachelor or MS in Computer Science or a relevant technical discipline or equivalent experience, including 5+ years of software engineering experience. - Familiarity with operating system internals and services, such as synchronization. primitives, efficient file system access, threading and thread safety, and logging facilities. - Proven experience of building system software using native and/or memory safe languages such as modern C++, C#, .Net. - Hands-on experience with REST API integrations. - Hands-on experience using AI tools such as Claude/Codex/ChatGPT. - Architecture and design knowledge and experience. - Knowledge and/or experience with asymmetric cryptography. - Experience with UI Frameworks (e.g., Avalonia UI, WPF (Windows Presentation Foundation) & XAML). - Experience working with CI/CD pipelines and hands-on experience with Kubernetes and GCP (or comparable cloud), ideally in production environments. - Thrives in a dynamic fast paced environment where you will be challenged to become better and expected to make a positive impact on Yubico Engineering. - Demonstrated ability to learn and apply new technologies. Note some have odd punctuation like "synchronization. primitives". We'll keep as is. Preferred Qualifications bullets: - Experience with writing and/or utilizing C/C++ libraries and software. - Experience with Postgres SQL. - Experience building and interacting with system level services. - Comfortable interacting with operating system APIs from application code, such as interacting with serial ports or block devices. - Comfortable working with binary serialization protocols and formats. Bonus Skills bullets: - Experience developing software to control robotics (e.g., developing an orchestration engine controlling robotic arms). Benefits bullets (U.S. Benefits Designed For Your Overall Well-being): - Health coverage. We’ve got you covered with top of the line health plans, including dental and vision. We pay 100% of your premium and 85% for your family. - Retirement plan. Our retirement plan includes a 401K dollar per dollar match up to 6% with a cap of $6K/year. Immediate vesting. - Wellness reimbursement. We offer $1,200.00 in wellness earnings (prorated based on start date) that you can use on your gym membership, a massage, or your favorite online fitness classes. This is a taxable benefit if you choose to participate. - Learning and development. We encourage your professional growth and offer a yearly development stipend of $3,000 and mentorship program. - Time off. We offer a total of 15 vacation days plus 10 holidays, and 7 sick days a year. - Paid parental leave. We love welcoming new family members to our YubiTeam! All parents receive 8 weeks of paid leave. Birthing parents receive an additional 8 weeks of paid leave (16 weeks total). - Commuter Benefits. If you need to commute to the office, we offer commuter benefits. - Strong mission & company values. We’re a global team on a global mission to make the internet more secure for everyone. We believe that every person’s work matters. That you should always be nice, stay humble, and have fun, and never take yourself too seriously. - Yubico offers a holistic Total Rewards package designed to support our employees in all aspects of their life inside and outside of work. We need to keep each as separateAbout the role
Meet Yubico Yubico is a global leader in identity security and creator of the YubiKey, the original hardware-backed passkey. We are publicly traded on Nasdaq Stockholm; our global footprint includes headquarters in Stockholm, Sweden, Silicon Valley, California; and Singapore. Why Join Our Mission? At Yubico, We Are Guided By a Shared Belief That Your Work Matters. We Operate Under a Cultural Philosophy Of Speed With Integrity, Pushing The Boundaries Of Technology To Secure The AI Frontier—protecting Both Human And Agentic AI Interactions—and Leading The Transition To Post-quantum Cryptography. In Everything We Do, We Live By Our Core Values Battle Friction: We constantly look for new ways to simplify our products, our work, and the user experience.Inspire Higher: We think big, champion the open internet, and strive to do the right thing even when it is