Position: Windows Software Engineer Location: Pittsburgh, PA 120-135K + Sign on Bonus + Full Benefits + Paid Relocation Flexible work from home days' Work onsite full time or work a flex schedule with more than 50% onsite. Please click on the link to apply.
Butler Recruitment Group’s Post
More Relevant Posts
-
Marketing Assistant at EERS ----tiktok.com/@eershungary instagram.com/eers.fibeersx #socialmediamarketing #tartalommarketing #engineering #lasertechnology #laser
EERS Support -on-site consultation -we help with installation, integration and commissioning -windows compatible servers -we provide training for our customers -we have a full Hungarian support background -technical support !4 year warranty! #warranty #warrante #4year #fiber #fibeersx #fiberlaser #laser #lasertech #lasertechnology #product #production #engineer #engineeringsolutions #engineeringprojects #engineering #project #projectengineer #projectmanagement #projectmanager #projectmanagers #manager #quality #multifunctional #support #supportlocal #localsupport #training #traininganddevelopment #development #developmentprojects #processengineering #process #processing #production #product #productdevelopment
To view or add a comment, sign in
-
What is workaround patch to Mitigate Hardware Issues? Since my career began as a Linux BSP engineer, I have encountered many challenging issues. The most difficult ones to deal with are hardware issues. Throughout my career, I have had heated arguments with hardware engineers, but some of them have also become good friends. Reflecting on my experiences, this post is aimed at Linux BSP engineers like me. I would like to share some insights for Linux system (embedded) developers to keep in mind. Near the end of a project, the software project manager is often in a situation where they need to freeze the software version. At this time, the hardware team or engineers usually send an email to arrange a meeting with the software manager. In the meeting, they share something that Linux BSP engineers hate to hear. They often say things like: - The hardware engineers made minor mistakes in circuit design. - The problem is that there is no chance to modify the circuit diagram. - We are requesting that system software engineers create workarounds to mitigate the hardware problems. In this situation, Linux BSP engineers have no choice but to create workaround patches to mitigate the issues related to hardware design. Common questions include: "What are examples of patches?" Here are some examples(This one is most important in this post): 1. Configure a particular pin as pull-up (this is called a software pull-up). 2. Disable the dynamic voltage table in specific cases. 3. Disable power-gating of specific IP in corner cases. 4. Apply a sequence to the GPIO with high-to-low or low-to-high transitions in corner cases. 5. Disable sleep mode in corner cases. 6. Reboot the first bootloader again at the early boot stage. 7. Disable a specific pin. After the meeting, I had no choice but to create these workaround patches while working overtime. I felt overwhelming stress and pain, working until 2 am to create patches even though the issues were related to hardware, not software. I thought to myself that what happens if I already prepared for these kinds of situations. After the 3~4 projects were completed with mitigating patches, I had created more than 30 patches to mitigate hardware issues. For me, I make it rule to prepare for patches before starting a new project to avoid unnecessary overwork. If this post is helpful, please follow me Austin Kim. BR, Austin Kim
To view or add a comment, sign in
-
Reposting a great explanation about Linux workaround patches by Austin Kim Linux workaround patches are often used to mitigate hardware issues that cannot be resolved through hardware changes or replacements. These patches can address a variety of hardware problems, such as bugs in processors, issues with specific peripheral devices, or other hardware malfunctions.
What is workaround patch to Mitigate Hardware Issues? Since my career began as a Linux BSP engineer, I have encountered many challenging issues. The most difficult ones to deal with are hardware issues. Throughout my career, I have had heated arguments with hardware engineers, but some of them have also become good friends. Reflecting on my experiences, this post is aimed at Linux BSP engineers like me. I would like to share some insights for Linux system (embedded) developers to keep in mind. Near the end of a project, the software project manager is often in a situation where they need to freeze the software version. At this time, the hardware team or engineers usually send an email to arrange a meeting with the software manager. In the meeting, they share something that Linux BSP engineers hate to hear. They often say things like: - The hardware engineers made minor mistakes in circuit design. - The problem is that there is no chance to modify the circuit diagram. - We are requesting that system software engineers create workarounds to mitigate the hardware problems. In this situation, Linux BSP engineers have no choice but to create workaround patches to mitigate the issues related to hardware design. Common questions include: "What are examples of patches?" Here are some examples(This one is most important in this post): 1. Configure a particular pin as pull-up (this is called a software pull-up). 2. Disable the dynamic voltage table in specific cases. 3. Disable power-gating of specific IP in corner cases. 4. Apply a sequence to the GPIO with high-to-low or low-to-high transitions in corner cases. 5. Disable sleep mode in corner cases. 6. Reboot the first bootloader again at the early boot stage. 7. Disable a specific pin. After the meeting, I had no choice but to create these workaround patches while working overtime. I felt overwhelming stress and pain, working until 2 am to create patches even though the issues were related to hardware, not software. I thought to myself that what happens if I already prepared for these kinds of situations. After the 3~4 projects were completed with mitigating patches, I had created more than 30 patches to mitigate hardware issues. For me, I make it rule to prepare for patches before starting a new project to avoid unnecessary overwork. If this post is helpful, please follow me Austin Kim. BR, Austin Kim
To view or add a comment, sign in
-
#hiring #infrasupportengineer #contract #newjersey #hybrid #sivak@arkhyatech.com Infrastructure Support Engineer @ New Jersey (Hybrid) Linux: Proficiency in various distributions (ubuntu) is expected.. Understanding command-line tools and shell scripting is important. 3+ Experience reading, writing, and debugging Go code Familiarity with shell & git Familiarity with continuous integration systems and concepts (ideally Github Actions) configuration management, live image, PXE boot #linux #ubuntu #support #go #shell #git #support
To view or add a comment, sign in
-
Nova Innovators, as a freelance IT services company, has a promising foundation, especially with its focus on Desktop Support Services, IT Support Services, and Network Support Services. Given the increasing reliance on IT infrastructure across industries, the demand for such services is high. #NovaInnovators #ITSupportServices #DesktopSupport #NetworkSupport #TechSolutions #FreelanceIT #TechConsulting #ITConsulting #ManagedITServices #NetworkEngineering #TechnicalSupport #ITInfrastructure #CloudSupport #Cybersecurity #ITProjectManagement #CustomerSupport #TechFreelancer #SmallBusinessIT #RemoteITSupport #TechStartup
At Nova Innovators, We are providing highly skilled IT, Desktop Support, and Network Engineers. Whether you require assistance with Windows installations, or complex tasks (stacking, switching routers) our team is equipped to handle it all. Best regards, Gulzaib Rehman (CEO Nova Innovators LTD) 📱+447365358981 📧 hr@novainnovators.com 🌐 Novainnovators.com #Europejobs #Recruiting #HiringNow #JobRecruitment #JobOpportunity #CareerOpportunities #NowRecruiting #HardwareSupport #ITServices #ITJobs #TechnicalSupport #NetworkTroubleshooting #TechSupport #NetworkEngineer #DesktopEngineer #DesktopSupport #DesktopServices #DesktopEngineering
To view or add a comment, sign in
-
We just fit 🤝🏻🎯 . We provide services: 1) RECRUITMENT AND STAFFING 2) SOFTWARE DEVELOPMENT 3) NOC AND FACILITY MANAGEMENT 4) CLOUD AND OTHER SOFTWARE SOLUTIONS #cybersecurity #tech #computerscience #programming #business #coding #innovation #security #technologynews #programmer #linux #technologyrocks #technologythesedays
To view or add a comment, sign in
-
When it comes to having secure software and by how it is designed it mainly starts at the operating system for instance like windows 10 or 11 which already have those types of measures in place for emergences. Luckly the system already set it up for the user but it can always be changed as well. with having a good control over your own devices software you can help prevent attacks on your own system from happening. #LetsBeCarefulOutThere and #flcc270 https://lnkd.in/ez-gZx5A
7 Principles of Secure Design in Software Development | Jit
jit.io
To view or add a comment, sign in
-
HIRING IMMEDIATELY OPEN FOR C2C and W2 Share your resumes to crizann@compestsolutions.com Job Posting Title- Principal Engineer - Embedded Systems Location : Onsite Philadelphia, Pennsylvania Position Type- Contract Technology: Embedded systems , Linux, Bash scripting, RDK-B is built on top of Linux, C and C++, TCP/IP, UDP, DHCP, Yocto build system. • Understanding of embedded systems and experience working with low-level hardware, including an understanding of CPU architectures, memory management, and device drivers. • Proficiency in Linux and experience in configuring, custornizing, and building Linux distributions, as RDK-B is built on top of Linux. • Strong programming skills in C and C++., which are the primary languages used in RDK-B development. • Familiarity with networking protocols, including TCP/IP, UDP, DHCP, DNS, and VLANs and other relevant protocols for networking devices. • Knowledge of the Yocto build system. • Understanding of the Linux kernel, as RDK-B often involves kernel-level customization. This includes kernel configuration, device drivers, and kernel modules. • Understanding of linux system programming. • Lead the design and development of software architecture, defining the structure and components of complex systems. Create architectural blueprints that guide the development team. • You should have experience in defining the architecture for at least one broadband component. • Proficiency with version control systems like Git for managing code repositories and collaboration with other developers. • Scripting skills in shell languages like Bash for automation and scripting tasks in RDK-B • Awareness of security best practices, as network devices need to be secure. This includes understanding encryption, authentication, and network security. • Understanding of wireless technologies, including Wi-Fi, and how to configure wireless interfaces in RDK-B • Familiarity with web-based user interfaces and web server technologies. RDK-B often includes web interfaces for configuration. • Proficiency in debugging tools and techniques, as embedded systems can be challenging to troubleshoot. • Good projec-t management skills to plan, prioritize, and execute tasks effectively, especially when working on complex, long-term projects. • Active participation in the RDK-B community and an understanding of its development processes and culture. • The ability to adapt to evolving technologies and software requirements as RDK-B and the networking landscape change. • Designs new software and web applications, supports applications under development and customizes current applications. Develops software update processes for existing applications. Assists in the roll-out of software releases. • Works with the Quality Assurance team to determine if applications fit specification and technical requirements. Tests and evaluates systems, subsysterns, and components.
To view or add a comment, sign in
-
12.5K+ Connection 📊 Embedded Software Engineer C| C++| Linux Internal| Data Structure| UART| I2C| SPI| CAN| TCP/IP| Shell Scripting| QT C++| SQLLite| Socket Programming| Embedded Yocto Linux
𝙒𝙝𝙚𝙣 𝙮𝙤𝙪 𝙥𝙤𝙬𝙚𝙧 𝙤𝙣 𝙮𝙤𝙪𝙧 𝙨𝙮𝙨𝙩𝙚𝙢 𝙧𝙪𝙣𝙣𝙞𝙣𝙜 𝙇𝙞𝙣𝙪𝙭, 𝙨𝙚𝙫𝙚𝙧𝙖𝙡 𝙨𝙩𝙚𝙥𝙨 𝙤𝙘𝙘𝙪𝙧 𝙪𝙣𝙙𝙚𝙧 𝙩𝙝𝙚 𝙝𝙤𝙤𝙙: 1️⃣ 𝙋𝙤𝙬𝙚𝙧 𝙤𝙣: You initiate the boot process by powering on your machine. 2️⃣ 𝘽𝙄𝙊𝙎 𝙄𝙣𝙞𝙩𝙞𝙖𝙡𝙞𝙯𝙖𝙩𝙞𝙤𝙣: The Basic Input/Output System (BIOS) initializes and checks the hardware components of your system, ensuring they are functioning correctly. 3️⃣ 𝘽𝙤𝙤𝙩 𝙇𝙤𝙖𝙙𝙚𝙧 𝙀𝙭𝙚𝙘𝙪𝙩𝙞𝙤𝙣: BIOS passes control to the boot loader, often GRUB, stored in a storage device like a hard disk. The boot loader then loads the kernel image and the initial RAM disk (initramfs) into memory. 4️⃣ 𝙆𝙚𝙧𝙣𝙚𝙡 𝙄𝙣𝙞𝙩𝙞𝙖𝙡𝙞𝙯𝙖𝙩𝙞𝙤𝙣: The kernel takes over from the boot loader. It checks the system hardware and initializes device drivers necessary for hardware interaction. 5️⃣ 𝙄𝙣𝙞𝙩 𝙋𝙧𝙤𝙘𝙚𝙨𝙨: The kernel mounts the initial RAM disk, which contains essential programs and binary files needed to mount the filesystem. The /sbin/init process is the first userspace process initiated by the kernel. It is responsible for starting other processes to run the system, such as setting up networking and initiating system services. On modern Linux systems, systemd has largely replaced the traditional SysV-style init system. 6️⃣ 𝙇𝙤𝙜𝙞𝙣 𝙎𝙘𝙧𝙚𝙚𝙣 𝙤𝙧 𝙂𝙐𝙄: Depending on the system configuration, the initialization process may lead to a command-line interface (e.g., bash) or a graphical user interface (GUI) login screen. Users can then log in and interact with the system. These steps provide a high-level overview of the boot process in a Linux system. Understanding this process can help in troubleshooting and gaining insights into system performance and behaviour. #ITHR #SoftwareEngineer #EmbeddedSystems #TechRecruitment #HR #EngineeringTalent #TechJobs #TechRecruiting #TechIndustry #SoftwareDevelopment #CodingLife #Programming #EmbeddedSoftware #EngineerLife #Innovation #TechCommunity #Developers #SoftwareDeveloper #Hardware #Firmware #OpenSource #Linux #CareerOpportunity #JobSearch #JobHunt #CareerDevelopment #CareerGrowth #LinkedInNetworking
To view or add a comment, sign in
4,859 followers