<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nava Public Benefit Corporation on Medium]]></title>
        <description><![CDATA[Stories by Nava Public Benefit Corporation on Medium]]></description>
        <link>https://medium.com/@NavaPBC?source=rss-382e245b904a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*o7SOz6xrEAXDDaqmLcuVMw.png</url>
            <title>Stories by Nava Public Benefit Corporation on Medium</title>
            <link>https://medium.com/@NavaPBC?source=rss-382e245b904a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:16:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@NavaPBC/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Interviewing at Nava: Preparing for your portfolio presentation]]></title>
            <link>https://blog.navapbc.com/interviewing-at-nava-preparing-for-your-portfolio-presentation-b4b2a6a2e1c?source=rss-382e245b904a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4b2a6a2e1c</guid>
            <category><![CDATA[interview-tips]]></category>
            <dc:creator><![CDATA[Nava Public Benefit Corporation]]></dc:creator>
            <pubDate>Tue, 30 Nov 2021 03:59:50 GMT</pubDate>
            <atom:updated>2021-11-30T04:04:44.974Z</atom:updated>
            <content:encoded><![CDATA[<h4>A portfolio presentation is not just a chance to show off your work. It’s also a time to share your process, what you learned, and maybe even things you would have done differently. Here are some tips to help you prepare for this essential part of Nava’s interview process.</h4><p>By Tamar Fox</p><p>The portfolio presentation is one of the last steps for design, content, and frontend dev candidates in Nava’s interview process. It’s part of a day of interviews we call an “onsite,” though it will most likely be conducted over a series of video calls.</p><p>If you’ve made it this far, we’re already excited about you, your skills and experience, and want to know more about how you work and think. The portfolio presentation is your chance to show us that. I’ve been on the other side of the table and know how intimidating this can be. But you’ll have a friendly audience that’s genuinely looking forward to hearing from you.</p><p>The first and best (and maybe most frustrating) advice I can give is to be yourself. It’s a cliche, but it’s also, frustratingly, correct. We want to get a sense of who you are and what excites you professionally.</p><p>Understanding how you work and think is essential for us to understand how you’d contribute to teams at Nava. This means that while it’s important to share finished products in your presentation, it’s also important to share how you got to them. You might want to consider things like:</p><ul><li>What are your processes throughout a project?</li><li>How do you engage and build trust with stakeholders?</li><li>What kinds of tools do you use?</li><li>What did you learn along the way?</li><li>What would you do differently next time?</li></ul><p>Building trust with stakeholders is a big part of our work. Tell us about how you’ve brought clients along with you as you design, build, and iterate. This is a lot of ground to cover in a relatively short period of time so it’s important to be prepared.</p><h3>How to prepare</h3><p>Here’s some tactical advice for planning your portfolio presentation. This structure is not a requirement. If it doesn’t work for you, you don’t have to use it. But if you’re feeling overwhelmed or stuck, it could help.</p><p>You’ll have an hour for this interview, including time for followup questions. Budget 40–45 minutes to present and 15–20 minutes for questions. We’ll give you a time check at 30 minutes.</p><p>You’ll present to a team of designers, usually two or more people. I highly recommend creating a deck of some kind to take us through your work. You’ll want to share your screen and take us through a presentation of two to three projects.</p><p>When you’re thinking about what projects to show us, pick something that you’re excited about and proud of and that’s a good example of how you work. But also err on the side of something that ultimately got launched. Volunteer work and prototypes are also good, but we’re especially interested in anything you have actually seen go into production.</p><h3>Try this structure</h3><p>Here’s what I suggest including in the presentation:</p><h4>Say hi!</h4><p>Introduce yourself and tell us about what kind of work excites you.</p><h4>Set an agenda.</h4><p>Let us know what you plan to talk about.</p><h4>Tell us about a project and your process.</h4><p>What was the challenge you were working on? How did you approach it? What were the constraints you had to work within? Did you work with a team? What were the roles of the other people on the team? Show us any artifacts and prototypes that might help us to get a better sense of your work.</p><h4>Tell us about the finished product.</h4><p>How did you get there? Why did you use the approach you used? Tell us about any research that went into it, and any iterations you went through.</p><h4>Tell us about any lessons you learned on this project.</h4><p>What did you take away from working on this project? Is there anything you would do differently if you could do it again?</p><h4>Repeat steps 3–5 for each project you’re talking about.</h4><h4>Finish up.</h4><p>Once you’re done presenting we’ll have questions. We don’t do gotcha questions at Nava, but we are super curious and always interested in things like:</p><ul><li>What risks did you see when you decided on this approach to your problem?</li><li>What kind of stakeholders were you working with? What was your relationship like?</li><li>How did you prioritize the work you needed to do?</li></ul><p>So, expect questions like those and the others above. If you need more help, Torrey Podmajersky has some great ideas in her <a href="https://docs.google.com/document/d/1vZ4mvq1smp5bz9TQTD5_h0pijiiwYe_HbR-vZkKJOd8/edit">Basic portfolio presentation outline</a>. You can also get a better sense of some of the work we do and the thinking behind it by browsing some of our <a href="https://www.navapbc.com/case-studies/shaping-policy-with-design-practices.html">case studies</a> and <a href="https://www.navapbc.com/toolkits/content-strategy-for-user-onboarding.html">toolkits</a>.</p><p>Remember that you wouldn’t be in front of us if we didn’t think you were a strong candidate. We’re excited to meet you and learn about your work.</p><h3>Join us</h3><p>Nava is a talented and diverse team working holistically across engineering, research, design, and operations to positively transform how people experience government. And we’re hiring. <a href="https://www.navapbc.com/careers/">Browse open roles to learn more.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4b2a6a2e1c" width="1" height="1" alt=""><hr><p><a href="https://blog.navapbc.com/interviewing-at-nava-preparing-for-your-portfolio-presentation-b4b2a6a2e1c">Interviewing at Nava: Preparing for your portfolio presentation</a> was originally published in <a href="https://blog.navapbc.com/">Nava PBC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navanauts at work]]></title>
            <link>https://blog.navapbc.com/navanauts-at-work-13651dcc7155?source=rss-382e245b904a------2</link>
            <guid isPermaLink="false">https://medium.com/p/13651dcc7155</guid>
            <category><![CDATA[security-engineering]]></category>
            <category><![CDATA[meet-the-team]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[civictech]]></category>
            <category><![CDATA[engineer]]></category>
            <dc:creator><![CDATA[Nava Public Benefit Corporation]]></dc:creator>
            <pubDate>Tue, 13 Jul 2021 16:08:39 GMT</pubDate>
            <atom:updated>2021-07-13T16:08:39.688Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Day at Nava as a Security Engineer</h3><p><em>It’s hard to describe what a typical day at Nava is like because no two days are ever the same. Every day brings new projects, challenges, and opportunities. So we’re sharing just a glimpse of what work is actually like for different</em><a href="https://www.navapbc.com/about/team/"><em> Navanauts</em></a><em>. Here’s what </em><a href="https://www.linkedin.com/in/mohib-r-519669a4/"><em>Mohib Rizv</em>i</a>,<em> Security Engineer, has been up to lately.</em></p><h3>Mohib Rizvi (he/him), Security Engineer</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*Bi_GzepQlZtQhxBL" /></figure><h3><strong>Current projects</strong></h3><p>My team and I are working on a project that will improve security operations and account compliance for various supported <a href="https://blog.navapbc.com/nava-pbc-wins-new-contracts-to-modernize-mission-critical-systems-with-the-centers-for-medicare-44e6c4dad8c1">Centers for Medicare &amp; Medicaid Services (CMS) applications</a>. Each application’s security posture is assessed using tools such as Prowler to verify the application’s configurations against CMS Standards. Our team is also responsible for assisting and guiding the application teams with improving their security posture.</p><p>Furthermore, to ensure CMS maintains a strong overall security posture, the team is developing solutions for monitoring and auto-remediation of non-compliant configurations. Developing and researching continuous compliance policies and solutions has been an exciting project as I learn the endless possibilities and security architectures available within the cloud.</p><p>I enjoy the challenge of solving puzzles with multiple moving parts by architecting and developing security solutions that streamline operations and improve efficiency.</p><h3><strong>On learning new skills</strong></h3><p>With Nava being a <a href="https://www.navapbc.com/values/">mission-driven company</a> that focuses on enhancing government operations, this was an ideal role for me, as it provided an opportunity to use my expertise and knowledge for a better cause while also learning new skills. Additionally, having worked with Centers for Medicare &amp; Medicaid Services before, I felt comfortable and confident with the work and ideas that Nava had planned with the government agency.</p><h3><strong>Nava’s culture in three words</strong></h3><p>Determined, transparent, and progressive</p><h3><strong>On government</strong></h3><p>The government is responsible for serving the entire nation, and it’s rewarding to play a role in improving how they deliver their services. These improvements impact the lives and well-being of many people across the nation, especially those in vulnerable populations.</p><h3><strong>When I’m not at work, I can be found…</strong></h3><p>Playing or watching sports, especially football.</p><h3>Join Us</h3><p>Nava is a talented and diverse team working holistically across engineering, research, design, and operations to positively transform how people experience government. And we’re hiring. <a href="https://www.navapbc.com/careers/">Browse open roles to learn more.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13651dcc7155" width="1" height="1" alt=""><hr><p><a href="https://blog.navapbc.com/navanauts-at-work-13651dcc7155">Navanauts at work</a> was originally published in <a href="https://blog.navapbc.com/">Nava PBC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Day at Nava as a Program Director]]></title>
            <link>https://blog.navapbc.com/a-day-at-nava-as-a-program-director-3249e5ce4054?source=rss-382e245b904a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3249e5ce4054</guid>
            <category><![CDATA[civictech]]></category>
            <category><![CDATA[program-director]]></category>
            <category><![CDATA[meet-the-team]]></category>
            <category><![CDATA[govtech]]></category>
            <dc:creator><![CDATA[Nava Public Benefit Corporation]]></dc:creator>
            <pubDate>Wed, 30 Jun 2021 18:58:24 GMT</pubDate>
            <atom:updated>2021-06-30T18:58:24.048Z</atom:updated>
            <content:encoded><![CDATA[<h3>Angela Colter (she/her), Program Director</h3><p><em>It’s hard to describe what a typical day at Nava is like because no two days are ever the same. Every day brings new projects, challenges, and opportunities. So we’re sharing just a glimpse of what work is actually like for different </em><a href="https://www.navapbc.com/about/team/"><em>Navanauts</em></a><em>. Here’s what </em><a href="https://www.linkedin.com/in/angelacolter/"><em>Angela Colter</em></a><em>,</em> <em>Program Director</em> <em>has been up to lately.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m8rZu1iuC8H4W_4D" /></figure><h3><strong>The path to Nava</strong></h3><p>After spending a four-year term of service with 18F, an office within the U.S. General Services Administration that partners with agencies to improve the user experience of government services, I was looking to join an organization with a similar mission. Many of my 18F colleagues made their way to Nava after their government service concluded, and I found that its mission aligned with my own.</p><h3><strong>Current projects</strong></h3><p>On the Caseflow project for the Department of Veterans Affairs (VA), the team <a href="https://www.navapbc.com/case-studies/shaping-policy-with-design-practices.html">developed an online process</a> for Veterans to appeal benefits decisions and <a href="https://www.navapbc.com/case-studies/Supporting-Veterans-During-the-Pandemic-with-Virtual-Tele-Hearings.html">schedule virtual hearings</a> with a judge. This helped Veterans get a decision about their benefits faster by reducing the backlog of appeals cases from 400,000 to 150,000, over one year. Other government agencies have taken note of Caseflow’s virtual hearings process and are eager to bring that functionality to their own systems.</p><p>With the state of California, we’re building a tracking system that will give people more information about the status of their unemployment claims. We expect this will reduce some of the anxiety for claimants waiting for their payments as well as the amount of time claims processors spend answering questions.</p><h3><strong>A typical day at Nava</strong></h3><p>A typical day at Nava would involve meetings with project teams; meetings to discuss staffing, contracts, finances, and business development on my projects; meetings with my direct reports; meetings with stakeholders; and candidate interviews. Basically a lot of meetings!</p><h3><strong>On government</strong></h3><p>I believe that people have a right to expect that the services their government provides are clear, accurate, and easy to use.</p><h3><strong>Professional development at Nava</strong></h3><p>The projects at Nava are a master class in so many areas of software development: user-centered design, agile processes, stakeholder management, team dynamics, and business operations. The folks here are highly skilled and more than willing to share their knowledge and approach to new team members.</p><h3><strong>When I’m not at work, I can be found…</strong></h3><p>Serving as an elections officer in my local precinct, gardening, and training my rescue puppy, a pit bull/Great Dane mix named Moxie, not to chew on my sneakers.</p><h3>Join Us</h3><p>Nava is a talented and diverse team working holistically across engineering, research, design, and operations to positively transform how people experience government. And we’re hiring. <a href="https://www.navapbc.com/careers/">Browse open roles to learn more.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3249e5ce4054" width="1" height="1" alt=""><hr><p><a href="https://blog.navapbc.com/a-day-at-nava-as-a-program-director-3249e5ce4054">A Day at Nava as a Program Director</a> was originally published in <a href="https://blog.navapbc.com/">Nava PBC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Day at Nava as a Frontend Developer]]></title>
            <link>https://blog.navapbc.com/a-day-at-nava-as-a-frontend-developer-8ecb62c079ce?source=rss-382e245b904a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ecb62c079ce</guid>
            <category><![CDATA[day-in-the-life]]></category>
            <category><![CDATA[meet-the-team]]></category>
            <category><![CDATA[diversity-and-inclusion]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Nava Public Benefit Corporation]]></dc:creator>
            <pubDate>Wed, 23 Jun 2021 16:35:24 GMT</pubDate>
            <atom:updated>2025-01-28T17:56:49.386Z</atom:updated>
            <content:encoded><![CDATA[<h3>Frontend Developer, Juweek Adolphe (he/him)</h3><p><em>It’s hard to describe what a typical day at Nava is like because no two days are ever the same. Every day brings new projects, challenges, and opportunities. So we’re sharing just a glimpse of what work is actually like for different </em><a href="https://www.navapbc.com/about/team/"><em>Navanauts</em></a><em>. Here’s what </em><a href="https://www.linkedin.com/in/juweek/"><em>Juweek Adolphe</em></a><em>,</em> <em>Frontend Developer has been up to lately.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*1J7Jmei7Qik8dh8x" /></figure><h3><strong>Current projects</strong></h3><p>Our Centers for Medicare &amp; Medicaid Services cloud team is starting to really dive into viewing quality assurance (QA) as an essential core of any team, and I get to play a big part in establishing founding principles on how we integrate QA into our process. Recently, the cloud.cms.gov website went through a big update, and <a href="https://blog.navapbc.com/nava-pbc-wins-new-contracts-to-modernize-mission-critical-systems-with-the-centers-for-medicare-44e6c4dad8c1">as we continue to better improve the site and its services,</a> we continue to maintain the quality of our codebase and experience. Trying to juggle both problems has been endlessly fascinating.</p><h3><strong>A typical day at Nava</strong></h3><p>I’m usually awake an hour or so before I get started on Nava work, so I start with writing down my to-do list and clarifying my intentions for the day. I work on two teams, so I try to break my day up into two parts; my mornings are spent as a QA engineer, while my afternoons are spent on the more traditional frontend duties of the Comms team. I’ll alternate between heads-down work and meetings for both teams.</p><h3><strong>On working on civic tech</strong></h3><p>I’ve always been attracted to the civic tech space, and I enjoy using my technical abilities for good. Nava is a company that leads the field in that regard. For a while now, but especially after the last year, many people’s faith in American government institutions and services has fallen. I think it’s important for me to offer up my skills to help preserve and build up government websites so that that faith may eventually be restored.</p><p>The government historically has played a large part in providing social services to its people, and I know I personally would not be here were it not for government social programs. I want to help better deliver these services to fellow Americans like myself so that they may take part in sharing some of the privileges I do.</p><h3><strong>On quality assurance</strong></h3><p>I’m currently doing QA testing, and I love knowing how important the QA process is in the whole development cycle. I really enjoy improving upon a product and helping it meet higher standards.</p><h3><strong>Challenges in frontend engineering</strong></h3><p>Many frontend engineers are increasingly having to deal with web maintenance, and making sure past engineering decisions are maintained and integrated well with the rest of the codebase.</p><h3><strong>Nava’s culture in three words</strong></h3><p>Educational, determined, and collaborative</p><h3>When I’m not at work, I can be found…</h3><p>Playing video games or watching anime.</p><h3>Join Us</h3><p>Nava is a talented and diverse team working holistically across engineering, research, design, and operations to positively transform how people experience government. And we’re hiring. <a href="https://www.navapbc.com/careers/">Browse open roles to learn more.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ecb62c079ce" width="1" height="1" alt=""><hr><p><a href="https://blog.navapbc.com/a-day-at-nava-as-a-frontend-developer-8ecb62c079ce">A Day at Nava as a Frontend Developer</a> was originally published in <a href="https://blog.navapbc.com/">Nava PBC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing the American Families Plan in the digital age]]></title>
            <link>https://blog.navapbc.com/implementing-the-american-families-plan-in-the-digital-age-c1a181fc2282?source=rss-382e245b904a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1a181fc2282</guid>
            <category><![CDATA[digital-service]]></category>
            <category><![CDATA[american-families-plan]]></category>
            <category><![CDATA[paid-family-leave]]></category>
            <category><![CDATA[civictech]]></category>
            <category><![CDATA[govtech]]></category>
            <dc:creator><![CDATA[Nava Public Benefit Corporation]]></dc:creator>
            <pubDate>Tue, 04 May 2021 20:29:14 GMT</pubDate>
            <atom:updated>2021-05-05T16:30:54.995Z</atom:updated>
            <content:encoded><![CDATA[<p>By Martelle Esposito, Senior Program Strategist at Nava</p><p><em>“My employer does not provide any paid maternity leave, and my husband got one whole week of paid paternity leave. So, I drained my bank of sick and vacation time to stay home for 12 weeks. When I returned to work full-time, I had no way to take half-days or days when my baby got sick or even needed a routine pediatrician visit.” — Erica</em></p><p>Unfortunately, this quote from a report by MomsRising is a common experience for many parents across the country. In the US, people go into debt or lose their jobs for having a baby or caring for a family member. Nearly<a href="https://inthesetimes.com/article/the-real-war-on-families"> one in four mothers</a> return to work within two weeks of giving birth and <a href="https://www.aarp.org/content/dam/aarp/research/public_policy_institute/ltc/2012/understanding-impact-family-caregiving-work-AARP-ppi-ltc.pdf">one in five retirees</a> left or were forced to leave the workforce earlier than planned to care for an ill family member. <a href="https://www.bls.gov/ncs/ebs/benefits/2020/employee-benefits-in-the-united-states-march-2020.pdf">Ninety-five percent of the lowest wage workers</a>, mostly <a href="https://www.dol.gov/sites/dolgov/files/OASP/evaluation/pdf/WHD_FMLAGenderShortPaper_January2021.pdf">women</a> and <a href="https://www.nationalpartnership.org/our-work/resources/economic-justice/paid-leave/paid-family-and-medical-leave-racial-justice-issue-and-opportunity.pdf">workers of color</a>, lack any access to paid family leave.</p><p>The<a href="https://www.whitehouse.gov/briefing-room/statements-releases/2021/04/28/fact-sheet-the-american-families-plan/"> American Families Plan</a> includes a critical benefit: 12 weeks of paid leave to new parents; people who are healing from an illness; caregivers for a sick family member; and survivors of sexual assault, stalking, and domestic violence seeking a safe environment. Paid leave is <a href="https://www.reuters.com/article/us-health-infantmortality-maternity-leav/paid-maternity-leave-linked-to-lower-infant-mortality-rates-idUSKCN0X51S0">linked to lower infant mortality rates</a> among other benefits, and <a href="https://www.pewsocialtrends.org/2017/03/23/americans-widely-support-paid-family-and-medical-leave-but-differ-over-specific-policies/">Americans widely support it</a>. While paid leave is a relatively new program in the US, ten states have passed legislation and eight have implemented the program. Massachusetts is one of these trailblazing states, and Nava is honored to work with them as they roll out their new paid family and medical leave program.</p><figure><img alt="95% of the lowest wage workers, mostly women and workers of color, lack any access to paid family leave." src="https://cdn-images-1.medium.com/max/891/1*hc060BaBS-W3YnbK-Z7LmA.png" /></figure><p>If the American Families Plan moves forward and paid leave is offered to all Americans, there will be a unique opportunity to get this critical program right from the start. <strong>To ensure that paid leave is equitable and effective, now is the time to talk about policy design and technical implementation.</strong></p><p>Nava has worked with some of the largest federal agencies and state benefits programs, from modernizing legacy systems to rolling out new digital services driven by legislation. We know from experience that a new paid leave program can work for the people who need it the most — it doesn’t have to be yet another brittle government service. <strong>By taking a human-centered approach and building the service with modular software components, enrolling in paid leave can be a simple and accessible experience for everyone.</strong></p><p>As policymakers debate the details of a national paid leave law, and government employees think about how they would implement the program, here are two things we’ve learned while building similar programs: Plan for a program that will evolve over time and make technology decisions with equity at the center.</p><h3><strong>Plan for a program that will evolve over time</strong></h3><p>As agencies plan to implement a new program they’ll likely discover unexpected needs along the way. They’ll learn about unique use cases from all different kinds of people who interact with the service — from workers and employers to staff administering the program. <strong>Policy, operations, and technology should be flexible enough to respond to those emerging needs.</strong></p><p><strong>Invest in and empower a digital service team.</strong> To build a responsive and nimble program, invest in a digital service team that understands the value of modular, well-crafted software that uses scalable cloud infrastructure. They will incorporate principles you can refer to often, like open source, accessibility, and reusability. Government agencies, not vendors, should own their systems, which is why investing in in-house technical talent is critical to successful service delivery. State digital services teams like Massachusetts Digital Service, Colorado Digital Service, the State of New Jersey’s Office of Innovation, California’s Office of Digital Innovation, and more are already paving the way.</p><figure><img alt="Policy, operations, and technology should be flexible enough to respond to emerging needs" src="https://cdn-images-1.medium.com/max/1024/1*nbP2MbEBOoMzAG34AgvIDw.png" /></figure><p><strong>Get core components of the service running in production, then scale adoption and functionality as you learn. </strong>Nava’s approach to addressing large-scale digital service challenges like paid leave is to build and release small, modular software components that are loosely coupled by well-defined APIs. Develop those components with real requirements and real implementation needs, planning to enhance them over time as you get feedback from people using the service. This enables agencies to quickly deliver services that help people now, while also building a flexible foundation that supports long-term technical evolution in response to changing needs.</p><p><strong>Strengthen the feedback loop between policy and implementation.</strong> Another way to build a responsive program is to pair technical teams with the policy and business operations teams. In a new program, there is substantial value in interdependent technology, policy, and operational decision-making. Technologists and policy teams can research, develop, and test small parts of the service together. By doing so, they can make data-driven policy and operational decisions that meet user needs, are technically feasible, and ensure the technology is compliant to achieve the program’s goals. For example, in Massachusetts we learned through usability testing that people wanted to apply for parental leave before their baby was born or adopted. Designers and engineers worked with the policy team to identify a compliant solution that would allow parents to apply in advance without adding significant technical or administrative scope. In doing so, parents can apply for parental leave before their baby arrives.</p><h3><strong>Make technology decisions with equity at the center</strong></h3><p>As stated in President Biden’s plan, paid leave can <a href="https://www.tandfonline.com/doi/full/10.1080/13668803.2019.1704398">reduce racial disparities</a> in wage loss between workers of color and white workers, and increase women’s participation in the labor force. There’s an opportunity to design with the people who need this service the most, learn about what might prevent them from accessing it, and make it as easy as possible for them to enroll.</p><p><strong>Build with marginalized communities. </strong>Take a human-centered approach by talking to all user groups — workers, employers, healthcare providers, and the civil servants who will need to maintain and operate the service. Engaging with communities throughout the development process helps identify potential pitfalls before the service is rolled out. Talk to people from marginalized groups, including women of color who have been historically stigmatized for accessing public benefit programs. What you learn could reveal opportunities for content and product strategy. These conversations can also help you leverage influential voices who can add a layer of credibility when you’re rolling out the program. When recruiting for user research (research that aims to understand behaviors, needs, and motivations of people engaging with the service), use a demographic screener to ensure you’re speaking with a diverse cohort and uplifting their voices. At the close of every research session, compare the recruitment diversity to the overall makeup of the region, and use that to signal where to focus next. For example, if in your early research you spoke to a lot of people with bachelor degrees, prioritize new research with people who have an associates degree or a high school diploma.</p><p><strong>Words matter; prioritize content strategy. </strong>People who apply for paid leave are often under stress, whether they’re expecting a baby or dealing with a health crisis. Content strategy — sending the right message to the right person at the right time — can make or break the experience of applying for paid leave. For example, use <a href="https://www.plainlanguage.gov/">plain language</a> to help a broad range of people understand their rights and responsibilities. Read more about <a href="https://www.navapbc.com/toolkits/content-strategy-for-user-onboarding.html">Nava’s approach content strategy and user onboarding</a>.</p><p><strong>Leverage your technology to measure progress towards program outcomes. </strong>Develop a strong monitoring, data analytics, and evaluation plan from the get-go. Plan to measure progress towards program outcomes, leveraging data from the technology you are building. Don’t wait for your vendor to send you data a few times a year. Set up a dashboard so you can see how people are interacting with your service in real time, and do research with your users throughout implementation. Use that information to make improvements that meet participant and program administration needs. Continue to measure their impact and improve the service over time in iterative cycles to achieve your programmatic goals.</p><p>The United States is the only industrialized country in the world without a national paid leave program. If the American Family Plan is enacted as proposed, it will mark a huge step forward for the country, at a time when people are in dire need of support. It is possible and within reach to build a simple, effective, and accessible program from the ground up. If done right, we’re hopeful that a national paid family and medical leave program will lay strong foundations for a more resilient and equitable safety net that’s fit for the digital age.</p><p><em>Special thanks to Tamar Fox, Allison Johnson, Madison Loew,</em> <em>Shaun Mosley,</em> <em>Lauren Peterson, and Makaela Stephens for their contributions to this piece.</em></p><p><strong>Let’s work together</strong><br>Since our founding, Nava has been trusted to solve some of the most urgent, challenging, and highly scrutinized government technology projects. We’d love to hear about yours. <a href="https://www.navapbc.com/contact/">Get in touch</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1a181fc2282" width="1" height="1" alt=""><hr><p><a href="https://blog.navapbc.com/implementing-the-american-families-plan-in-the-digital-age-c1a181fc2282">Implementing the American Families Plan in the digital age</a> was originally published in <a href="https://blog.navapbc.com/">Nava PBC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navanauts at Work]]></title>
            <link>https://blog.navapbc.com/navanauts-at-work-24c25c89c762?source=rss-382e245b904a------2</link>
            <guid isPermaLink="false">https://medium.com/p/24c25c89c762</guid>
            <category><![CDATA[govtech]]></category>
            <category><![CDATA[meet-the-team]]></category>
            <category><![CDATA[policy]]></category>
            <category><![CDATA[civictech]]></category>
            <dc:creator><![CDATA[Nava Public Benefit Corporation]]></dc:creator>
            <pubDate>Thu, 15 Apr 2021 15:55:01 GMT</pubDate>
            <atom:updated>2021-04-15T16:37:50.398Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Every day Navanauts build simple, effective, and accessible digital services to help improve how the government serves vulnerable populations. These services operate at massive scale, meet urgent social needs, and have legacies measured in generations.</em></p><p><em>In the Navanauts at Work series, learn a little bit about what it’s like to do this work from some of the people who are doing it.</em></p><h3>Martelle Esposito (she/her), Senior Program Strategist</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LMeKc462KUcXBuS7" /></figure><p><strong>The path to Nava</strong></p><p>Nava is one of the first movers connecting public policy, program implementation, technology, and design. I came to Nava because I was interested in contributing to combining these worlds to help transform government services. Having worked primarily in nonprofit and academic settings prior to Nava, most recently at the <a href="https://thewichub.org/supporting-wic-enrollment-using-technology-to-improve-certification-experience-for-wic-participants-and-wic-agencies/">WIC</a> innovation lab at Johns Hopkins University, the company’s mission-driven approach and community feel were also big factors in my excitement to join the team.</p><p><strong>Nava’s culture in three words</strong></p><p>Meaningful, collaborative, efficient</p><p><strong>On the impact of civic tech</strong></p><p>Working in a multidisciplinary and experimental environment to solve problems together and push the boundaries of what is possible for critical government services keeps me motivated. Knowing that my work directly impacts real people who are navigating life milestones and facing challenges is fulfilling.</p><p><strong>On government</strong></p><p>I believe government is one of the greatest tools we have for social change. Government has the power to promote or hinder a healthy, productive, and thriving society at scale, the potential to impact the quality of life for millions of people, and the ability to set off a chain reaction to dismantle historically oppressive power dynamics with policy actions.</p><p><strong>Current projects</strong></p><p>One of the projects I find most exciting is unpacking how similarities and differences between paid family and medical leave policies in different states impact program implementation opportunities and constraints. It’s fascinating, and I’m able to directly apply this learning to work the team at Nava is doing with Massachusetts to stand up their paid family and medical leave program, one of only a handful of these state programs in the country.</p><p><strong>When I’m not at work, I can be found…</strong></p><p>Exploring Baltimore neighborhoods by foot or bike.</p><h3>Join Us</h3><p>Nava is a talented and diverse team working holistically across engineering, research, design, and operations to positively transform how people experience government. And we’re hiring. <a href="https://www.navapbc.com/careers/">Browse open roles to learn more.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24c25c89c762" width="1" height="1" alt=""><hr><p><a href="https://blog.navapbc.com/navanauts-at-work-24c25c89c762">Navanauts at Work</a> was originally published in <a href="https://blog.navapbc.com/">Nava PBC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navanauts at work]]></title>
            <link>https://blog.navapbc.com/navanauts-at-work-506229a9c708?source=rss-382e245b904a------2</link>
            <guid isPermaLink="false">https://medium.com/p/506229a9c708</guid>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[meet-the-team]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[civictech]]></category>
            <category><![CDATA[govtech]]></category>
            <dc:creator><![CDATA[Nava Public Benefit Corporation]]></dc:creator>
            <pubDate>Thu, 01 Apr 2021 17:08:11 GMT</pubDate>
            <atom:updated>2021-04-02T05:31:01.137Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Every day Navanauts build simple, effective, and accessible digital services to help improve how the government serves vulnerable populations. These services operate at massive scale, meet urgent social needs, and have legacies measured in generations.</em></p><p><em>In the Navanauts at Work series, learn a little bit about what it’s like to do this work from some of the people who are doing it.</em></p><h3><a href="/service/mailto:eddietejeda@navapbc.com">Eddie Tejeda</a> (he/him), Director of Engineering — Infrastructure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*Pjq2EkUT3Pj6UrYW" /></figure><p><strong>The path to Nava</strong></p><p>I’ve been in the civic tech space for the past decade, working at places like 18F, where I led cloud.gov, and before that as a Code for America fellow, where I worked closely with local governments.</p><p>So I’ve had a chance to get to know a lot of organizations focused on government innovation. But throughout the years, I always kept an eye on Nava. I admired the founding story of the team and their commitment to long-term thinking in the public interest. So when the time seemed right for me, I decided to learn more about the company’s goals, and they fortunately lined up perfectly with my interests.</p><p><strong>Nava’s culture in three words</strong></p><p>Ambitious, optimistic, inclusive</p><p><strong>Nava’s impact on critical services</strong></p><p>For me, the most fulfilling part of my job is working at a large scale, both from a technical perspective and in terms of impact. We are working on systems that are at the core of the American economy and healthcare system. Knowing that the improvements we make have a lasting impact on millions of people is deeply rewarding.</p><p><strong>On government</strong></p><p>The role of government is to harness resources that benefit society. Similar to how companies harness the power of the wind, water, or light towards productive goals, governments harness the total capacity of a society towards collective goals.</p><p>Ultimately, we measure a society by the way that it treats its least privileged. Having a strong safety net is a necessary part of building a society in which everyone has the opportunity to lead a healthy and meaningful life.</p><p>So we have to build systems that are flexible enough that they can adapt to constant social, cultural, and technological change but sturdy enough that they can last for centuries. That’s an inherently complicated problem, but that’s the task at hand.</p><p><strong>Current projects</strong></p><p>A big emphasis of my work will be looking over our cloud infrastructure at CMS, where vital services like HealthCare.gov and <a href="https://blog.navapbc.com/nava-pbc-awarded-contract-to-improve-mymedicare-gov-e2d82ef1afee">MyMedicare.gov</a> currently run. But I will also be involved in state-level projects. COVID-19 has revealed some of the infrastructural weaknesses that states have to address to respond to crises effectively. This state-level infrastructure work will become increasingly important as we move forward.</p><p><strong>When I’m not at work, I can be found…</strong></p><p>Ideally, I would be backpacking through the Sierras, but on a typical week, you’ll find me obsessing about my sourdough bread.</p><h4>Join Us</h4><p>Nava is a talented and diverse team working holistically across engineering, research, design, and operations to positively transform how people experience government. And we’re hiring. <a href="https://www.navapbc.com/careers/">Browse open roles to learn more.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=506229a9c708" width="1" height="1" alt=""><hr><p><a href="https://blog.navapbc.com/navanauts-at-work-506229a9c708">Navanauts at work</a> was originally published in <a href="https://blog.navapbc.com/">Nava PBC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Now hiring: Client Solutions Manager]]></title>
            <link>https://blog.navapbc.com/now-hiring-client-solutions-manager-24b5364fe6c0?source=rss-382e245b904a------2</link>
            <guid isPermaLink="false">https://medium.com/p/24b5364fe6c0</guid>
            <category><![CDATA[job-opening]]></category>
            <category><![CDATA[civictech]]></category>
            <category><![CDATA[govtech]]></category>
            <category><![CDATA[business-development]]></category>
            <dc:creator><![CDATA[Nava Public Benefit Corporation]]></dc:creator>
            <pubDate>Wed, 09 Dec 2020 21:40:22 GMT</pubDate>
            <atom:updated>2020-12-10T04:04:09.976Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By Brian Hanley, Vice President of Business Development at Nava</em></p><p>Nava is a <a href="https://blog.navapbc.com/why-is-nava-a-public-benefit-corporation-3c20e1617856">Public Benefit Corporation</a> which means that our mission — to make public digital services simple, effective, and accessible to all — informs everything we do. Our mission guides how we choose to bid on the most <a href="https://blog.navapbc.com/how-nava-picks-government-work-6983cd191739">impactful projects</a>, how we conceive and propose flexible and human-centered solutions, and how we deliver working software that addresses the unmet needs of civil servants and program beneficiaries.</p><figure><img alt="Apply today for the client solutions manager role" src="https://cdn-images-1.medium.com/max/1024/1*_8A497dd1jjsXwaZ1vQflw.png" /></figure><p>Traditionally, in the government contracting ecosystem, a “Capture Manager” orchestrates solution development and the proposal process. The traditional Capture Manager’s job is to increase the probability of winning the bid by leveraging their relationships, narrowing the competitive field, and speaking to client pain points and fears to frame their proposed solution in the best light. In short, a strong traditional “capture”, as defined by the industry, seeks to narrow and limit the government’s choices, ideally providing no choices except the one proposed.</p><p>At Nava, this role is different. Instead of working to constrain the government’s options, we work to expand them. This aligns with <a href="https://www.navapbc.com/values/">our values</a>, how we operate at Nava and reflects the relationship we strive to build with our government clients. We are seeking a <a href="https://jobs.lever.co/nava/5e0edeeb-ba79-4cb0-8074-f4cbe5ce55b9?utm_medium=jobpost&amp;utm_source=creativeguild"><strong>Client Solutions Manager </strong></a>to help us conceive and propose the best possible solutions for our prospective clients. At Nava, Client Solutions Managers support Nava’s mission by engaging our subject matter experts — engineers, designers, researchers, content strategists, and program analysts — to tailor human-centered solutions that meet users’ needs and programmatic goals in the short-term and long-term, embracing the constraints that exist within complex programs and agencies.</p><p>We pursue the highest impact projects, the most challenging service transformation and modernization projects, often under public scrutiny or legislative deadlines. We believe that government programs serving vulnerable populations cannot fail — that these services are critical to rebuilding trust in public institutions and cannot be ineffective or inefficient. The stakes are extremely high, so the standards we hold ourselves to must be even higher. In order to meet them, our goal is to develop solutions that are flexible to quick iteration, reliable, secure, compliant, and easily replaceable so that the government is always in a position to change technologies, approaches, or vendors to meet people’s needs in a world that is only evolving more rapidly.</p><p>The Nava Client Solutions Manager is charged not just with winning work that helps us achieve our mission, but proposing solutions that lay the groundwork for delivery partnership, that provide our government clients with options and flexibility, and ensure that the services we build together will be simple, effective, and accessible to all.</p><p><a href="https://jobs.lever.co/nava/5e0edeeb-ba79-4cb0-8074-f4cbe5ce55b9?utm_medium=jobpost&amp;utm_source=creativeguild">Nava - Client Solutions Manager (DC, SF, NYC, Remote)</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24b5364fe6c0" width="1" height="1" alt=""><hr><p><a href="https://blog.navapbc.com/now-hiring-client-solutions-manager-24b5364fe6c0">Now hiring: Client Solutions Manager</a> was originally published in <a href="https://blog.navapbc.com/">Nava PBC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Day at Nava as a Software Engineer]]></title>
            <link>https://blog.navapbc.com/a-day-at-nava-as-a-software-engineer-c01879277ce?source=rss-382e245b904a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c01879277ce</guid>
            <category><![CDATA[software-engineer]]></category>
            <category><![CDATA[apprenticeship]]></category>
            <category><![CDATA[civictech]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Nava Public Benefit Corporation]]></dc:creator>
            <pubDate>Thu, 22 Oct 2020 18:39:23 GMT</pubDate>
            <atom:updated>2020-12-24T21:06:56.025Z</atom:updated>
            <content:encoded><![CDATA[<p><em>It’s hard to describe what a typical day at Nava is like because no two days are ever the same. Every day brings new projects, challenges, and opportunities. So we’re sharing just a glimpse of what work is actually like for different </em><a href="https://www.navapbc.com/about/team/"><em>Navanauts</em></a><em>. Here’s what</em><a href="https://www.linkedin.com/in/alsia-plybeah-6114a5178/"><em> Alsia Plybeah</em></a><em>, a software engineer who started at Nava as an </em><a href="https://blog.navapbc.com/nava-pbc-welcomes-first-cohort-of-engineering-apprentices-5e89d4bcad6f"><em>apprentice</em></a><em>, has been up to lately.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6LMfVArMMAhR_YzfmzwUMA.jpeg" /><figcaption>Alsia Plybeah, software engineer at Nava, working in the DC office pre-pandemic. Photo by Eric Chiu</figcaption></figure><h4>On expectations versus reality</h4><p>My “every day” at Nava is completely different than what I expected when I first started here. In the project I’m currently working on — supporting <a href="https://www.mass.gov/info-details/paid-family-and-medical-leave-pfml-fact-sheet">Paid Family Medical Leave in Massachusetts</a> — I was surprised to find out how closely I’d work with government stakeholders. I actually get to see legislation come to life and help build the systems that support it.</p><p>I previously thought I’d be working heads down with other engineers. But our work is a lot more than that. There’s a lot of collaboration (which I love), writing, research, and helping people who aren’t technical understand what we’re building. I’m using skills from previous work that I didn’t expect to bring out here.</p><h4>On the <a href="https://jobs.lever.co/nava/aa96a257-6434-4dea-96bb-2e32dbb26a25">Engineering Apprenticeship </a>Program</h4><p>As an apprentice, I got to take on real work — not busy work — as a junior engineer. It was first and foremost a learning opportunity, which was extremely helpful because this was my first job in tech. I basically had a person dedicated to helping me navigate the world of government contracting and day-to-day as an engineer. After meetings, for example, we’d have a debriefing session where I could ask questions and get the proper context around policies and decisions.</p><p>And it was fun. I got to play around with things like state management with Redux, custom tools like Sniffybara (a Rails tool, based on Capybara, that checks for accessibility in code), Flask and seeing the differences between that and Django (both for Python), and documentation like Storybook, which lets you build interactive documentation for your app.</p><h4>On changing career paths</h4><p>Before I got into engineering, I worked at a library and volunteered at polling stations and in grassroots community organizing. I hadn’t worked in tech before but I recognized and understood the need for civic tech.</p><p>When I first applied for the apprenticeship, I was focused on front-end engineering and more specifically, accessibility. But I’ve since shifted into back-end engineering and infrastructure. The project I was first assigned to had a blend of responsibilities, which let me try out other things. And there are other opportunities to learn, at things like off site workshops like Design for Engineers.</p><p>I wouldn’t have said I was really into back-end work without the chance to really dive into it. People on my team were actively supportive of this transition. Pairing and screen sharing <a href="https://blog.navapbc.com/learning-front-end-development-as-a-designer-6c2ab5825f0d">to learn new skills</a> is pretty common. People are willing to work with you or get on a call to answer questions.</p><h4>Join us</h4><p>Nava is a talented and diverse team working holistically across engineering, research, design, and operations to positively transform how people experience government. And we’re hiring. <a href="https://www.navapbc.com/careers/">Browse open roles to learn more</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c01879277ce" width="1" height="1" alt=""><hr><p><a href="https://blog.navapbc.com/a-day-at-nava-as-a-software-engineer-c01879277ce">A Day at Nava as a Software Engineer</a> was originally published in <a href="https://blog.navapbc.com/">Nava PBC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Day at Nava as an Infrastructure Engineer]]></title>
            <link>https://blog.navapbc.com/a-day-at-nava-as-an-infrastructure-engineer-bce5288db7a?source=rss-382e245b904a------2</link>
            <guid isPermaLink="false">https://medium.com/p/bce5288db7a</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[meet-the-team]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[civictech]]></category>
            <dc:creator><![CDATA[Nava Public Benefit Corporation]]></dc:creator>
            <pubDate>Thu, 16 Jul 2020 17:10:57 GMT</pubDate>
            <atom:updated>2020-07-16T17:10:57.124Z</atom:updated>
            <content:encoded><![CDATA[<p><em>It’s hard to describe what a typical day at Nava is like because no two days are ever the same. Every day brings new projects, challenges, and opportunities. So we’re sharing just a glimpse of what work is actually like for different </em><a href="https://www.navapbc.com/about/team/"><em>Navanauts</em></a><em>. Here’s what Wei Leong, an infrastructure engineer, has been up to lately.</em></p><figure><img alt="Infrastructure engineer, Wei Leong working from home." src="https://cdn-images-1.medium.com/max/642/1*-4E6iSgmUBYKwy9H9qZ5dw.png" /><figcaption>Infrastructure engineer <em>Wei</em><strong><em> </em></strong><em>Leong working from home.</em></figcaption></figure><h4>Current projects</h4><p>I’m working on the <a href="https://www.navapbc.com/public-benefit-reports/2019/#creating-responsive-health-care-services-for-58-million-people">Medicare Payment System Modernization</a> (MPSM) project. MPSM modernizes the Medicare payments system. This system affects approximately <a href="https://www.usds.gov/projects/medicare-payment-program">57 million people</a> who depend on Medicare and processes over <a href="https://www.usds.gov/projects/medicare-payment-program">$500 billion</a> in claims each year. It’s a vital service.</p><p>But the current system is about 40 years old, runs on millions of lines of COBOL and assembly language, and is deployed to mainframe computers. Our job is to build a platform that enables different teams to deploy and operate their services using modern tools such as Terraform, Docker, and Amazon Web Services (AWS).</p><p>Right now, we’re in the midst of two migrations: in one, we’re updating our infrastructure configuration from Terraform 0.11 to 0.12; and two, from Elastic Container Services (ECS, an AWS service) instances to AWS Fargate. We’re also working on standing up infrastructure for public APIs that we plan to roll out in the future.</p><p>It’s an interesting project because it provides the opportunity to work on some legacy technologies that aren’t common today. You don’t get to integrate decades-old and modern technologies very often.</p><h4>On the day-to-day</h4><p>I tend to get a lot of my coding/implementation work out of the way in the mornings. Because I’m on the East Coast — our team is distributed across the country — I start the day earlier than most. It’s a good time to do more quiet, focused, solo work.</p><p>We operate on two-week sprints. On the last day, different teams within the MPSM project get to demo what they’ve been doing over the last couple of weeks. Recently, I demoed a deployment pipeline using a Jenkins shared library that our team has been working on. The goal of these demos is to share one or two highlights with stakeholders, including people from government and other contractors on the project.</p><h4>Favorite part of the day</h4><p>My favorite part of the day is usually in the afternoon, when everyone is available to either pair on certain tasks or collaborate on system design and research projects. A lot of our collaboration is done over Google Meet, Zoom, or even Slack messages.</p><p>If I’m stuck on a problem, someone’s around to help me resolve it because everyone, regardless of where they are, is available during this time. It also enables me to better understand what other people are working on.</p><h4>On working from home during the COVID-19 pandemic</h4><p>I usually work out of the Washington, D.C. office, but like everyone else, I’m <a href="https://blog.navapbc.com/practical-tips-for-working-remotely-cfe829e6b95f?source=---------2">working from home</a> right now. My partner and I rotate childcare responsibilities every few hours, but we don’t have a specific schedule. (We had one but it just didn’t hold up.)</p><p>My team’s been very understanding and accommodating of my (sort-of) chaotic schedule. I just make sure to communicate when I’m available and when I’m not. Usually, meetings or discussions can be moved to accommodate.</p><h4>Join us</h4><p>Nava is a talented and diverse team working holistically across engineering, research, design, and operations to positively transform how people experience government. And we’re hiring. <a href="https://www.navapbc.com/careers/">Browse open roles to learn more</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bce5288db7a" width="1" height="1" alt=""><hr><p><a href="https://blog.navapbc.com/a-day-at-nava-as-an-infrastructure-engineer-bce5288db7a">A Day at Nava as an Infrastructure Engineer</a> was originally published in <a href="https://blog.navapbc.com/">Nava PBC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>